Concurrency Control

Not Supported

SwayDB assumes it runs 'under a single process in a single application', as the author clarifies on Reddit. Everything is atomic in SwayDB, including transactions. The only guarantee it has on transactions is atomicity. No concurrency control is needed, and indeed it is not mentioned in docs at all.

Query Interface

Custom API

SwayDB is used embedded in applications. The API is in Scala with its custom APIs. A Java wrapper is also implemented for Java APIs.

Compression

Naïve (Page-Level)

SwayDB supports compressing segments using LZ4 and Snappy, which are open-sourced Java compression tools.

Logging

Physical Logging

Write ahead logging is used for its persistent version databases. Because it is a key-value store, it does not have the notion of pages. The logs are physical logging of write operations.

Indexes

Log-Structured Merge Tree

SwayDB organizes data in levels of segments, using the Log-Structured Merge Tree data structure. Upper levels write to lower levels in batches when it is full or the user explicitly demanded.

Checkpoints

Not Supported

No checkpoints are supported. For its in-memory implementation, no checkpoint or logging is supported. For the persistent version, it can persist its memory segments to disk, but this is used for reducing memory, but not for recovery.

Foreign Keys

Not Supported

Data Model

Key/Value

SwayDB is a key-value store, having Map[K, V] and Set[T] for data storage and providing APIs to create, read, stream, update, delete & expire data.

Isolation Levels

Serializable

Since every operation is atomic and runs on the same memory space, it is serializable.