3 ms·
Given the documentation says that this is supposedly to be between JVMs, how do they handle the serialize/deserialize?
by bsder 2y ago
Given the documentation says that this is supposedly to be between JVMs, how do they handle the serialize/deserialize?
- kasey_junk 2y agoThey punt on the actual serialization format: https://www.coralblocks.com/index.php/inter-process-communication-with-coralqueue/ https://www.coralblocks.com/index.php/inter-process-communic... In most applications like this you'll see direct byte manipulation to byte buffers because you want to pull as much performance as possible. There are fast serialization formats like SBE that people leverage for this as well.
- joas_coder 2y ago> Given the documentation says that this is supposedly to be between JVMs, how do they handle the serialize/deserialize? Your transfer object needs to implement MemorySerializable. Below two examples from CoralRing's GitHub: https://github.com/coralblocks/CoralRing/blob/main/src/main/java/com/coralblocks/coralring/example/ring/Message.java https://github.com/coralblocks/CoralRing/blob/main/src/main/... https://github.com/coralblocks/CoralRing/blob/main/src/main/java/com/coralblocks/coralring/util/PayloadByteBufferMessage.java https://github.com/coralblocks/CoralRing/blob/main/src/main/... The second one effectively allows you to send anything you want (as bytes) through the ring, making CoralRing message agnostic.