DBMS > Dolt vs. EXASOL vs. GridGain vs. Snowflake vs. ToroDB

System Properties Comparison Dolt vs. EXASOL vs. GridGain vs. Snowflake vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

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

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Document store

Secondary database models

Document store

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

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

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

Website

github.com/dolthub/dolt
www.dolthub.com

www.exasol.com

www.gridgain.com

www.snowflake.com

github.com/torodb/server

Technical documentation

docs.dolthub.com

www.exasol.com/resources

www.gridgain.com/docs/index.html

docs.snowflake.net/manuals/index.html

Developer

DoltHub Inc

Exasol

GridGain Systems, Inc.

Snowflake Computing Inc.

8Kdata

Initial release

2018

2000

2007

2014

2016

Current release

GridGain 8.5.1

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

AGPL-V3

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

Java

Server operating systems

Linux
macOS
Windows

Linux
OS X
Solaris
Windows

hosted

All OS with a Java 7 VM

Data scheme

yes

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

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

APIs and other access methods

CLI Client
HTTP REST

.Net
JDBC
ODBC
WebSocket

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

CLI Client
JDBC
ODBC

Supported programming languages

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

Java
Lua
Python
R

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

currently in alpha release

user defined functions

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

user defined functions

Triggers

yes

yes (cache interceptors and events)

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

yes (replicated cache)

yes

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
Immediate Consistency

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

In-memory capabilities

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

yes

User concepts

Access control

Only one user is configurable, and must be specified in the config file at startup

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

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.