Chronicle Queue is available as a fully native Java, Rust or C++ library, and also supports a Python API. All versions are fully binary compatible.
Eliminate Compatibility Issues
- Build your queue messaging system with the flexibility to use Java, Python, C++, or Rust and leverage the strengths of each.
- Ensure efficient interoperability whilst minimising development time and enhancing system performance.
- Chronicle Queue supports throughputs of millions of events per second, with stable, sub microsecond latencies.
- Compared against Chronicle’s original open-source Java Queue, the C++ and Rust variants show lower latencies and tighter jitter, with Python queue a little higher reflecting the fact that it is an interpreted language.
Explore new languages
Rust is a rapidly growing systems programming language focusing on safety, speed, and concurrency, and seeing a surge in popularity across many industries.
Build the Python version of Chronicle Queue built directly on C++ version of Queue, which is binary compatible with the Java version, allowing interoperability between versions.
Get started with Chronicle Queue, using C++. This includes everything from how to write to and read from a Chronicle Queue, to configuring and using Queue.
Trusted by Top-Tier Financial Institutions
Queue Open Source vs Queue Enterprise
|Further Latency Optimisations||No||Yes|
Articles about Chronicle Queue
The Big Question How is Chronicle Queue being used for Big Data solutions in Java, and how does it work under the covers? What is Chronicle Queue? Chronicle Queue is a persisted journal of messages which supports concurrent writers and readers even across multiple JVMs on the same machine. Every reader sees every message, and…
Compared to a year ago, we have significantly improved the throughput at which we can achieve the 99%ile (worst one in 100). What tools and tricks did we use to achieve that? What are we testing? Chronicle Queue appends messages to a file while another thread or process can be reading it. This gives you…
If you use a standard JVM like the Oracle JVM or the OpenJDK, you might find that as the heap size grows the performance of your JVM can drop as GC pause time escalates. This tends to be a problem around 32 GB of heap, but it often depends on the application at which point…