openhft/chronicle-queue

Micro second messaging that stores everything to disk

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 38 minutes ago
Added to GitGenius on September 18th, 2026
Created on June 2nd, 2013
Open Issues & Pull Requests: 50 (+0)
GitHub issues: Enabled
Number of forks: 568
Total Stargazers: 3,815 (+0)
Total Subscribers: 164 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 42.1 hours
Mean response time: 215.6 days
90th percentile: 1343.3 days
Tracked items: 19

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 669 days
Stale 30+ days: 4
Stale 90+ days: 3

Recent activity

Opened in 7 days: 0
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • review (9)

Most active issues this week

Detailed Description

Chronicle Queue is a broker-less, off-heap Java library for ultra-low-latency persisted messaging.

Chronicle Queue addresses the challenge of building high-performance, memory-intensive applications in Java by eliminating garbage collection pauses through off-heap storage. Messages are stored entirely to disk, enabling applications to achieve microsecond-level latencies while maintaining persistence. The tool supports multiple concurrent writers through locking and lock-less concurrent readers, allowing messages to be appended, tailed, and randomly accessed within a single queue.

Chronicle Queue suits applications where garbage collection pauses are unacceptable and microsecond-level latency is critical. It works well for distributed systems that need durable, asynchronous messaging without a separate broker, and for scenarios involving high-frequency data processing or financial systems where both performance and message persistence are essential. The tool is particularly valuable when building memory-intensive applications where traditional Java queues would introduce unacceptable GC overhead.

The project maintains active development with regular updates to its codebase. The maintainers respond to issues and pull requests, indicating ongoing engagement with the user community. Documentation is kept current alongside code changes, and the project provides multiple communication channels including a Gitter chat room for user support.