DBMS > GridGain vs. Microsoft SQL Server vs. Quasardb vs. RavenDB

System Properties Comparison GridGain vs. Microsoft SQL Server vs. Quasardb vs. RavenDB

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

Microsofts flagship relational DBMS

Distributed, high-performance timeseries database

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Time Series DBMS

Document store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series 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	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	0.19
Rank	#327	Overall
	#30	Time Series DBMS

Score	3.01
Rank	#101	Overall
	#17	Document stores

Website

www.gridgain.com

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

quasar.ai

ravendb.net

Technical documentation

www.gridgain.com/docs/index.html

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

doc.quasar.ai/master

ravendb.net/docs

Developer

GridGain Systems, Inc.

Microsoft

quasardb

Hibernating Rhinos

Initial release

2007

1989

2009

2010

Current release

GridGain 8.5.1

SQL Server 2022, November 2022

3.14.1, January 2024

5.4, July 2022

License

Commercial or Open Source

commercial

restricted free version is available

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

AGPL version 3, commercial license available

Cloud-based only

Only available as a cloud service

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

Linux
Windows

BSD
Linux
OS X
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

yes

SQL

Support of SQL

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

yes

SQL-like query language

SQL-like query language (RQL)

APIs and other access methods

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

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

HTTP API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

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

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

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

Server-side scripts

Stored procedures

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

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

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

consistent hashing

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes, but depending on the SQL-Server Edition

Source-replica replication with selectable replication factor

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

User concepts

Access control

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

Cryptographically strong user authentication and audit trail

Authorization levels configured per client per database

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.