If we start a new application we should take in my that our application should be easily upgradable and distributable. Some applications require maximum uptime. This application can be, for example…

Medium_JS is a curated collection of insights and tutorials on JavaScript development, designed to help developers stay informed and inspired in the ever-evolving world of web development. By featuring a selection of high-quality articles, tutorials, and expert opinions from the JavaScript community, Medium_JS offers  guidance on mastering JavaScript language features, exploring modern frameworks and libraries, and solving common development challenges. Whether you're a frontend developer, a full-stack engineer, or an aspiring JavaScript enthusiast, Medium_JS provides a  knowledge and resources to fuel your JavaScript journey.

Medium

In Golang we can start multiple web servers that use the same port. When we start a new process in Golang, you can specify file descriptors that can be inherited. We can share our opened socket with our child so our child can start where we left off. The second variant is rather more complex but can be used in multiple scenarios.

Zero downtime API in Golang

Good use cases with two examples explained with code.

I don’t see how you replace the binary with minimal downtime? you can’t replace the binary with another one because it’s in use…? you only seem to restart it, wouldn’t you start a new version (from another path/filename) on the same address/port and then kill the old version?

Is this pretty much a rolling deployment strategy? Run 2 processes, wait until its ready then switch over the network exposure to the new (healthy) service/binary?