DBMS > etcd vs. Firebase Realtime Database vs. PostGIS vs. SQLite vs. Yanza

System Properties Comparison etcd vs. Firebase Realtime Database vs. PostGIS vs. SQLite vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Spatial extension of PostgreSQL

Widely used embeddable, in-process RDBMS

Time Series DBMS for IoT Applications

Primary database model

Secondary database models

Relational DBMS

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

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

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

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

firebase.google.com/products/realtime-database

postgis.net

www.sqlite.org

yanza.com

Technical documentation

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

firebase.google.com/docs/database

postgis.net/documentation

www.sqlite.org/docs.html

Developer

Google

acquired by Google 2014

Dwayne Richard Hipp

Yanza

Initial release

2012

2005

2000

2015

Current release

3.4, August 2019

3.4.2, February 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL v2.0

Open Source

Public Domain

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Server operating systems

FreeBSD
Linux
Windows

experimental

hosted

server-less

Windows

Data scheme

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

yes

SQL-92 is not fully supported

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

HTTP API

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

limited functionality with using 'rules'

user defined functions

Triggers

yes, watching key changes

Callbacks are triggered when data changes

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

yes

based on PostgreSQL

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

based on PostgreSQL

none

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

Immediate Consistency

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

yes

based on PostgreSQL

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.