DBMS > AgensGraph vs. Firebase Realtime Database vs. GeoMesa vs. MaxDB vs. Microsoft Azure Cosmos DB

System Properties Comparison AgensGraph vs. Firebase Realtime Database vs. GeoMesa vs. MaxDB vs. Microsoft Azure Cosmos DB

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Graph DBMS
Relational DBMS

Document store

Spatial DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

Score	0.23
Rank	#315	Overall
	#26	Graph DBMS
	#140	Relational DBMS

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	0.86
Rank	#205	Overall
	#4	Spatial 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

Website

bitnine.net/agensgraph

firebase.google.com/products/realtime-database

www.geomesa.org

maxdb.sap.com

azure.microsoft.com/services/cosmos-db

Technical documentation

bitnine.net/documentation

firebase.google.com/docs/database

www.geomesa.org/documentation/stable/user/index.html

maxdb.sap.com/documentation

learn.microsoft.com/azure/cosmos-db

Developer

Bitnine Global Inc.

Google

acquired by Google 2014

CCRi and others

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

Microsoft

Initial release

2016

2012

2014

1984

2014

Current release

2.1, December 2018

5.0.0, May 2024

7.9.10.12, February 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Apache License 2.0

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

Scala

C++

Server operating systems

Linux
OS X
Windows

hosted

AIX
HP-UX
Linux
Solaris
Windows

hosted

Data scheme

depending on used data model

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

Cypher Query Language
JDBC

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC
WebDAV

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

Supported programming languages

C
Java
JavaScript
Python

Java
JavaScript
Objective-C

.Net
C#
Java
Perl
PHP
Python

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

Server-side scripts

Stored procedures

yes

limited functionality with using 'rules'

yes

JavaScript

Triggers

Callbacks are triggered when data changes

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

depending on storage layer

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

depending on storage layer

Source-replica replication

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

depending on storage layer

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

yes

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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.

depending on storage layer

User concepts

Access control

fine grained access rights according to SQL-standard

yes, based on authentication and database rules

yes

depending on the DBMS used for storage

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.