Side by side
Pebble vs Tkrzw
Both stand on embedded databases. Which one you can start free with, which one lets you read the code, and what each costs once you pay.
Free plan Self-hosted
Pebble offers a focused Go storage engine with a substantial listed feature set and CockroachDB production history. It is most appropriate when its narrower scope and compatibility rules match the application.
Visit Pebble Paid LinuxMacSelf-hosted+1
Tkrzw provides a broad DBM toolkit with several storage structures, adapters, indexes, and language interfaces. Build prerequisites and careful database closing are important operational considerations.
Visit TkrzwThe facts
| Pebble | Tkrzw | |
|---|---|---|
| Free plan | Yes | Not published |
| Open source | Not published | Not published |
| Runs on | Self-hosted | Linux, Mac, Self-hosted, Windows |
| Lowest paid plan | Not published | Not published |
| Plans published | None | None |
| Maker | Not published | Not published |
| Website | github.com | dbmx.net |
| On embedded databases | #24 of 30 | #28 of 30 |
Pebble: what it does well
- Open-source BSD-3-Clause license
- Go key-value store for self-hosting
- Checkpoints, snapshots, batches, and compaction
- Used as CockroachDB’s default storage engine
- Production use described at scale
What to know first
- No backups, column families, or transactions
- No universal compaction
- RocksDB compatibility has version limits
- Unsupported RocksDB features may corrupt data
Tkrzw: what it does well
- Multiple file-backed and in-memory database types
- Thread-safe classes for simultaneous access
- Python, Java, Ruby, and Go bindings
- Secondary indexes and database adapters included
- Compression and AES or RC4 options documented
What to know first
- Python binding requires Python 3.6 or later
- Java binding requires JDK 9 or later
- Tkrzw must be installed before language bindings
- Opened databases must be explicitly closed