DBMS > EJDB vs. etcd vs. SQLite vs. Tarantool

System Properties Comparison EJDB vs. etcd vs. SQLite vs. Tarantool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

A distributed reliable key-value store

Widely used embeddable, in-process RDBMS

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store

Key-value store

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

github.com/Softmotions/ejdb

etcd.io
github.com/etcd-io/etcd

www.sqlite.org

www.tarantool.io

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

www.sqlite.org/docs.html

www.tarantool.io/en/doc

Developer

Softmotions

Dwayne Richard Hipp

Initial release

2012

2000

2008

Current release

3.4, August 2019

3.45.3 (15 April 2024), April 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache Version 2.0

Open Source

Public Domain

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and C++

Server operating systems

server-less

FreeBSD
Linux
Windows

experimental

server-less

BSD
Linux
macOS

Data scheme

schema-free

yes

dynamic column types

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

not rigid because of 'dynamic typing' concept.

string, double, decimal, uuid, integer, blob, boolean, datetime

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

Full-featured ANSI SQL support

APIs and other access methods

in-process shared library

gRPC
JSON over HTTP

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Open binary protocol

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

Lua, C and SQL stored procedures

Triggers

yes, watching key changes

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

none

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

none

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

via file-system locks

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.