Checkpoints

Non-Blocking

The user has the option to toggle the flag SyncWrites, to determine how immediately an update is propagated to disk. If SyncWrite is false, writes may not sync to disk immediately and the database might have to be closed before the changes are propagated to disk. In addition to changes being propagate to disk on Close(), changes are also propagated when MaxTableSize is reached.

Compression

Delta Encoding

BadgerDB uses delta encoding to reduce the size of keys, to further reduce the size of the LSMs. Also, during a read, a fingerprint of the key is stored rather than the key itself to also save space. The fingerprint of a key contains the information necessary to identify a unique key, but takes up less space. It is not a 100% accurate and can cause a false negative causing a transaction to abort (and requiring it to be restarted).

Logging

Physical Logging

BadgerDB seems to support Write-Ahead Logging (WAL), and after a crash, it iterates over recent updates (logged in disk) and re-applies them. To prevent iterating over the entire WAL, Badger maintains a pointer to the latest log to have been written to disk.

Stored Procedures

Not Supported

Storage Architecture

Disk-oriented In-Memory

BadgerDB is an in-memory DBMS, that supports larger-than-memory databases by writing to disk. Disk is also used to make the BadgerDB persistent and resilient. BadterDB works in-memory until the MaxTableSize is reached, at which point the data is propagated to disk. A database is retrieved from and written on disk upon Open() and Close().

System Architecture

Embedded

The documentation states that BadgerDB is an embeddable database management system but does not go into detail.

Storage Model

Custom

The LSM writes the initial in-memory updates in memtables. Once those are full, they are moved over to immutable memtables that are eventually written to disk.

Concurrency Control

Multi-version Concurrency Control (MVCC) Two-Phase Locking (Deadlock Prevention)

Badger supports ACID transactions and Multi-Version Concurrency Control with Snapshot Isolation. Badger acquires locks on directories when accessing data, so multiple processes cannot open the same database at the same time. If the transaction is read-write, the transaction checks if there is a conflict and return and error if there is one.

Data Model

Key/Value

Badger’s underlying functionality is a key-value store. The user can choose to store additional meta-data with the key-value pair for use when processing that data.

Indexes

Log-Structured Merge Tree

BadgerDB supports a LSM tree, where keys are stored in the LSM and values are store in a write-ahead log called a value log. Since key tend to be smaller than values, this allows the system to maintain a smaller LSM tree. The LSM make sure to maintain a sorted order, making range queries easier to process, as well.

Storage Organization

Log-structured Sorted Files

BadgerDB uses a sorted LSMs to support a key-value store storage organization.

Query Interface

Custom API

The query interface for BadgerDB is in Go since the system was originally created to provide a key-value store that can easily be accessed through Go without having to go through Ggo.

Isolation Levels

Serializable Snapshot Isolation

BadgerDB supports snapshot isolation. Badger also has read-only transactions (called Views), that ensures a consistent view of the database system, and that will not include changes made by an uncommitted transaction at the start of this transactions. With read-write transactions, if a conflict occurs, the transaction will written with an error notifying the user of a conflict, giving the user the option to retry the transaction.

Views

Not Supported

Query Execution

Tuple-at-a-Time Model Vectorized Model

BadgerDB is inspired by the simplicity of LevelDB and supports Get, Set, Delete, and Iterate functions. Multiple updates can be batched-up into a single transaction, allowing the user to do a lot of writes at a time.