DBMS > EXASOL vs. HEAVY.AI vs. JaguarDB vs. Memcached vs. Snowflake

System Properties Comparison EXASOL vs. HEAVY.AI vs. JaguarDB vs. Memcached vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

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

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Performant, highly scalable DBMS for AI and IoT applications

In-memory key-value store, originally intended for caching

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

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Key-value store

Relational DBMS

Secondary database models

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.77
Rank	#141	Overall
	#65	Relational DBMS

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

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.exasol.com

github.com/heavyai/heavydb
www.heavy.ai

www.jaguardb.com

www.memcached.org

www.snowflake.com

Technical documentation

www.exasol.com/resources

docs.heavy.ai

www.jaguardb.com/support.html

github.com/memcached/memcached/wiki

docs.snowflake.net/manuals/index.html

Developer

Exasol

HEAVY.AI, Inc.

DataJaguar, Inc.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Snowflake Computing Inc.

Initial release

2000

2016

2015

2003

2014

Current release

5.10, January 2022

3.3 July 2023

1.6.25, March 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

Open Source

GPL V3.0

Open Source

BSD license

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

C++

the server part. Clients available in other languages

Server operating systems

Linux

FreeBSD
Linux
OS X
Unix
Windows

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

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

JDBC
ODBC
Thrift
Vega

JDBC
ODBC

Proprietary protocol

CLI Client
JDBC
ODBC

Supported programming languages

Java
Lua
Python
R

All languages supporting JDBC/ODBC/Thrift
Python

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

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Repcached, a Memcached patch, provides this functionallity

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

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

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

fine grained access rights according to SQL-standard

rights management via user accounts

yes

using SASL (Simple Authentication and Security Layer) protocol

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.