Dolt is a single-node DBMS that incorporates Git-style versioning as a first-class entity. Dolt can behave as an RDBMS as it provides a MySQL Server, using the Go implementation (work in progress). Dolt is also a file format as you can write to Dolt through the command line without having the server process running. Dolt behaves like Git, i.e as a content addressable local database where the main objects are tables instead of files. In Dolt, a user creates a repository locally. The repository contains tables that can be read and updated using SQL. Similar to Git, writes are staged until the user issues a commit. Upon commit, the writes are appended to permanent storage. Branch/merge semantics are supported allowing for the tables to evolve at a different pace for multiple users. This allows for loose collaboration on data as well as multiple views on the same core data. Merge conflicts are detected for schema and data conflicts. Data conflicts are cell-based, not line-based. Remote repositories allow for cooperation among repository instances. Clone, push, and pull semantics are all available.
Source control, and particularly Git, enabled a revolution in the way people collaborate when they create software. It did this by providing semantics for building source code in a collaborative and decentralized way. Dolt aims to do this for data to allow people to be able to build relational databases collaboratively. Dolt was created by Liquidata and was open-sourced in late August and is under active development.
Dolt does not support transactions. Concurrent SQL sessions on the same dolt checkout will see read committed, with an auto-commit on each executed SQL statement.
Dolt stores tables in the N-ary Storage Model with clustered primary keys. The entire dataset is content-addressed as a Merkle Tree of component blocks. The boundaries for internal and leaf nodes are chosen by a rolling hash of the block contents.
Dolt does not support transactions. In Dolt's model, concurrent edits take place on separate branches and would be merged by explicit user actions.
Dolt supports iterator based query processing with no intra-query parallelism.
Dolt supports a B+ tree like index structure for table primary keys only.
Dolt uses disk storage. Dolt will eventually support the storage of large datasets across multiple machines. Currently, Dolt can store datasets up to 100GB.
Dolt does not support mutable database files, hence it does not explicitly take checkpoints. Dolt has a manifest to store pointers to all currently active table files which and is updated atomically on every mutation of the database.
Under active development.
Dolt emulates MySQL.
Dolt is not distributed at a system level. Dolt is designed to distribute the same database to multiple locations where it can be worked on in isolation and any edits from one location can be explicitly pulled or pushed to another location. At the checkout level, Dolt databases are shared-nothing.
Dolt uses [Snappy](https://en.wikipedia.org/wiki/Snappy_(compression)) an open-sourced compression library that prioritizes speed over size. All chunks are compressed with Snappy before storage and are decompressed as they are read into the block cache. It is necessary to decompress in order to process queries.
Dolt stores its dataset as a Merkle Tree of component blocks. The content-addressed blocks are stored in write-once table files with a static binary-searchable index at the end. When the table files grow to a number beyond a certain threshold, a compaction phase is run. New data is only written once. It is written to new table files containing the new chunks. These table files are flushed to disk before the manifest referencing them is updated.
Linux, OS X, Windows