DBMS > Heroic vs. MaxDB vs. Microsoft Azure Cosmos DB vs. ObjectBox

System Properties Comparison Heroic vs. MaxDB vs. Microsoft Azure Cosmos DB vs. ObjectBox

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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

Globally distributed, horizontally scalable, multi-model database service

Extremely fast embedded database for small devices, IoT and Mobile

Primary database model

Time Series DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Object oriented DBMS

Secondary database models

Spatial DBMS

Time Series DBMS

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

Score	0.46
Rank	#265	Overall
	#22	Time Series 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	1.29
Rank	#166	Overall
	#5	Object oriented DBMS

Website

github.com/spotify/heroic

maxdb.sap.com

azure.microsoft.com/services/cosmos-db

objectbox.io

Technical documentation

spotify.github.io/heroic

maxdb.sap.com/documentation

learn.microsoft.com/azure/cosmos-db

docs.objectbox.io

Developer

Spotify

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

Microsoft

ObjectBox Limited

Initial release

2014

1984

2014

2017

Current release

7.9.10.12, February 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Limited community edition free

commercial

Open Source

Apache License 2.0

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

Java

C++

C and C++

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows

hosted

Android
iOS
Linux
macOS
Windows

Data scheme

schema-free

yes

schema-free

yes

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.

Secondary indexes

yes

via Elasticsearch

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
ODBC
WebDAV

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

Proprietary native API

Supported programming languages

.Net
C#
Java
Perl
PHP
Python

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

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

Server-side scripts

Stored procedures

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

yes

Source-replica replication

yes

Implicit feature of the cloud service

online/offline synchronization between client and server

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate 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

In-memory capabilities

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

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

yes

More information provided by the system vendor

News

The on-device Vector Database for Android and Java
29 May 2024

Vector search: making sense of search queries
29 May 2024

Python on-device Vector and Object Database for Local AI
28 May 2024

Evolution of search: traditional vs vector search
23 May 2024

On-device Vector Database for Dart/Flutter
21 May 2024

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.