DBMS > GridGain vs. JaguarDB vs. Microsoft SQL Server vs. Warp 10

System Properties Comparison GridGain vs. JaguarDB vs. Microsoft SQL Server vs. Warp 10

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

Performant, highly scalable DBMS for AI and IoT applications

Microsofts flagship relational DBMS

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Key-value store
Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial 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	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

www.gridgain.com

www.jaguardb.com

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

www.warp10.io

Technical documentation

www.gridgain.com/docs/index.html

www.jaguardb.com/support.html

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

www.warp10.io/content/02_Getting_started

Developer

GridGain Systems, Inc.

DataJaguar, Inc.

Microsoft

SenX

Initial release

2007

2015

1989

2015

Current release

GridGain 8.5.1

3.3 July 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

commercial

restricted free version is available

Open Source

Apache License 2.0

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++

the server part. Clients available in other languages

C++

Java

Server operating systems

Linux
OS X
Solaris
Windows

Linux

Linux
Windows

Linux
OS X
Windows

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

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

JDBC
ODBC

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

HTTP API
Jupyter
WebSocket

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

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

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

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

WarpScript

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

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Multi-source replication

yes, but depending on the SQL-Server Edition

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

User concepts

Access control

Security Hooks for custom implementations

rights management via user accounts

fine grained access rights according to SQL-standard

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.