What is Chronicle Queue?
This memory mapped file is also used for exceptionally fast interprocess communication (IPC) without affecting your system performance. This is especially useful when there is a need to transfer large amounts of data, its ideal for transferring data between processes very quickly on the same server or across the network. There is no Garbage Collection (GC) as everything is done 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
Chronicle Queue Features
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.
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.
Our partners
We partner with some of the industry's most trusted brands
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.