Chronicle Queue and Aeron are both high-performance messaging systems, but they have different strengths and weaknesses.
Chronicle Queue is designed for low latency and high throughput messaging within a single machine or cluster. It uses a shared memory ring buffer to store messages, which can achieve very low latency (<1 microsecond) for messages that are sent and received on the same machine. Chronicle Queue also supports persistence, so messages can be written to disk and recovered in the event of a crash.
Aeron is designed for high-performance messaging between machines over a network. It uses a reliable UDP transport protocol, which can achieve very high throughput (up to 100 million messages per second) with low latency (<1 millisecond). Aeron also supports persistence, so messages can be written to disk and recovered in the event of a crash.
In general, Chronicle Queue is a good choice for applications that require very low latency messaging within a single machine or cluster. Aeron is a good choice for applications that require high-performance messaging between machines over a network.
| Feature | Chronicle Queue | Aeron |
|---|---|---|
| Latency | Very low (<1 microsecond) | Low (<1 millisecond) |
| Throughput | High (up to 100 million messages per second) | Very high (up to 1 billion messages per second) |
| Persistence | Yes | Yes |
| Transport protocol | Shared memory | Reliable UDP |
| Use cases | Low latency messaging within a single machine or cluster | High-performance messaging between machines over a network |
Ultimately, the best choice for you will depend on your specific needs and requirements. If you need very low latency messaging within a single machine or cluster, then Chronicle Queue is a good choice. If you need high-performance messaging between machines over a network, then Aeron is a good choice.