DBMS > GridGain vs. Microsoft Azure Cosmos DB vs. Microsoft Azure SQL Database vs. Realm

System Properties Comparison GridGain vs. Microsoft Azure Cosmos DB vs. Microsoft Azure SQL Database vs. Realm

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Globally distributed, horizontally scalable, multi-model database service

Database as a Service offering with high compatibility to Microsoft SQL Server

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Primary database model

Key-value store
Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Document store

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	1.53
Rank	#155	Overall
	#26	Key-value stores
	#73	Relational DBMS

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

Score	78.40
Rank	#15	Overall
	#10	Relational DBMS

Score	7.71
Rank	#52	Overall
	#9	Document stores

Website

www.gridgain.com

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/products/azure-sql/database

realm.io

Technical documentation

www.gridgain.com/docs/index.html

learn.microsoft.com/azure/cosmos-db

docs.microsoft.com/en-us/azure/azure-sql

realm.io/docs

Developer

GridGain Systems, Inc.

Microsoft

Realm, acquired by MongoDB in May 2019

Initial release

2007

2014

2010

2014

Current release

GridGain 8.5.1

V12

License

Commercial or Open Source

commercial

Open Source

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

C++

Server operating systems

Linux
OS X
Solaris
Windows

hosted

Android
Backend: server-less
iOS
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

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

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

ADO.NET
JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

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

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

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

JavaScript

Transact SQL

runs within the applications so server-side scripts are unnecessary

Triggers

yes (cache interceptors and events)

JavaScript

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

Implicit feature of the cloud service

yes, with always 3 replicas available

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

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

In-Memory realm

User concepts

Access control

Security Hooks for custom implementations

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

yes

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.