DBMS > Amazon CloudSearch vs. Google Cloud Datastore vs. H2 vs. Microsoft Azure Cosmos DB vs. Sequoiadb

System Properties Comparison Amazon CloudSearch vs. Google Cloud Datastore vs. H2 vs. Microsoft Azure Cosmos DB vs. Sequoiadb

Editorial information provided by DB-Engines

Name

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

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.

Globally distributed, horizontally scalable, multi-model database service

NewSQL database with distributed OLTP and SQL

Primary database model

Search engine

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.81
Rank	#137	Overall
	#12	Search engines

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

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

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Website

aws.amazon.com/cloudsearch

cloud.google.com/datastore

www.h2database.com

azure.microsoft.com/services/cosmos-db

www.sequoiadb.com

Technical documentation

docs.aws.amazon.com/cloudsearch

cloud.google.com/datastore/docs

www.h2database.com/html/main.html

learn.microsoft.com/azure/cosmos-db

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

Amazon

Google

Thomas Mueller

Microsoft

Sequoiadb Ltd.

Initial release

2012

2008

2005

2014

2013

Current release

2.2.220, July 2023

License

Commercial or Open Source

commercial

Open Source

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

commercial

Open Source

Server: AGPL; Client: Apache V2

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

hosted

All OS with a Java VM

hosted

Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

yes

JSON types

yes

oid, date, timestamp, binary, regex

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.

Secondary indexes

yes

all search fields are automatically indexed

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

SQL-like query language

APIs and other access methods

HTTP API

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

JDBC
ODBC

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

proprietary protocol using JSON

Supported programming languages

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

Java

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

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

using Google App Engine

Java Stored Procedures and User-Defined Functions

JavaScript

Triggers

Callbacks using the Google Apps Engine

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

Multi-source replication using Paxos

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

yes

Implicit feature of the cloud service

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual 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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Document is locked during a transaction

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

authentication via encrypted signatures

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

simple password-based access control

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.