DBMS > etcd vs. Google Cloud Firestore vs. Infobright vs. RocksDB

System Properties Comparison etcd vs. Google Cloud Firestore vs. Infobright vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

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

Primary database model

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

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

Score	8.96
Rank	#48	Overall
	#8	Document stores

Score	1.00
Rank	#193	Overall
	#90	Relational DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Website

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

firebase.google.com/products/firestore

ignitetech.com/softwarelibrary/infobrightdb

rocksdb.org

Technical documentation

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

firebase.google.com/docs/firestore

github.com/facebook/rocksdb/wiki

Developer

Google

Ignite Technologies Inc.; formerly InfoBright Inc.

Facebook, Inc.

Initial release

2017

2005

2013

Current release

3.4, August 2019

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

BSD

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

C++

Server operating systems

FreeBSD
Linux
Windows

experimental

hosted

Linux
Windows

Linux

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

Knowledge Grid Technology used instead

SQL

Support of SQL

yes

APIs and other access methods

gRPC
JSON over HTTP

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

ADO.NET
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

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

Triggers

yes, watching key changes

yes, with Cloud Functions

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

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

Multi-source replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

ACID

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.