jankotek/mapdb

MapDB provides concurrent Maps, Sets and Queues backed by disk storage or off-heap-memory. It is a fast and easy to use embedded Java database engine.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Type:Library / SDKCategory(s):NoSQL, Key-Value & CachesDatabases & Storage
Added to GitGenius on September 13th, 2026
Created on August 17th, 2012
Open Issues & Pull Requests: 200 (+0)
GitHub issues: Enabled
Number of forks: 877
Total Stargazers: 5,053 (+0)
Total Subscribers: 298 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.8 days
Mean response time: 316.2 days
90th percentile: 279.4 days
Tracked items: 10

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 12
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 800 days
Stale 30+ days: 12
Stale 90+ days: 10

Recent activity

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

Top labels

  • 3.0 (1)
  • bug (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

MapDB is an embedded Java database engine that provides concurrent Maps, Sets, and Queues backed by disk storage or off-heap memory.

MapDB addresses the need for persistent, high-performance data structures in Java applications by combining an embedded database engine with familiar Java collection interfaces. It allows developers to use Maps, Lists, and Queues that transparently persist to disk or allocate memory outside the Java heap, avoiding garbage collection pauses. The tool supports multiple deployment modes: as a drop-in replacement for standard collections, as an off-heap cache unaffected by garbage collection, as a multilevel cache with expiration and disk overflow capabilities, or as a lightweight relational database alternative with transactions, MVCC, and incremental backups.

MapDB suits applications that need to handle large datasets efficiently without the overhead of a separate database server. It works well for local data processing and filtering tasks where performance matters and garbage collection latency is a concern. The off-heap storage capability makes it particularly valuable for applications managing substantial in-memory collections that would otherwise trigger frequent garbage collection. Developers should choose this tool when they want collection-like semantics with persistence guarantees, or when they need to process huge quantities of data in reasonable time without deploying a full RDBMS.

The project maintains an extensive test suite with over a million test cases, though the default build runs only a tiny fraction to keep build time reasonable. The codebase is written in Kotlin and requires IntelliJ IDEA for development. MapDB comes with comprehensive documentation including a quick start guide and full API documentation available on its website.