OpenHFT/Chronicle-Queue

Health v2 · maintenance only

Flags: no_readme

Adoption not part of the score

3815 stars · 567 forks observed · 2026-09-24

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Chronicle Queue is a Java library providing microsecond-latency, persisted messaging that stores every message to disk in an append-only, zero-GC format. It supports deterministic replay and high-throughput inter-process communication, with an enterprise edition adding replication and cross-language support.

Use cases

• persist millions of messages per second to disk with microsecond latency
• build event-sourced systems with deterministic replay of all messages
• share data between JVM processes with low-latency IPC
• capture audit logs where every message must be durably recorded
• eliminate GC pauses from a trading system's critical path
• replay market data feeds for backtesting

When to choose

• you need durable, append-only messaging with consistent single-digit microsecond latencies on the JVM
• you require complete auditability and replay of every message
• you're building low-latency trading or financial systems in Java
• you need high-throughput IPC between processes without a network hop

When to avoid

• you need a distributed broker with multi-language clients out of the box (community edition is Java-centric)
• your throughput needs are modest and a standard message broker like Kafka or RabbitMQ suffices
• you need flexible consumer semantics like competing consumers or per-message acknowledgments
• your data is small-volume and a database or log file is enough

Facets

library · maturity stable

message-queue serialization logging caching fintech performance developer-tools jvm windows low-latency persisted-messaging zero-gc event-sourcing off-heap microsecond-latency messaging linux macos

Member repositories

For agents

markdown · JSON · MCP: product_card(name="OpenHFT/Chronicle-Queue")