Menu
Image

Chronicle Queue Backed Map

Chronicle Queue Backed Map serves as a high-performance, drop-in replacement for standard Java Maps, delivering superior speed and zero garbage generation. Leveraging off-heap memory, it enables efficient data sharing between processes on the same host and supports replication for seamless distribution across LAN or WAN environments.

Talk to our team
Image

Key Features

Zero-Compromise Persistence

QBM uses an underlying Chronicle Queue as its persistence backbone. Every map mutation is first appended to the Queue before being reflected in the Map.

Deterministic, Sub-microsecond Latency

By bypassing the JVM heap entirely and using memory-mapped I/O, map read and write operations remain in the nanosecond-to-microsecond range, with no stop-the-world GC pauses.

Replication

Maps are configured as a source or sink, with Chronicle Queue Enterprise replicating the underlying queue over TCP/IP to one or more remote nodes, ensuring that data continuity and throughput are never sacrificed for distribution guarantees.

Consistent State Snapshotting

QBM supports periodic, consistent snapshots of the full Map state, capturing a point-in-time materialised view of the key-value surface without interrupting read/write operations.

Scalability for Large Datasets

Memory-mapped files let you keep vast data sets such as full order books or historical ticks in a single map, limited only by available disk. Grow effortlessly as volumes rise.

Highly Performant

Proven to handle up to 30 million updates per second on a 16-core server with a 64 MB heap. Run real-time pricing, risk, and analytics workloads without costly hardware refreshes.

Technical Information

Explore the advanced engineering principles that shape this product’s core, ensuring exceptional performance, operational resilience, and seamless scalability.

What is a Queue-backed Map?

Chronicle QBM is an ultra-low-latency, highly concurrent key-value store with optional disk persistence and scalable replication.

Read More

Replication

Discover the mechanics and considerations of QBM replication over TCP/IP

Read More

Snapshotting

Capture full Map state in a single Queue event, eliminating unbounded replay on restart.

Read More
Image

Use Cases

Discover how Chronicle helps financial institutions solve real integration, latency, and scalability challenges proven in production environments.

  • QBM in Real-time Risk Systems
  • HA/DR and Replication
  • State Snapshotting & Time-Travel Recovery

QBM in Real-time Risk Systems

A Tier-1 investment bank's risk desk runs a Global Position & Limit Monitoring Engine that must hold the real-time state of hundreds of millions of live positions, Greeks, P&L snapshots, and pre-trade risk limits, all of which must be readable in under a microsecond by downstream systems. A JVM-heap-based store collapses under GC pressure at this scale; a traditional database introduces query latency that makes real-time pre-trade checking impossible.

Image

HA/DR and Replication

QBM's replication model is architected so that Chronicle Queue is the unit of replication, not the Map itself. Changes are appended to the source queue and propagated to sink queues on remote nodes via Chronicle Queue Enterprise's TCP/IP replication layer, which is fully tested against network partitions and ungraceful node shutdowns. Because replication runs asynchronously off the critical Map I/O path, a degraded or failed replica node never introduces latency jitter into the source.

Image

State Snapshotting & Time-Travel Recovery

Because every Map write is first committed as an immutable Queue excerpt, QBM maintains a complete, ordered, replayable history of all state transitions. This means that any prior state of the Map can be reconstructed by replaying the Queue from its genesis (or from a known checkpoint) up to any target timestamp.

Image

Learn more about our offerings

Connect with a Chronicle expert to unlock seamless trading connectivity, elevate performance, and scale with your business.

Talk to our team