tidwall/buntdb

BuntDB is an embeddable, in-memory key/value database for Go with custom indexing and geospatial support

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 14th, 2026
Created on July 19th, 2016
Open Issues & Pull Requests: 32 (+0)
GitHub issues: Enabled
Number of forks: 311
Total Stargazers: 4,870 (+0)
Total Subscribers: 109 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 45.1 hours
Mean response time: 13.8 days
90th percentile: 39.5 days
Tracked items: 3

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 500 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

BuntDB is an embeddable, in-memory key/value database for Go with custom indexing and geospatial support.

BuntDB addresses the need for a fast, reliable embedded database by storing all data in memory while persisting to disk in an append-only format. It provides ACID semantics through transaction support, allowing multiple concurrent read transactions but enforcing a single writer at a time via locking. The tool supports spatial indexing across up to twenty dimensions, making it suitable for geospatial queries, and allows custom indexes on JSON fields and arbitrary data types. Built-in index types for strings, integers, and floats enable quick setup, while flexible iteration supports ascending, descending, and range-based queries.

BuntDB suits Go projects that prioritize speed and can accept the memory overhead of in-memory storage. It works well for applications needing an embedded database without external dependencies, particularly those handling geospatial data or requiring custom indexing logic. The tool is ideal when data size remains manageable in RAM and durability matters enough to justify disk persistence. Projects should choose BuntDB when they value simplicity and performance over the scalability of larger distributed systems.

The project maintains a straightforward codebase with focused development. Commits are infrequent but address specific issues and feature requests when they arise. The maintainer responds to reported problems and accepts pull requests that align with the project's scope. Documentation is comprehensive, covering all major features through the README and API documentation. The project remains stable with minimal breaking changes, suggesting a mature tool that prioritizes backward compatibility.