DBMS > EXASOL vs. Ignite vs. Quasardb vs. Snowflake vs. SpatiaLite

System Properties Comparison EXASOL vs. Ignite vs. Quasardb vs. Snowflake vs. SpatiaLite

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.

Distributed, high-performance timeseries database

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

Spatial extension of SQLite

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Time Series DBMS

Relational DBMS

Spatial DBMS

Secondary database models

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.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Website

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

www.exasol.com/resources

apacheignite.readme.io/docs

doc.quasar.ai/master

docs.snowflake.net/manuals/index.html

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Exasol

Apache Software Foundation

quasardb

Snowflake Computing Inc.

Alessandro Furieri

Initial release

2000

2015

2009

2014

2008

Current release

Apache Ignite 2.6

3.14.1, January 2024

5.0.0, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

commercial

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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++

Server operating systems

Linux
OS X
Solaris
Windows

BSD
Linux
OS X
Windows

hosted

server-less

Data scheme

yes

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

yes

SQL

Support of SQL

yes

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

SQL-like query language

yes

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

Supported programming languages

Java
Lua
Python
R

C#
C++
Java
PHP
Python
Ruby
Scala

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

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

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

consistent hashing

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Source-replica replication with selectable replication factor

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes (compute grid and hadoop accelerator)

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

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

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

yes

User concepts

Access control

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

Security Hooks for custom implementations

Cryptographically strong user authentication and audit trail

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.