Sure. Let me try to share some details. But before that, just want to make a point (which you surely know) that its also a major decision of a language change from Java to Go.<p>In the Tomcat&#x2F;Jetty&#x2F;&lt;any other Java app server&gt; world. If we want to have a web app (HTTP) we need to code servlets and add them into web.xml config, matching urls to Servlet Names. And within the Servlet we have coded, we need to call other Java code (the logic).<p>The container&#x2F;app server takes care of the TCP&#x2F;HTTP layers. Thread pools (which you can configure etc.).<p>Now in the Golang world. We just use the http package[1] for all that.<p>To listen to url:<p><pre><code>  http.Handle(&quot;&#x2F;doSearch&quot;, &amp;MySearch{&quot;MySearch&quot;})
</code></pre>
Where MySearch is a struct which just needs to implement the interface:<p><pre><code>  func ServeHTTP( w http.ResponseWriter,r * http.Request)
</code></pre>
Within this function you can put all the code which you will put in a java Servlet.<p>And to make this a service in your main package&#x2F;program you will also do:<p><pre><code>  err := http.ListenAndServe(&quot;localhost:10001&quot;, nil)
</code></pre>
So these 3 pieces are the ones needed to have your own micro service or any web service running.<p>In our case, the similar functionality when moved resulted in lower memory usage and much higher stability (very less crashes, in the rare event of the service needing memory, which OS doesn&#x27;t have. So the OS will kill that service anyhow - tech independent. We check using dmesg | grep &lt;program name&gt;)<p>Another benefit of this move, from our experience is getting rid of that webapp folder in any Java Servlet container. You will often end up plugging along multiple smaller apps, alongside your main one. And all reside in the same process.<p>That&#x27;s not ample segregation, in our use. Its better you have different processes. So even if one dies, the others are independent.<p>This is also easier to manage. Deploy new ones - restarting just the ones changed.<p>Now we all know hot loading (without restart) is offered in several techs including some Java containers. But in practice, there always is some silly reason for you to restart. And sometimes the reason is psychological :-), we are not convinced that there is some baggage until we restart.<p>So hope my brief experience share is of some use. All the best.<p>Edit: Just want to add You must review this package page, if you are considering it<p>[1] <a href="https:&#x2F;&#x2F;golang.org&#x2F;pkg&#x2F;net&#x2F;http&#x2F;" rel="nofollow">https:&#x2F;&#x2F;golang.org&#x2F;pkg&#x2F;net&#x2F;http&#x2F;</a>