Checkpoints[07]

Compression[08]

SequoiaDB uses BSON (binary JSON) format to encode and store JSON format data.

Concurrency Control[09]

SequoiaDB implements transactions, but does not support concurrency control options. Transactions are limited to only include record insert, delete, update, and query (read) operations. Other database operations such as creating new index are not supported in transactions and will not be logged as part of the transaction.

Data Model[10][11]

SequoiaDB supports relational, semi-structured (e.g. JSON), and unstructured (e.g. POSIX file) data models. Data model in storage is JSON.

Indexes[11][12]

Indexes in SequoiaDB use conventional B-trees. An index has a unique name for the index on the data collection and a JSON object that defines the indexing criteria and direction. Indexes can be unique or non-unique. If an index is unique, it can be null-able or non-null-able.

In addition to regular indexes, SequoiaDB supports full-text searching via Elasticsearch.

Isolation Levels[13]

SequoiaDB supports three levels of isolation - read uncommitted, read committed, and read stability. By default, the system is configured as read uncommitted.

Logging[14][07][15]

The system implements logical logging and log replay to support data consistency across distributed replicas.

Parallel Execution[16]

Parallel query execution is supported via individual query configuration.

Query Interface[17]

Storage Architecture[18][17]

If the system is deployed on distributed clusters, it can be configured with either range-based or hash-based sharding.

Storage Model[19][17]

SequoiaDB uses a JSON format record as a unit of data storage. These records are stored in collections. Collections are stored in "collection spaces".

Stored Procedures[20][21]

SequoiaDB supports creating and executing custom procedures via JavaScript-like syntax in SequoiaDB Shell.

System Architecture[11]

The system is configurable to deploy on a single node or on multiple distributed nodes. In a distributed environment, coordination nodes and catalog nodes share disk space, while storage nodes are given separate disk space. The storage nodes can be configured to share disk or each to be given nonshared disk.