A few things to consider:<p>* it tends to be harder to write good C++ code than Java. For example we think that an average person can write better java code than C++ code because java is simpler to get going with. We also think that the average developer makes fewer mistakes in java than C++ (because C++ allows you to do &#x27;crazy things!&#x27;)<p>* that means that you need (on average) a better developer for C++, and that tends to cost more<p>* java tooling is exceptional (probably the best there is?)<p>* making small changes and releasing is much quicker in Java; builds tend to be shorter in duration for example<p>* once you have the framework for your system, the differentiator is then the business benefits delivered. If you can push small changes out very quickly you&#x27;re getting rewards quicker and you can experiment more<p>* once you get down to certain performance points, it becomes similar writing java code as writing C++ code, but the JVM is also doing various work that you can&#x27;t control so much. That can then inhibit you.<p>Other things:<p>* Azul isn&#x27;t just h&#x2F;w development it&#x27;s also now in kernel plugin form iirc<p>* Have a look at Aeron (<a href="https:&#x2F;&#x2F;github.com&#x2F;real-logic&#x2F;Aeron" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;real-logic&#x2F;Aeron</a>) and I think the C++ and Java versions are fairly similar performance and they&#x27;re designed by super  with decent (industry renowned) developers writing it<p>* A lot of people write high performance code making extensive use of templates. That&#x27;s a totally different way of programming than usual C++