DBMS > etcd vs. Google Cloud Firestore vs. GridGain vs. Snowflake vs. TerarkDB

System Properties Comparison etcd vs. Google Cloud Firestore vs. GridGain vs. Snowflake vs. TerarkDB

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.

GridGain is an in-memory computing platform, built on Apache Ignite

Cloud-based data warehousing service for structured and semi-structured data

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Key-value store

Document store

Key-value store
Relational DBMS

Relational DBMS

Key-value store

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

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

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

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

firebase.google.com/products/firestore

www.gridgain.com

www.snowflake.com

github.com/bytedance/terarkdb

Technical documentation

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

firebase.google.com/docs/firestore

www.gridgain.com/docs/index.html

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Google

GridGain Systems, Inc.

Snowflake Computing Inc.

ByteDance, originally Terark

Initial release

2017

2007

2014

2016

Current release

3.4, August 2019

GridGain 8.5.1

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

restricted open source version available

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

Java, C++, .Net

C++

Server operating systems

FreeBSD
Linux
Windows

experimental

hosted

Linux
OS X
Solaris
Windows

hosted

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

gRPC
JSON over HTTP

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

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

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

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

yes (compute grid and cache interceptors can be used instead)

user defined functions

Triggers

yes, watching key changes

yes, with Cloud Functions

yes (cache interceptors and events)

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

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.

Multi-source replication

yes (replicated cache)

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

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

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.

Security Hooks for custom implementations

Users with fine-grained authorization concept, user roles and pluggable authentication

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.