DBMS > etcd vs. Microsoft Azure Table Storage vs. PouchDB vs. SQLite vs. Tibero

System Properties Comparison etcd vs. Microsoft Azure Table Storage vs. PouchDB vs. SQLite vs. Tibero

Editorial information provided by DB-Engines

Name

Description

A distributed reliable key-value store

A Wide Column Store for rapid development using massive semi-structured datasets

JavaScript DBMS with an API inspired by CouchDB

Widely used embeddable, in-process RDBMS

A secure RDBMS, designed for easy portability from Oracle

Primary database model

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

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

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

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

azure.microsoft.com/en-us/services/storage/tables

pouchdb.com

www.sqlite.org

us.tmaxsoft.com/products/tibero

Technical documentation

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

pouchdb.com/guides

www.sqlite.org/docs.html

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Microsoft

Apache Software Foundation

Dwayne Richard Hipp

TmaxSoft

Initial release

2012

2000

2003

Current release

3.4, August 2019

7.1.1, June 2019

3.45.3 (15 April 2024), April 2024

6, April 2015

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Public Domain

commercial

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

JavaScript

C and Assembler

Server operating systems

FreeBSD
Linux
Windows

experimental

hosted

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

server-less

AIX
HP-UX
Linux
Solaris
Windows

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.

yes

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

APIs and other access methods

gRPC
JSON over HTTP

RESTful HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

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++
Java
JavaScript (Node.js)
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

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

View functions in JavaScript

Persistent Stored Procedure (PSM)

Triggers

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

with a proxy-based framework, named couchdb-lounge

none

horizontal partitioning

by range, hash, list or composite

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. Replication either local, cross-facility or geo-redundant.

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

Multi-source replication
Source-replica replication

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

optimistic locking

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 capabilities

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

yes

planned for next version

User concepts

Access control

Access rights based on private key authentication or shared access signatures

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.