DBMS > EXASOL vs. Ignite vs. JaguarDB vs. Riak TS vs. Snowflake

System Properties Comparison EXASOL vs. Ignite vs. JaguarDB vs. Riak TS vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

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

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Performant, highly scalable DBMS for AI and IoT applications

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Key-value store
Vector DBMS

Time Series 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	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

Technical documentation

www.exasol.com/resources

apacheignite.readme.io/docs

www.jaguardb.com/support.html

www.tiot.jp/riak-docs/riak/ts/latest

docs.snowflake.net/manuals/index.html

Developer

Exasol

Apache Software Foundation

DataJaguar, Inc.

Open Source, formerly Basho Technologies

Snowflake Computing Inc.

Initial release

2000

2015

2014

Current release

Apache Ignite 2.6

3.3 July 2023

3.0.0, September 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL V3.0

Open Source

commercial

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

C++, Java, .Net

C++

the server part. Clients available in other languages

Erlang

Server operating systems

Linux
OS X
Solaris
Windows

Linux

Linux
OS X

hosted

Data scheme

yes

schema-free

yes

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

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

restricted

SQL

Support of SQL

yes

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes, limited

yes

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

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

JDBC
ODBC

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

Supported programming languages

Java
Lua
Python
R

C#
C++
Java
PHP
Python
Ruby
Scala

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

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

Erlang

user defined functions

Triggers

yes

yes (cache interceptors and events)

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Multi-source replication

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

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

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

Security Hooks for custom implementations

rights management via user accounts

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

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.