<p>I was told that Go's garbage collector does not cause interruptions in the program unlike Java's garbage collector which can cause a program to pause. This makes Go's much superior for latency sensitive micro-services.</p>

<p>I tried understanding this but not being an expert, I did not. I found some stuff like -
sub 10ms latency <a href="https://groups.google.com/forum/?fromgroups#!topic/golang-dev/Ab1sFeoZg_8" rel="nofollow noreferrer">https://groups.google.com/forum/?fromgroups#!topic/golang-dev/Ab1sFeoZg_8</a></p>

<p>In general, are there reasons where Go is a superior choice for designing micro-services running on docker/kubernetes compared to Java (I know that until Java 9,  Java only understood memory and cpu resources at a host level. which meant that it made assumptions about sizing thread pools and memory allocations and Docker wouldn't always provide these resources).  </p>

Illusionist
<p>10ms in Go GC is outdated. </p>

<p><a href="https://i.stack.imgur.com/165gA.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/165gA.png" alt="enter image description here"></a>Last time GC was improved in Go 1.10 (Feb 2018)</p>

<p>Regarding STW:</p>

<blockquote>
  <p>We now have an objective of 500 microseconds stop the world pause per GC cycle. Perhaps a little sandbagging here.</p>
</blockquote>

<p>See <a href="https://blog.golang.org/ismmkeynote" rel="nofollow noreferrer">https://blog.golang.org/ismmkeynote</a></p>
