Does go have a hot update mechanism? If not, how to design a hot update mechanism?

  golang, question

The company plans to let us accumulate small program technology and develop a small program every month. If there is no demand, we can think of a demand by ourselves.

Most small programs need back-end support.

The back-end is going to use go. That’s the problem. How should the back-end project be designed?

I want to write the back-end of all small programs into a go project, but every time I add the back-end of a small program, I have to restart this large go project. The restart is very fast, but even if it is faster, it may affect the users who are playing small programs, and in case there is data in memory, it will disappear after the restart.

Does go have a hot update mechanism? If not, how to design a hot update mechanism?

(I know PHP is excellent in this respect, but I have been using PHP for more than two years and want to change my language to feel the charm of go.)

I tried to learn go a few years ago, and if I am interested, I can take a look at it (I am not sure if I can use it, because I didn’t care after I finished it at that time):https://github.com/tim1020/go …

In addition, here are some references:
http://grisha.org/blog/2014/0 …
http://studygolang.com/articl …
http://siddontang.com/2015/01 …