DBMS > EXASOL vs. GridGain vs. Snowflake vs. SQL.JS vs. VoltDB

System Properties Comparison EXASOL vs. GridGain vs. Snowflake vs. SQL.JS vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

Cloud-based data warehousing service for structured and semi-structured data

Port of SQLite to JavaScript

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

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

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.53
Rank	#252	Overall
	#116	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

Technical documentation

www.exasol.com/resources

www.gridgain.com/docs/index.html

docs.snowflake.net/manuals/index.html

sql.js.org/documentation/index.html

docs.voltdb.com

Developer

Exasol

GridGain Systems, Inc.

Snowflake Computing Inc.

Alon Zakai

enhancements implemented by others

VoltDB Inc.

Initial release

2000

2007

2014

2012

2010

Current release

GridGain 8.5.1

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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.

Implementation language

Java, C++, .Net

JavaScript

Java, C++

Server operating systems

Linux
OS X
Solaris
Windows

hosted

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

Linux
OS X

for development

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

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

yes

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

yes

SQL-92 is not fully supported

yes

only a subset of SQL 99

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

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

CLI Client
JDBC
ODBC

JavaScript API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

Java
Lua
Python
R

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

JavaScript

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

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

user defined functions

Java

Triggers

yes

yes (cache interceptors and events)

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

except by serializing a db to a file

yes

Snapshots and command logging

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, groups and roles according to SQL-standard

Security Hooks for custom implementations

Users with fine-grained authorization concept, user roles and pluggable authentication

Users and roles with access to stored procedures

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.