DBMS > GigaSpaces vs. GridDB vs. Microsoft Azure Cosmos DB vs. Microsoft SQL Server vs. Sphinx

System Properties Comparison GigaSpaces vs. GridDB vs. Microsoft Azure Cosmos DB vs. Microsoft SQL Server vs. Sphinx

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

Scalable in-memory time series database optimized for IoT and Big Data

Globally distributed, horizontally scalable, multi-model database service

Microsofts flagship relational DBMS

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Document store
Object oriented DBMS

Values are user defined objects

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Search engine

Secondary database models

Graph DBMS
Search engine

Key-value store
Relational DBMS

Spatial DBMS

Document store
Graph DBMS
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	2.02
Rank	#132	Overall
	#11	Time Series DBMS

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

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	6.03
Rank	#60	Overall
	#6	Search engines

Website

www.gigaspaces.com

griddb.net

azure.microsoft.com/services/cosmos-db

www.microsoft.com/en-us/sql-server

sphinxsearch.com

Technical documentation

docs.gigaspaces.com/latest/landing.html

docs.griddb.net

learn.microsoft.com/azure/cosmos-db

learn.microsoft.com/en-US/sql/sql-server

sphinxsearch.com/docs

Developer

Gigaspaces Technologies

Toshiba Corporation

Microsoft

Sphinx Technologies Inc.

Initial release

2000

2013

2014

1989

2001

Current release

15.5, September 2020

5.1, August 2022

SQL Server 2022, November 2022

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache Version 2; Commercial licenses available

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

restricted free version is available

Open Source

GPL version 2, commercial licence available

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
macOS
Solaris
Windows

Linux

hosted

Linux
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

full-text index on all search fields

SQL

Support of SQL

SQL-99 for query and DML statements

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like query language

yes

SQL-like query language (SphinxQL)

APIs and other access methods

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

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

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Proprietary protocol

Supported programming languages

.Net
C++
Java
Python
Scala

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

JavaScript

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes, event driven architecture

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

Source-replica replication

yes

Implicit feature of the cloud service

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

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

Immediate consistency within container, eventual consistency across containers

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

ACID at container level

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

The original contents of fields are not stored in the Sphinx index.

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 for users can be defined per database

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

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.