DBMS > GeoMesa vs. KairosDB vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. ObjectBox

System Properties Comparison GeoMesa vs. KairosDB vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. ObjectBox

Editorial information provided by DB-Engines

Name

Description

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

Distributed Time Series DBMS based on Cassandra or H2

Globally distributed, horizontally scalable, multi-model database service

A Wide Column Store for rapid development using massive semi-structured datasets

Extremely fast embedded database for small devices, IoT and Mobile

Primary database model

Spatial DBMS

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column 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.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

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

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	1.29
Rank	#166	Overall
	#5	Object oriented DBMS

Website

www.geomesa.org

github.com/kairosdb/kairosdb

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/services/storage/tables

objectbox.io

Technical documentation

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

kairosdb.github.io

learn.microsoft.com/azure/cosmos-db

docs.objectbox.io

Developer

CCRi and others

Microsoft

ObjectBox Limited

Initial release

2014

2013

2014

2012

2017

Current release

5.0.0, May 2024

1.2.2, November 2018

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

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

Scala

Java

C and C++

Server operating systems

Linux
OS X
Windows

hosted

Android
iOS
Linux
macOS
Windows

Data scheme

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

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

Graphite protocol
HTTP REST
Telnet API

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

RESTful HTTP API

Proprietary native API

Supported programming languages

Java
JavaScript

Node.js
PHP
Python

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

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

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

Server-side scripts

Stored procedures

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

based on Cassandra

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

selectable replication factor

based on Cassandra

yes

Implicit feature of the cloud service

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

online/offline synchronization between client and server

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

depending on storage layer

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

Multi-item ACID transactions with snapshot isolation within a partition

optimistic locking

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.

depending on storage layer

User concepts

Access control

yes

depending on the DBMS used for storage

simple password-based access control

Access rights can be defined down to the item level

Access rights based on private key authentication or shared access signatures

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.