DBMS > etcd vs. Firebase Realtime Database vs. SQLite vs. TerminusDB

System Properties Comparison etcd vs. Firebase Realtime Database vs. SQLite vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

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.25
Rank	#54	Overall
	#5	Key-value stores

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

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

firebase.google.com/products/realtime-database

www.sqlite.org

terminusdb.com

Technical documentation

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

firebase.google.com/docs/database

www.sqlite.org/docs.html

terminusdb.github.io/terminusdb/#

Developer

Google

acquired by Google 2014

Dwayne Richard Hipp

DataChemist Ltd.

Initial release

2012

2000

2018

Current release

3.4, August 2019

3.45.3 (15 April 2024), April 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Public Domain

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

FreeBSD
Linux
Windows

experimental

hosted

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

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

Android
iOS
JavaScript API
RESTful HTTP 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

Java
JavaScript
Objective-C

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

limited functionality with using 'rules'

yes

Triggers

yes, watching key changes

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

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

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

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, based on authentication and database rules

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.