DBMS > Ehcache vs. Google Cloud Bigtable vs. SingleStore vs. Snowflake

System Properties Comparison Ehcache vs. Google Cloud Bigtable vs. SingleStore vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

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

Primary database model

Key-value store

Key-value store
Wide column store

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	4.79
Rank	#66	Overall
	#8	Key-value stores

Score	2.97
Rank	#92	Overall
	#15	Key-value stores
	#8	Wide column stores

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

www.ehcache.org

cloud.google.com/bigtable

www.singlestore.com

www.snowflake.com

Technical documentation

www.ehcache.org/documentation

cloud.google.com/bigtable/docs

docs.singlestore.com

docs.snowflake.net/manuals/index.html

Developer

Terracotta Inc, owned by Software AG

Google

SingleStore Inc.

Snowflake Computing Inc.

Initial release

2009

2015

2013

2014

Current release

3.10.0, March 2022

8.5, January 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

free developer edition available

commercial

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++, Go

Server operating systems

All OS with a Java VM

hosted

Linux

64 bit version required

hosted

Data scheme

schema-free

yes

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

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

but no triggers and foreign keys

yes

APIs and other access methods

JCache

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

Java

C#
C++
Go
Java
JavaScript (Node.js)
Python

Bash
C
C#
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

Cache Event Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

hash partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Internal replication in Colossus, and regional replication between two clusters in different zones

Source-replica replication

stores two copies of each physical data partition on two separate nodes

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

supports JTA and can work as an XA resource

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

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 (IAM)

Fine grained access control via users, groups and roles

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.