DBMS > GridGain vs. JanusGraph vs. Microsoft SQL Server vs. RavenDB vs. SWC-DB

System Properties Comparison GridGain vs. JanusGraph vs. Microsoft SQL Server vs. RavenDB vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

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

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Microsofts flagship relational DBMS

Open Source Operational and Transactional Enterprise NoSQL Document Database

A high performance, scalable Wide Column DBMS

Primary database model

Key-value store
Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

Time Series DBMS

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

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

www.gridgain.com

janusgraph.org

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

ravendb.net

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

www.gridgain.com/docs/index.html

docs.janusgraph.org

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

ravendb.net/docs

Developer

GridGain Systems, Inc.

Linux Foundation; originally developed as Titan by Aurelius

Microsoft

Hibernating Rhinos

Alex Kashirin

Initial release

2007

2017

1989

2010

2020

Current release

GridGain 8.5.1

0.6.3, February 2023

SQL Server 2022, November 2022

5.4, July 2022

0.5, April 2021

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

AGPL version 3, commercial license available

Open Source

GPL V3

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

Java

C++

Server operating systems

Linux
OS X
Solaris
Windows

Linux
OS X
Unix
Windows

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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

SQL

Support of SQL

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

yes

SQL-like query language (RQL)

SQL-like query language

APIs and other access methods

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

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

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

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

Proprietary protocol
Thrift

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

Clojure
Java
Python

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

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

C++

Server-side scripts

Stored procedures

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

yes

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

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

yes, but depending on the SQL-Server Edition

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

via Faunus, a graph analytics engine

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

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.

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

User authentification and security via Rexster Graph Server

fine grained access rights according to SQL-standard

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.