DBMS > Ehcache vs. Google Cloud Firestore vs. Snowflake vs. TerarkDB vs. Vitess

System Properties Comparison Ehcache vs. Google Cloud Firestore vs. Snowflake vs. TerarkDB vs. Vitess

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

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.

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

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

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

www.ehcache.org

firebase.google.com/products/firestore

www.snowflake.com

github.com/bytedance/terarkdb

vitess.io

Technical documentation

www.ehcache.org/documentation

firebase.google.com/docs/firestore

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

vitess.io/docs

Developer

Terracotta Inc, owned by Software AG

Google

Snowflake Computing Inc.

ByteDance, originally Terark

The Linux Foundation, PlanetScale

Initial release

2009

2017

2014

2016

2013

Current release

3.10.0, March 2022

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

restricted open source version available

Open Source

Apache Version 2.0, commercial licenses 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++

Server operating systems

All OS with a Java VM

hosted

Docker
Linux
macOS

Data scheme

schema-free

yes

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

schema-free

yes

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

yes

with proprietary extensions

APIs and other access methods

JCache

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

CLI Client
JDBC
ODBC

C++ API
Java API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Java

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

JavaScript (Node.js)
Python

C++
Java

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

user defined functions

yes

proprietary syntax

Triggers

yes

Cache Event Listeners

yes, with Cloud Functions

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

yes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Multi-source replication

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

supports JTA and can work as an XA resource

yes

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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.

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

Users with fine-grained authorization concept

no user groups or roles

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.