On Sunday, September 3, 2017 at 11:35:30 PM UTC+2, emarti...@gmail.com wrote: > > I am looking for the 'best' way to launch and monitor several go > processes. Doing it with just 1 is easy enough, using monit or systemctl > should do the trick, however since our app takes a while to start, we want > to keep a few proceses running at all times so we don't have downtime > everytime the app needs to be restarted. Similar to how apache sub proceses > works. One of the solutions we are thinking is to create a go launcher that > will spawn sub processes and using systemctl on that launcher. >
How are users interacting with your program? If it is network-based you could just run multiple instances of your process with a load balancer in front. Either software (haproxy, nginx) or an (often expensive) hardware solution. Most cloud providers even have options for running hosted load balancers. Then it is just a matter of doing a rolling upgrade and restart your processes one by one and the load balancer will route around the unavailable processes. Cheers, Christian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
