DBMS > Ehcache vs. Google Cloud Datastore vs. H2 vs. Microsoft SQL Server vs. TinkerGraph

System Properties Comparison Ehcache vs. Google Cloud Datastore vs. H2 vs. Microsoft SQL Server vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Microsofts flagship relational DBMS

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	5.23
Rank	#68	Overall
	#8	Key-value stores

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	8.22
Rank	#50	Overall
	#32	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	0.12
Rank	#344	Overall
	#34	Graph DBMS

Website

www.ehcache.org

cloud.google.com/datastore

www.h2database.com

www.microsoft.com/en-us/sql-server

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

www.ehcache.org/documentation

cloud.google.com/datastore/docs

www.h2database.com/html/main.html

learn.microsoft.com/en-US/sql/sql-server

Developer

Terracotta Inc, owned by Software AG

Google

Thomas Mueller

Microsoft

Initial release

2009

2008

2005

1989

2009

Current release

3.10.0, March 2022

2.2.220, July 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

dual-licence (Mozilla public license, Eclipse public license)

commercial

restricted free version is available

Open Source

Apache 2.0

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

Java

Server operating systems

All OS with a Java VM

hosted

All OS with a Java VM

Linux
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL-like query language (GQL)

yes

APIs and other access methods

JCache

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

TinkerPop 3

Supported programming languages

Java

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Groovy
Java

Server-side scripts

Stored procedures

using Google App Engine

Java Stored Procedures and User-Defined Functions

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Cache Event Listeners

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

none

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Multi-source replication using Paxos

With clustering: 2 database servers on different computers operate on identical copies of a database

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

none

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Relationships in graphs

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

optional

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 rights according to SQL-standard

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.