DBMS > Amazon CloudSearch vs. EsgynDB vs. Google Cloud Datastore vs. Microsoft Azure Cosmos DB vs. TinkerGraph

System Properties Comparison Amazon CloudSearch vs. EsgynDB vs. Google Cloud Datastore vs. Microsoft Azure Cosmos DB vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Globally distributed, horizontally scalable, multi-model database service

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

Primary database model

Search engine

Relational DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Graph 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	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

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

Score	0.13
Rank	#345	Overall
	#35	Graph DBMS

Website

aws.amazon.com/cloudsearch

www.esgyn.cn

cloud.google.com/datastore

azure.microsoft.com/services/cosmos-db

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

Technical documentation

docs.aws.amazon.com/cloudsearch

cloud.google.com/datastore/docs

learn.microsoft.com/azure/cosmos-db

Developer

Amazon

Esgyn

Google

Microsoft

Initial release

2012

2015

2008

2014

2009

License

Commercial or Open Source

commercial

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

C++, Java

Java

Server operating systems

hosted

Linux

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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.

Secondary indexes

yes

all search fields are automatically indexed

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language (GQL)

SQL-like query language

APIs and other access methods

HTTP API

ADO.NET
JDBC
ODBC

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

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

TinkerPop 3

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

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

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

Groovy
Java

Server-side scripts

Stored procedures

Java Stored Procedures

using Google App Engine

JavaScript

Triggers

Callbacks using the Google Apps Engine

JavaScript

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

Multi-source replication between multi datacenters

Multi-source replication using Paxos

yes

Implicit feature of the cloud service

none

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

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.

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

authentication via encrypted signatures

fine grained access rights according to SQL-standard

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

Access rights can be defined down to the item level

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.