Store complete history of all your messages to disk

With Chronicle Queue you are able to persist every single event and message, It records each event to a memory mapped file.

What is Chronicle Queue?

Chronicle Queue is a persisted low-latency messaging framework for high performance and critical applications, it can be used for low latency Interprocess communication (IPC) without affecting your system performance this can be useful when transferring large amounts of data between processes. It is a "record everything store" which can read with microsecond real-time latency and supports even the most demanding low latency trading systems.

Although it is not just limited to trading it can be used in any application where the recording and movement of information is a concern. There is also no Garbage Collection (GC) as everything is off heap.

More information

Getting Started: Technical Guide

GitHub: Source Code

Source Code Documentation: JavaDoc

StackOverflow: Questions

Frequently Asked Questions: Github

Issues: Github

Benchmarks: Click here

Usage: Click here

View Chronicle Queue on GitHub

Chronicle Queue Features

Low-latency, high-performance Java and C++ software

No data loss; stores every value instead of replacing them

No GC as everything is done off-heap

Persistence to disk through memory mapped files

IPC between Java processes or between threads in a Java process

Simple API for ease of use

Replay-ability of all your inputs and outputs

Concurrent writers across processes on the same machine

Embedded performance in all processes

Data is written synchronously to ensure no data is lost

Data is read less than a microsecond after it is written

How does it work?

Chronicle uses a memory mapped file to continuously journal messages, Chronicle's file-based storage will slowly grow in size as more data is written to the queue, the size of the queue can exceed your available memory, you are only constrained by the amount of disk space you have on your server. Chronicle writes data directly into off-heap memory which is shared between java processes on the same server.

Chronicle is very fast, it is able to write and read a message in just two microseconds with no garbage. Typically at the end of each day, you archive the queue and start the next day with a fresh empty queue.

Read the start guide

Get a Free Chronicle Queue Demo

To see Chronicle Queue in action – run this demonstration on your machine. Download the chronicle-demo.jar (executable jar). The jar should be launched with Java 1.7+.

Double click to launch or use the command line java -jar chronicle-demo.jar.

Download Chronicle Queue Demo

Want to learn more? See the benefits of Chronicle's products in action

At Chronicle, we believe less is more. Learn more about why and how Chronicle can support your business and how it can increase efficiency and streamline your systems and workflows by speaking with one of our experts.

We can also offer you our release notes.