DBMS > GridGain vs. LokiJS vs. Microsoft SQL Server vs. Oracle NoSQL

System Properties Comparison GridGain vs. LokiJS vs. Microsoft SQL Server vs. Oracle NoSQL

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

In-memory JavaScript DBMS

Microsofts flagship relational DBMS

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Primary database model

Key-value store
Relational DBMS

Document store

Relational DBMS

Document store
Key-value store
Relational 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.43
Rank	#264	Overall
	#42	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Website

www.gridgain.com

github.com/techfort/LokiJS

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

www.oracle.com/database/nosql/technologies/nosql

Technical documentation

www.gridgain.com/docs/index.html

techfort.github.io/LokiJS

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

docs.oracle.com/en/database/other-databases/nosql-database/index.html

Developer

GridGain Systems, Inc.

Microsoft

Oracle

Initial release

2007

2014

1989

2011

Current release

GridGain 8.5.1

SQL Server 2022, November 2022

23.3, December 2023

License

Commercial or Open Source

commercial

Open Source

commercial

restricted free version is available

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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

JavaScript

C++

Java

Server operating systems

Linux
OS X
Solaris
Windows

server-less, requires a JavaScript environment (browser, Node.js)

Linux
Windows

Linux
Solaris SPARC/x86

Data scheme

yes

schema-free

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

Typing

predefined data types such as float or date

yes

optional

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

via views

yes

SQL

Support of SQL

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

yes

SQL-like DML and DDL statements

APIs and other access methods

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

JavaScript API

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

RESTful HTTP API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript

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

C
C#
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

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

View functions in JavaScript

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

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

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)

none

yes, but depending on the SQL-Server Edition

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a single collection possible

ACID

configurable

ACID within a storage node (=shard)

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

yes

In-memory capabilities

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

yes

off heap cache

User concepts

Access control

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

Access rights for users and roles

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.