Java JIT vs. Java AOT vs. Go for Small, Short-Lived Processes
It&#x27;s hard to square these articles with the reality I see on the ground: our baseline memory usage for common types of Java service is 1 GB, vs 50 MB for Go. We do have a few mammoth servers at the top end in both languages though (e.g. 75 GB heaps)<p>The deploy JARs have 100+ MB of class files, so perhaps it&#x27;s a function of all the dependencies that you &quot;need&quot; for an enterprise Java program and not something more fundamental.<p>These blog posts also present AOT as if its just another option you can toggle, while my impression is that it&#x27;s incompatible with common Java libraries and requires swapping &#x2F; maintaining a parallel compiler in the build toolchain, configuring separate rules to build it AOT, etc. I don&#x27;t have actual experience with it though so I could be missing something.