DBMS > etcd vs. Memcached vs. PouchDB vs. SQLite vs. TerminusDB

System Properties Comparison etcd vs. Memcached vs. PouchDB vs. SQLite vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

A distributed reliable key-value store

In-memory key-value store, originally intended for caching

JavaScript DBMS with an API inspired by CouchDB

Widely used embeddable, in-process RDBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Document store
RDF store

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

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

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

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

Technical documentation

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

github.com/memcached/memcached/wiki

pouchdb.com/guides

www.sqlite.org/docs.html

terminusdb.github.io/terminusdb/#

Developer

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Apache Software Foundation

Dwayne Richard Hipp

DataChemist Ltd.

Initial release

2003

2012

2000

2018

Current release

3.4, August 2019

1.6.27, May 2024

7.1.1, June 2019

3.46.0 (23 May 2024), May 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

BSD license

Open Source

Public Domain

Open Source

GPL V3

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

JavaScript

Prolog, Rust

Server operating systems

FreeBSD
Linux
Windows

experimental

FreeBSD
Linux
OS X
Unix
Windows

server-less, requires a JavaScript environment (browser, Node.js)

server-less

Linux

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

via views

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

SQL-like query language (WOQL)

APIs and other access methods

gRPC
JSON over HTTP

Proprietary protocol

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

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

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

JavaScript

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

JavaScript
Python

Server-side scripts

Stored procedures

View functions in JavaScript

yes

Triggers

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

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

none

Repcached, a Memcached patch, provides this functionallity

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

in-memory journaling

In-memory capabilities

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

yes

User concepts

Access control

yes

using SASL (Simple Authentication and Security Layer) protocol

Role-based access control

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.