135M messages a second between processes in Java (2013)

The JVM is a treasure just sitting there waiting to be rediscovered.<p>It really is a shame that there is so much noise and unnecessary complexity around using it.

There&#x27;s also more light weight alternatives to &quot;XML heavy traditional frameworks&quot; on Java side. Check for example Play[1], which makes the &quot;write some code, test in browser, write more, test&quot; cycle possible.<p><a href="https:&#x2F;&#x2F;www.playframework.com" rel="nofollow">https:&#x2F;&#x2F;www.playframework.com</a>

Java in HFT environment is wonderfully perverse and beautifully abused in so many ways.

Is there any reason someone would want to run multiple Java processes communicating at high speed? It seems useless, since the massive overhead of each process makes IPC useless in a high-performance environment.

Moving blocks of memory around is something I am expecting java to do quite fast, just because the VM has intrinsic instructions to do that. You could do the same thing in any other language.

With all those memory accesses marked as unsafe, I&#x27;m wondering why not just use C++.

Can someone elaborate on this:<p>&quot;IPC, what&#x27;s the problem? Inter Process Communication is an old problem and there are many ways to solve it (which I will not discuss here).&quot;<p>How is IPC an old problem and how was it solved?

(2013)