DBMS > GeoSpock vs. GridGain vs. Microsoft SQL Server vs. SQL.JS vs. XTDB

System Properties Comparison GeoSpock vs. GridGain vs. Microsoft SQL Server vs. SQL.JS vs. XTDB

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Spatial and temporal data processing engine for extreme data scale

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

Microsofts flagship relational DBMS

Port of SQLite to JavaScript

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Document store

Secondary database models

Time Series DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	0.63
Rank	#241	Overall
	#112	Relational DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

geospock.com

www.gridgain.com

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

sql.js.org

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

www.gridgain.com/docs/index.html

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

sql.js.org/documentation/index.html

www.xtdb.com/docs

Developer

GeoSpock

GridGain Systems, Inc.

Microsoft

Alon Zakai

enhancements implemented by others

Juxt Ltd.

Initial release

2007

1989

2012

2019

Current release

2.0, September 2019

GridGain 8.5.1

SQL Server 2022, November 2022

1.19, September 2021

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

MIT License

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Java, Javascript

Java, C++, .Net

C++

JavaScript

Clojure

Server operating systems

hosted

Linux
OS X
Solaris
Windows

Linux
Windows

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

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

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

yes

SQL-92 is not fully supported

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC

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

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

JavaScript API

HTTP REST
JDBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

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

JavaScript

Clojure
Java

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

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes, but depending on the SQL-Server Edition

none

yes, each node contains all data

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

none

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

except by serializing a db to a file

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users can be defined per table

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

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.