DBMS > etcd vs. EventStoreDB vs. Microsoft Azure Cosmos DB vs. Tarantool vs. TinkerGraph

System Properties Comparison etcd vs. EventStoreDB vs. Microsoft Azure Cosmos DB vs. Tarantool vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

A distributed reliable key-value store

Industrial-strength, open-source database solution built from the ground up for event sourcing.

Globally distributed, horizontally scalable, multi-model database service

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

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Key-value store

Event Store

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Key-value store
Relational DBMS

Graph DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

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

Score	1.14
Rank	#181	Overall
	#1	Event Stores

Score	29.85
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	1.67
Rank	#150	Overall
	#25	Document stores
	#25	Key-value stores
	#69	Relational DBMS

Score	0.12
Rank	#344	Overall
	#34	Graph DBMS

Website

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

www.eventstore.com

azure.microsoft.com/services/cosmos-db

www.tarantool.io

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

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

developers.eventstore.com

learn.microsoft.com/azure/cosmos-db

www.tarantool.io/en/doc

Developer

Event Store Limited

Microsoft

Initial release

2012

2014

2008

2009

Current release

3.4, August 2019

21.2, February 2021

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

commercial

Open Source

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

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C and C++

Java

Server operating systems

FreeBSD
Linux
Windows

experimental

Linux
Windows

hosted

BSD
Linux
macOS

Data scheme

schema-free

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

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

yes

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

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

Full-featured ANSI SQL support

APIs and other access methods

gRPC
JSON over HTTP

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Open binary protocol

TinkerPop 3

Supported programming languages

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

Groovy
Java

Server-side scripts

Stored procedures

JavaScript

Lua, C and SQL stored procedures

Triggers

yes, watching key changes

JavaScript

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

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

yes

Implicit feature of the cloud service

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

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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

none

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

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

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

optional

In-memory capabilities

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

yes, full featured in-memory storage engine with persistence

yes

User concepts

Access control

Access rights can be defined down to the item level

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.