LOW-LATENCY MESSAGING FRAMEWORK

Chronicle Queue Enterprise

Chronicle Queue is a leading choice for organisations seeking a low-latency, high-performance messaging framework.

The Chronicle Queue Enterprise version eliminates compatibility issues and allows for the seamless integration and sharing of data between Java, Rust, Python and C++ libraries.

"I am an admirer of all things Chronicle, I can honestly say, Chronicle Queue changed my entire perspective"

- Nicholas Whitehead, DriveWealth

Eliminate Compatibility Issue with Chronicle Queue Enterprise

  • 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.
Feature Open Source Enterprise
Low Latency Yes Yes
Replay Strategies Yes Yes
TCP/IP Replication No Yes
Expert Support No Yes
Timezone Rolling No Yes
Further Latency Optimisations No Yes

Multilanguage Support

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.

java-logo-black-and-white-1
c-logo-black-and-white
python-logo-black-and-white-1
rust

Multilanguage Support

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.

java-logo-black-and-white-1
c-logo-black-and-white
python-logo-black-and-white-1
rust

Multilanguage Support

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.

Screenshot 2024-02-09 at 14.09.45

Download Languages

C++

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. 

RUST

Rust is a rapidly growing systems programming language focusing on safety, speed, and concurrency, and seeing a surge in popularity across many industries.

PYTHON

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.

Trusted by Top-Tier Financial Institutions

uob
hsbc-logo-black-and-white
mufg-logo-black-and-white-1
StoneXRTM_edge
GET STARTED

Speak To An Expert

We are seeing a rise in demand for offering our products in a range of languages. Book a free demo today for Chronicle Queue Enterprise, or our other products that are offered in different languages.

Screenshot 2023-06-28 at 10.42.33 AM

Articles About Chronicle Queue

Reducing Tail Latencies with Chronicle Queue Enterprise

Persistent queue solutions are frequently used when designing low-latency applications. The problem is that high sustained message rates, or bursty workloads, can lead to delays caused by the OS or hardware which are challenging to mitigate. In this article, we will describe how Chronicle Queue Enterprise solves this. Background When benchmarking Java low-latency persistent queue…

Continue Reading >>

Big Data and 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…

Continue Reading >>

Chronicle Queue storing 1TB in virtual memory on a 128GB machine

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…

Continue Reading >>