DBMS > Apache Impala vs. JaguarDB vs. MaxDB vs. Microsoft Azure Cosmos DB vs. XTDB

System Properties Comparison Apache Impala vs. JaguarDB vs. MaxDB vs. Microsoft Azure Cosmos DB vs. XTDB

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Performant, highly scalable DBMS for AI and IoT applications

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

Globally distributed, horizontally scalable, multi-model database service

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Secondary database models

Document store

Spatial DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

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

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

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

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

impala.apache.org

www.jaguardb.com

maxdb.sap.com

azure.microsoft.com/services/cosmos-db

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

impala.apache.org/impala-docs.html

www.jaguardb.com/support.html

maxdb.sap.com/documentation

learn.microsoft.com/azure/cosmos-db

www.xtdb.com/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

DataJaguar, Inc.

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

Microsoft

Juxt Ltd.

Initial release

2013

2015

1984

2014

2019

Current release

4.1.0, June 2022

3.3 July 2023

7.9.10.12, February 2024

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GPL V3.0

commercial

Limited community edition free

commercial

Open Source

MIT License

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

the server part. Clients available in other languages

C++

Clojure

Server operating systems

Linux

AIX
HP-UX
Linux
Solaris
Windows

hosted

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes, extensible-data-notation format

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like DML and DDL statements

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

SQL-like query language

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC
WebDAV

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

HTTP REST
JDBC

Supported programming languages

All languages supporting JDBC/ODBC

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

.Net
C#
Java
Perl
PHP
Python

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

Clojure
Java

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

Source-replica replication

yes

Implicit feature of the cloud service

yes, each node contains all data

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

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

rights management via user accounts

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.