DBMS > GridGain vs. HugeGraph vs. Microsoft Azure Cosmos DB vs. Yaacomo

System Properties Comparison GridGain vs. HugeGraph 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

GridGain is an in-memory computing platform, built on Apache Ignite

A fast-speed and highly-scalable Graph DBMS

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
Relational DBMS

Graph DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	0.17
Rank	#335	Overall
	#31	Graph DBMS

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

Website

www.gridgain.com

github.com/hugegraph
hugegraph.apache.org

azure.microsoft.com/services/cosmos-db

yaacomo.com

Technical documentation

www.gridgain.com/docs/index.html

hugegraph.apache.org/docs

learn.microsoft.com/azure/cosmos-db

Developer

GridGain Systems, Inc.

Baidu

Microsoft

Q2WEB GmbH

Initial release

2007

2018

2014

2009

Current release

GridGain 8.5.1

0.9

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

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, C++, .Net

Java

Server operating systems

Linux
OS X
Solaris
Windows

Linux
macOS
Unix

hosted

Android
Linux
Windows

Data scheme

yes

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

Secondary indexes

yes

also supports composite index and range index

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

SQL-like query language

yes

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Java API
RESTful HTTP API
TinkerPop Gremlin

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

JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

Groovy
Java
Python

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

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

asynchronous Gremlin script jobs

JavaScript

Triggers

yes (cache interceptors and events)

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

depending on used storage backend, e.g. Cassandra and HBase

Sharding

Implicit feature of the cloud service

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

depending on used storage backend, e.g. Cassandra and HBase

yes

Implicit feature of the cloud service

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

via hugegraph-spark

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

edges in graph

yes

Transaction concepts

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

ACID

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

Security Hooks for custom implementations

Users, roles and permissions

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.