DBMS > etcd vs. RavenDB vs. RocksDB vs. Spark SQL vs. TerarkDB

System Properties Comparison etcd vs. RavenDB vs. RocksDB vs. Spark SQL vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

Open Source Operational and Transactional Enterprise NoSQL Document Database

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Spark SQL is a component on top of 'Spark Core' for structured data processing

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

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

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

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

ravendb.net

rocksdb.org

spark.apache.org/sql

github.com/bytedance/terarkdb

Technical documentation

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

ravendb.net/docs

github.com/facebook/rocksdb/wiki

spark.apache.org/docs/latest/sql-programming-guide.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Hibernating Rhinos

Facebook, Inc.

Apache Software Foundation

ByteDance, originally Terark

Initial release

2010

2013

2014

2016

Current release

3.4, August 2019

5.4, July 2022

8.11.4, April 2024

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

AGPL version 3, commercial license available

Open Source

BSD

Open Source

Apache 2.0

commercial

restricted open source version available

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++

Scala

C++

Server operating systems

FreeBSD
Linux
Windows

experimental

Linux
macOS
Raspberry Pi
Windows

Linux

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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

SQL

Support of SQL

SQL-like query language (RQL)

SQL-like DML and DDL statements

APIs and other access methods

gRPC
JSON over HTTP

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

C++ API
Java API

JDBC
ODBC

C++ API
Java API

Supported programming languages

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

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Java
Python
R
Scala

C++
Java

Server-side scripts

Stored procedures

yes

Triggers

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

yes, utilizing Spark Core

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.

Multi-source replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

Transaction concepts

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

ACID, Cluster-wide transaction available

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

User concepts

Access control

Authorization levels configured per client per database

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.