Replicate your Key Value Store across your network, with consistency, persistance and performance.
Switch branches/tags
chronicle-map-3.16.0 chronicle-map-3.15.1 chronicle-map-3.15.0 chronicle-map-3.14.6 chronicle-map-3.14.5 chronicle-map-3.14.4 chronicle-map-3.14.3 chronicle-map-3.14.2 chronicle-map-3.14.1 chronicle-map-3.14.0 chronicle-map-3.13.0 chronicle-map-3.12.0 chronicle-map-3.11.0 chronicle-map-3.10.1 chronicle-map-3.10.0 chronicle-map-3.9.1 chronicle-map-3.9.0 chronicle-map-3.8.0 chronicle-map-3.7.0-rc chronicle-map-3.6.0-rc chronicle-map-3.5.0-rc chronicle-map-3.4.2-beta chronicle-map-3.4.1-beta chronicle-map-3.4.0-beta chronicle-map-3.3.0-beta chronicle-map-3.2.0-beta chronicle-map-3.1.5-alpha chronicle-map-3.1.4-alpha chronicle-map-3.1.2-alpha chronicle-map-3.1.1-alpha chronicle-map-3.1.0-alpha chronicle-map-3.0.3-alpha chronicle-map-3.0.2-alpha chronicle-map-3.0.1-alpha chronicle-map-3.0.0-alpha chronicle-map-2.4.17 chronicle-map-2.4.16 chronicle-map-2.4.15 chronicle-map-2.4.14 chronicle-map-2.4.13 chronicle-map-2.4.12 chronicle-map-2.4.11 chronicle-map-2.4.10 chronicle-map-2.4.9 chronicle-map-2.4.8 chronicle-map-2.4.7 chronicle-map-2.4.6 chronicle-map-2.4.5 chronicle-map-2.4.4 chronicle-map-2.4.3 chronicle-map-2.4.2 chronicle-map-2.4.1 chronicle-map-2.4.0 chronicle-map-2.3.9 chronicle-map-2.3.8 chronicle-map-2.3.7 chronicle-map-2.3.6 chronicle-map-2.3.5 chronicle-map-2.3.4 chronicle-map-2.3.3 chronicle-map-2.3.2 chronicle-map-2.3.1 chronicle-map-2.2.2 chronicle-map-2.2.1 chronicle-map-2.2.0 chronicle-map-2.1.17 chronicle-map-2.1.16 chronicle-map-2.1.15 chronicle-map-2.1.14 chronicle-map-2.1.13 chronicle-map-2.1.12 chronicle-map-2.1.10 chronicle-map-2.1.9 chronicle-map-2.1.8 chronicle-map-2.1.7 chronicle-map-2.1.6 chronicle-map-2.1.5 chronicle-map-2.1.4 chronicle-map-2.1.3 chronicle-map-2.1.2 chronicle-map-2.1.1 chronicle-map-2.1.0 chronicle-map-2.0.22rc6 chronicle-map-2.0.22rc5 chronicle-map-2.0.22rc4 chronicle-map-2.0.22rc3 chronicle-map-2.0.22rc2 chronicle-map-2.0.22rc1 chronicle-map-2.0.21b chronicle-map-2.0.20b chronicle-map-2.0.19b chronicle-map-2.0.18b chronicle-map-2.0.17b chronicle-map-2.0.16b chronicle-map-2.0.15b chronicle-map-2.0.14b chronicle-map-2.0.13b chronicle-map-2.0.12b chronicle-map-2.0.11b chronicle-map-2.0.10b
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.


Chronicle Map

docs\images\Map line




Chronicle Map is a super-fast, in-memory, non-blocking, key-value store, designed for low-latency, and/or multi-process applications such as trading and financial market applications. See Features doc for more information.

The size of a Chronicle Map is not limited by memory (RAM), but rather by the available disk capacity.

docs\images\CM Overview

Use cases

Chronicle Map is used in production around the world for:

  • real-time trading systems. Chronicle Map provides in-memory access speeds, and supports ultra-low garbage collection. Chronicle Map can support the most demanding of applications.

  • highly concurrent systems. Chronicle Map supports multiple readers and writers, distributed across multiple machines.

Why use Chronicle Map?

Chronicle Map is:

  • fast. Millions of operations per second, with low and stable microsecond latencies for reads and writes. Write queries scale well up to the number of hardware execution threads in the server. Read queries never block each other.

  • reliable. Chronicle Software have a “chaos monkey” test which verifies Chronicle Map multi-master replication in the face of node and network failures. The map can optionally be persisted to disk.

  • in production at banks and hedge funds, globally.

  • built using lessons learnt from real-world experience solving real-world problems.

  • open source (standard version), and in use at hundreds of sites around the world.

Our offering

Chronicle Software provides full support for Chronicle Map, consulting to help you make best use of the product, and can also deliver projects using a mix of our resources and your own.

Replication Environment Example

The following diagram shows an example of Chronicle Map replication over three servers (or sites). Chronicle Map Replication is part of Chronicle Map (Enterprise Edition); a commercially supported version of our successful open source Chronicle Map.

docs\images\Configure Three Way Replication

Replication is multi-master, lock-free, redundant, deterministic, and eventually consistent.

The writer can optionally wait for replication to occur across nodes or regions.

See Chronicle Map Replication for more information.


The Chronicle Map documentation comprises:

Table 1. Documentation




Features description.


Replication explanation.




Frequently asked questions.


Downloading the software.


Updates from Chronicle Map version 2.


Compatibility and Versioning description.

Linked documentation is contained in the docs folder.