DBMS > AlaSQL vs. GeoMesa vs. GridGain vs. Microsoft SQL Server vs. WakandaDB

System Properties Comparison AlaSQL vs. GeoMesa vs. GridGain vs. Microsoft SQL Server vs. WakandaDB

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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

Microsofts flagship relational DBMS

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Document store
Relational DBMS

Spatial DBMS

Key-value store
Relational DBMS

Relational DBMS

Object oriented DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

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

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

alasql.org

www.geomesa.org

www.gridgain.com

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

wakanda.github.io

Technical documentation

github.com/AlaSQL/alasql

www.geomesa.org/documentation/stable/user/index.html

www.gridgain.com/docs/index.html

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

wakanda.github.io/doc

Developer

Andrey Gershun & Mathias R. Wulff

CCRi and others

GridGain Systems, Inc.

Microsoft

Wakanda SAS

Initial release

2014

2007

1989

2012

Current release

4.0.5, February 2024

GridGain 8.5.1

SQL Server 2022, November 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache License 2.0

commercial

restricted free version is available

Open Source

AGPLv3, extended 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

JavaScript

Scala

Java, C++, .Net

C++

C++, JavaScript

Server operating systems

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

Linux
OS X
Solaris
Windows

Linux
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

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

Close to SQL99, but no user access control, stored procedures and host language bindings.

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

yes

APIs and other access methods

JavaScript API

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

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

RESTful HTTP API

Supported programming languages

JavaScript

C#
C++
Java
PHP
Python
Ruby
Scala

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

JavaScript

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

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

yes (replicated cache)

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

none

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

In-memory capabilities

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

yes

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

yes

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.