DBMS > Apache Impala vs. ArcadeDB vs. Datomic vs. EXASOL vs. Snowflake

System Properties Comparison Apache Impala vs. ArcadeDB vs. Datomic vs. EXASOL vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Fast and scalable multi-model DBMS, originally forked from OrientDB but most of the code has been rewritten

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

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

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Relational DBMS

Secondary database models

Document store

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	0.10
Rank	#358	Overall
	#48	Document stores
	#38	Graph DBMS
	#52	Key-value stores
	#35	Time Series DBMS

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

Technical documentation

impala.apache.org/impala-docs.html

docs.arcadedb.com

docs.datomic.com

www.exasol.com/resources

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Arcade Data

Cognitect

Exasol

Snowflake Computing Inc.

Initial release

2013

2021

2012

2000

2014

Current release

4.1.0, June 2022

September 2021

1.0.7075, December 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2.0

commercial

limited edition free

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

Java, Clojure

Server operating systems

Linux

All OS with a Java VM

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

SQL-like DML and DDL statements

SQL-like query language, no joins

yes

APIs and other access methods

JDBC
ODBC

JDBC
MongoDB API
OpenCypher
PostgreSQL wire protocol
Redis API
RESTful HTTP/JSON API
TinkerPop Gremlin

RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

CLI Client
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

Java

Clojure
Java

Java
Lua
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

Transaction Functions

user defined functions

Triggers

By using transaction functions

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

none

But extensive use of caching in the application peers

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

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

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

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

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.