DBMS > Apache Impala vs. Datomic vs. MaxDB vs. Microsoft Azure Cosmos DB vs. Snowflake

System Properties Comparison Apache Impala vs. Datomic vs. MaxDB vs. Microsoft Azure Cosmos DB vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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

A robust and reliable RDBMS optimized to run all major SAP solutions

Globally distributed, horizontally scalable, multi-model database service

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

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Document store

Spatial DBMS

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	2.26
Rank	#114	Overall
	#55	Relational DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

impala.apache.org

www.datomic.com

maxdb.sap.com

azure.microsoft.com/services/cosmos-db

www.snowflake.com

Technical documentation

impala.apache.org/impala-docs.html

docs.datomic.com

maxdb.sap.com/documentation

learn.microsoft.com/azure/cosmos-db

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Cognitect

SAP, acquired from Software AG (Adabas-D) in 1997

Microsoft

Snowflake Computing Inc.

Initial release

2013

2012

1984

2014

Current release

4.1.0, June 2022

1.0.7075, December 2023

7.9.10.12, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

limited edition free

commercial

Limited community 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, Clojure

C++

Server operating systems

Linux

All OS with a Java VM

AIX
HP-UX
Linux
Solaris
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

JSON types

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

All properties auto-indexed by default

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

ADO.NET
JDBC
ODBC
WebDAV

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

CLI Client
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java

.Net
C#
Java
Perl
PHP
Python

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

Transaction Functions

yes

JavaScript

user defined functions

Triggers

By using transaction functions

yes

JavaScript

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

none

Sharding

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

But extensive use of caching in the application peers

Source-replica replication

yes

Implicit feature of the cloud service

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.