DBMS > EXASOL vs. GridGain vs. SiriDB vs. Snowflake vs. Vitess

System Properties Comparison EXASOL vs. GridGain vs. SiriDB vs. Snowflake vs. Vitess

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

Open Source Time Series DBMS

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial 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	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

Technical documentation

www.exasol.com/resources

www.gridgain.com/docs/index.html

docs.siridb.com

docs.snowflake.net/manuals/index.html

vitess.io/docs

Developer

Exasol

GridGain Systems, Inc.

Cesbit

Snowflake Computing Inc.

The Linux Foundation, PlanetScale

Initial release

2000

2007

2017

2014

2013

Current release

GridGain 8.5.1

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

MIT License

commercial

Open Source

Apache Version 2.0, commercial licenses available

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

Server operating systems

Linux
OS X
Solaris
Windows

Linux

hosted

Docker
Linux
macOS

Data scheme

yes

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

yes

Typing

predefined data types such as float or date

yes

Numeric data

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

with proprietary extensions

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

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

HTTP API

CLI Client
JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Java
Lua
Python
R

C#
C++
Java
PHP
Python
Ruby
Scala

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

JavaScript (Node.js)
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

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

user defined functions

yes

proprietary syntax

Triggers

yes

yes (cache interceptors and events)

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Access rights for users, groups and roles according to SQL-standard

Security Hooks for custom implementations

simple rights management via user accounts

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

Users with fine-grained authorization concept

no user groups or 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.