DBMS > GeoMesa vs. MaxDB vs. Microsoft Azure Cosmos DB vs. PouchDB vs. Sequoiadb

System Properties Comparison GeoMesa vs. MaxDB vs. Microsoft Azure Cosmos DB vs. PouchDB vs. Sequoiadb

Editorial information provided by DB-Engines

Name

Description

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

JavaScript DBMS with an API inspired by CouchDB

NewSQL database with distributed OLTP and SQL

Primary database model

Spatial DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Document store
Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial 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	2.28
Rank	#115	Overall
	#21	Document stores

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Website

www.geomesa.org

maxdb.sap.com

azure.microsoft.com/services/cosmos-db

pouchdb.com

www.sequoiadb.com

Technical documentation

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

maxdb.sap.com/documentation

learn.microsoft.com/azure/cosmos-db

pouchdb.com/guides

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

CCRi and others

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

Microsoft

Apache Software Foundation

Sequoiadb Ltd.

Initial release

2014

1984

2014

2012

2013

Current release

4.0.5, February 2024

7.9.10.12, February 2024

7.1.1, June 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Limited community edition free

commercial

Open Source

Server: AGPL; Client: Apache V2

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

JavaScript

C++

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows

hosted

server-less, requires a JavaScript environment (browser, Node.js)

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

oid, date, timestamp, binary, regex

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

via views

yes

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
ODBC
WebDAV

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

HTTP REST

only for PouchDB Server
JavaScript API

proprietary protocol using JSON

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

JavaScript

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

yes

JavaScript

View functions in JavaScript

JavaScript

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

Implicit feature of the cloud service

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

yes

Implicit feature of the cloud service

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual 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

Document is locked during a transaction

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

User concepts

Access control

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

simple password-based access control

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.