DBMS > GeoMesa vs. Microsoft Azure Cosmos DB vs. Quasardb vs. Realm vs. searchxml

System Properties Comparison GeoMesa vs. Microsoft Azure Cosmos DB vs. Quasardb vs. Realm vs. searchxml

Editorial information provided by DB-Engines

Name

Description

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

Globally distributed, horizontally scalable, multi-model database service

Distributed, high-performance timeseries database

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Spatial DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Document store

Native XML DBMS
Search engine

Secondary database models

Spatial DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

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

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	7.41
Rank	#52	Overall
	#8	Document stores

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

www.geomesa.org

azure.microsoft.com/services/cosmos-db

quasar.ai

realm.io

www.searchxml.net/category/products

Technical documentation

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

learn.microsoft.com/azure/cosmos-db

doc.quasar.ai/master

realm.io/docs

www.searchxml.net/support/handouts

Developer

CCRi and others

Microsoft

quasardb

Realm, acquired by MongoDB in May 2019

informationpartners gmbh

Initial release

2014

2009

2014

2015

Current release

5.0.0, May 2024

3.14.1, January 2024

1.0

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

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

hosted

BSD
Linux
OS X
Windows

Android
Backend: server-less
iOS
Windows

Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

integer and binary

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

yes

with tags

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

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

HTTP API

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

.Net
Java

with Android only
Objective-C
React Native
Swift

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

JavaScript

runs within the applications so server-side scripts are unnecessary

yes

on the application server

Triggers

JavaScript

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Implicit feature of the cloud service

Sharding

consistent hashing

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Implicit feature of the cloud service

Source-replica replication with selectable replication factor

none

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

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

depending on storage layer

yes

Transient mode

yes

In-Memory realm

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights can be defined down to the item level

Cryptographically strong user authentication and audit trail

yes

Domain, group and role-based access control at the document level and for application services

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.