DBMS > Google Cloud Bigtable vs. Hazelcast vs. Microsoft Azure Cosmos DB vs. Yaacomo

System Properties Comparison Google Cloud Bigtable vs. Hazelcast vs. Microsoft Azure Cosmos DB vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

A widely adopted in-memory data grid

Globally distributed, horizontally scalable, multi-model database service

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Key-value store
Wide column store

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Spatial DBMS

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

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

Score	5.72
Rank	#59	Overall
	#6	Key-value stores

Score	24.97
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

cloud.google.com/bigtable

hazelcast.com

azure.microsoft.com/services/cosmos-db

yaacomo.com

Technical documentation

cloud.google.com/bigtable/docs

hazelcast.org/imdg/docs

learn.microsoft.com/azure/cosmos-db

Developer

Google

Hazelcast

Microsoft

Q2WEB GmbH

Initial release

2015

2008

2014

2009

Current release

5.3.6, November 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses 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

Server operating systems

hosted

All OS with a Java VM

hosted

Android
Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

the object must implement a serialization strategy

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

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

JCache
JPA
Memcached protocol
RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

JDBC
ODBC

Supported programming languages

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

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

JavaScript

Triggers

yes

Events

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

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

yes

Replicated Map

yes

Implicit feature of the cloud service

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

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

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic single-row operations

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

Multi-item ACID transactions with snapshot isolation within a partition

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

Role-based access control

Access rights can be defined down to the item level

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.