Ultra-low-latency, batching and concurrent queue for IPC in Java

<a href="https:&#x2F;&#x2F;github.com&#x2F;coralblocks&#x2F;CoralRing&#x2F;blob&#x2F;1168b047e0183c9195ab48505e43e8fb2faea73d&#x2F;src&#x2F;main&#x2F;java&#x2F;com&#x2F;coralblocks&#x2F;coralring&#x2F;ring&#x2F;BlockingRingConsumer.java#L190">https:&#x2F;&#x2F;github.com&#x2F;coralblocks&#x2F;CoralRing&#x2F;blob&#x2F;1168b047e0183c...</a><p>Am I missing something here or does the BlockingRingConsumer not actually block? And worse doesn&#x27;t it just return garbage if poll is called without first checking availableToPoll?<p>The example sure looks like it... <a href="https:&#x2F;&#x2F;github.com&#x2F;coralblocks&#x2F;CoralRing&#x2F;blob&#x2F;main&#x2F;src&#x2F;main&#x2F;java&#x2F;com&#x2F;coralblocks&#x2F;coralring&#x2F;example&#x2F;ring&#x2F;BlockingConsumer.java">https:&#x2F;&#x2F;github.com&#x2F;coralblocks&#x2F;CoralRing&#x2F;blob&#x2F;main&#x2F;src&#x2F;main&#x2F;...</a><p>Which if so isn&#x27;t this like 1&#x2F;4th a library for doing IPC? It doesn&#x27;t seem to do much itself

Weird to see this here! I&#x27;ve used CoralBlocks in the low-latency trading domain previously. Highly recommend. The API is kind, they&#x27;re very responsive, and the latency is exceptional (and comes with all the basics like thread pinning built-in for convenience)

Related: <a href="https:&#x2F;&#x2F;github.com&#x2F;pcdv&#x2F;jocket">https:&#x2F;&#x2F;github.com&#x2F;pcdv&#x2F;jocket</a><p>Drop-in replacement for java.net.Socket using shared memory (and optionally, futex for notification)

it&#x27;s sad how comfy the world for spawning request is versus when you are on the receiving side.

I don’t get it. How is this advantageous as it’s limited to one machine? Why wouldn’t you just have one jvm running multiple threads? What is the point of having multiple jvm processes interacting through this ring? Can someone enlighten me?

Does anyone have suggestions for something like this, but in Golang?

This is fascinating. I have no idea what something like this would be used for though... what are the use cases?

Super cool, nice work!

Our kafka isn’t reliable enough. I need to write data on disk before flushing it to kafka. Can I use this lis to write data to disk and then consume inside same jvm. I need data to live through restarts

ultra-low-latency and java in the same sentence... masochists?