DBMS > etcd vs. Google Cloud Datastore vs. Hazelcast vs. SAP HANA vs. UniData,UniVerse

System Properties Comparison etcd vs. Google Cloud Datastore vs. Hazelcast vs. SAP HANA vs. UniData,UniVerse

Editorial information provided by DB-Engines

Name

Description

A distributed reliable key-value store

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

A widely adopted in-memory data grid

In-memory, column based data store. Available as appliance or cloud service

MultiValue database and application server with SQL mapping layer and meta database capabilities

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	3.16
Rank	#97	Overall
	#2	Multivalue DBMS

Website

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

cloud.google.com/datastore

hazelcast.com

www.sap.com/products/hana.html

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-unidata

Technical documentation

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

cloud.google.com/datastore/docs

hazelcast.org/imdg/docs

help.sap.com/hana

docs.rocketsoftware.com/bundle?cluster=true&labelkey=unidata&labelkey=prod_unidata

Developer

Google

Hazelcast

SAP

Rocket Software

Initial release

2008

2010

1985

Current release

3.4, August 2019

5.3.6, November 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Server operating systems

FreeBSD
Linux
Windows

experimental

hosted

All OS with a Java VM

Appliance or cloud-service

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes, details here

yes

optional

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

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like query language

yes

APIs and other access methods

gRPC
JSON over HTTP

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

JCache
JPA
Memcached protocol
RESTful HTTP API

JDBC
ODBC

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

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

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

.Net
Basic

U2 Basic
C
Java

Server-side scripts

Stored procedures

using Google App Engine

yes

Event Listeners, Executor Services

SQLScript, R

yes

Triggers

yes, watching key changes

Callbacks using the Google Apps Engine

yes

Events

yes

U2 Basic

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 using Paxos

yes

Replicated Map

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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 or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

one or two-phase-commit; repeatable reads; read commited

ACID

configurable

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

Role-based access control

yes

Access rights according to SQL-standard and operating system based

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.