DBMS > GigaSpaces vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. mSQL

System Properties Comparison GigaSpaces vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. mSQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Globally distributed, horizontally scalable, multi-model database service

A Wide Column Store for rapid development using massive semi-structured datasets

mSQL (Mini SQL) is a simple and lightweight RDBMS

Primary database model

Document store
Object oriented DBMS

Values are user defined objects

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Relational DBMS

Secondary database models

Graph DBMS
Search engine

Spatial DBMS

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

Score	1.02
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

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

Score	4.92
Rank	#73	Overall
	#6	Wide column stores

Score	1.67
Rank	#151	Overall
	#70	Relational DBMS

Website

www.gigaspaces.com

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/services/storage/tables

hughestech.com.au/products/msql

Technical documentation

docs.gigaspaces.com/latest/landing.html

learn.microsoft.com/azure/cosmos-db

Developer

Gigaspaces Technologies

Microsoft

Hughes Technologies

Initial release

2000

2014

2012

1994

Current release

15.5, September 2020

4.4, October 2021

License

Commercial or Open Source

Open Source

Apache Version 2; Commercial licenses available

commercial

free licenses can be provided

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

Server operating systems

Linux
macOS
Solaris
Windows

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
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.

XML can be used for describing objects metadata

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-99 for query and DML statements

SQL-like query language

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

APIs and other access methods

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

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

RESTful HTTP API

JDBC
ODBC

Supported programming languages

.Net
C++
Java
Python
Scala

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

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

C
C++
Delphi
Java
Perl
PHP
Tcl

Server-side scripts

Stored procedures

yes

JavaScript

Triggers

yes, event driven architecture

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

yes

Implicit feature of the cloud service

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

none

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

optimistic locking

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

Role-based access control

Access rights can be defined down to the item level

Access rights based on private key authentication or shared access signatures

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.