vs

Chronicle Map vs LMDB

Chronicle Map: Off-heap, memory-mapped key-value store for Java with microsecond latency and cross-process sharing. LMDB: Tiny memory-mapped B+tree with ACID transactions and lock-free readers; reached 1.0 in 2026.

key differences

  • Transactions: Chronicle Map offers limited ACID; LMDB offers full.
  • Only Chronicle Map has in-memory.
  • Only LMDB has transactions.

choose chronicle-map for

  • +Low-latency reference data and order-book state in trading systems
  • +Sharing state between JVM processes on one host
  • +Large off-heap caches that survive restarts

best at · Cache, Tick data, Embedded

choose lmdb for

  • +Read-heavy embedded indexes and caches
  • +Directory services (OpenLDAP back-mdb)
  • +Blockchain and wallet state
  • +ML dataset storage with fast random reads

best at · Embedded, Metadata, Local-first

overview
Primary model
Key-Value
Key-Value
Also supports
–
–
Type
Embedded library
Embedded library
Status
Active
Active
Developer
Chronicle Software
Symas Corporation / OpenLDAP Project
First release
2014
2011
Latest version
2026.1 (Jan 29, 2026)
1.0.2 (Sep 8, 2026)
License
Open source (permissive)Apache License 2.0
Open source (permissive)OpenLDAP Public License 2.8
Free tier
✓
✓
popularity
WhichDB Score
8.7
39.7
Rank
#321
#47
GitHub stars
3K
3.1K
Stack Overflow questions
122
260
scale & guarantees
Comfortable data size
Medium (≤ 10 TB)
Medium (≤ 10 TB)
Horizontal scaling
None
None
Multi-region
None
None
ACID
Limited
Full
Consistency
Strong
Strong
Schema
Flexible
Schemaless
Architecture
Embedded, In memory
Embedded
deployment
Self-hosted
✓
✓
Vendor-managed cloud
—
—
Serverless
—
—
Embedded
✓
✓
Edge
—
—
Clouds
–
–
capabilities
Transactions
—
✓
Joins
—
—
Secondary indexes
—
—
Full-text search
—
—
Vector search
—
—
Geospatial
—
—
JSON
—
—
Change data capture
—
—
Triggers
—
—
Stored procedures
—
—
Materialized views
—
—
TTL / expiry
—
—
Pub/Sub
—
—
Columnar storage
—
—
In-memory
✓
—
Durable persistence
✓
✓
Compression
—
—
Encryption at rest
—
—
Role-based access
—
—
Time travel
—
—
Branching
—
—
Online schema changes
—
—
Streaming ingest
—
—
Offline sync
—
—
Runs in WebAssembly
—
—
interfaces
Query languages
Java Map API
C API
Client languages
Java
C, C++, Python, Go, Rust, Java, JavaScript
Best for
Cache, Tick data, Embedded
Embedded, Metadata, Local-first

Chronicle Map vs LMDB: FAQ

What is the difference between Chronicle Map and LMDB?

Chronicle Map: Off-heap, memory-mapped key-value store for Java with microsecond latency and cross-process sharing. LMDB: Tiny memory-mapped B+tree with ACID transactions and lock-free readers; reached 1.0 in 2026. Transactions: Chronicle Map offers limited ACID; LMDB offers full. Only Chronicle Map has in-memory. Only LMDB has transactions.

When should I choose Chronicle Map over LMDB?

Choose Chronicle Map for low-latency reference data and order-book state in trading systems; sharing state between JVM processes on one host; and large off-heap caches that survive restarts. Choose LMDB for read-heavy embedded indexes and caches; directory services (OpenLDAP back-mdb); and blockchain and wallet state.

Is Chronicle Map or LMDB more popular?

LMDB ranks #47 on the WhichDB Score (39.7/100) and Chronicle Map ranks #321 (8.7/100). Popularity is not fit: check the requirements that matter for your project.

Are Chronicle Map and LMDB open source?

Yes. Chronicle Map is open source. License: Apache License 2.0. Yes. LMDB is open source. License: OpenLDAP Public License 2.8.