DBMS > GeoMesa vs. InterSystems Caché vs. Microsoft Azure Cosmos DB vs. Spark SQL

System Properties Comparison GeoMesa vs. InterSystems Caché vs. Microsoft Azure Cosmos DB vs. Spark SQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed from the DB-Engines Ranking.

Description

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

A multi-model DBMS and application server

Globally distributed, horizontally scalable, multi-model database service

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Spatial DBMS

Key-value store
Object oriented DBMS
Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Document store

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	18.04
Rank	#33	Overall
	#20	Relational DBMS

Website

www.geomesa.org

www.intersystems.com/products/cache

azure.microsoft.com/services/cosmos-db

spark.apache.org/sql

Technical documentation

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

docs.intersystems.com

learn.microsoft.com/azure/cosmos-db

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

CCRi and others

InterSystems

Microsoft

Apache Software Foundation

Initial release

2014

1997

2014

Current release

5.0.0, May 2024

2018.1.4, May 2020

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Apache 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

Server operating systems

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

hosted

Linux
OS X
Windows

Data scheme

yes

depending on used data model

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language

SQL-like DML and DDL statements

APIs and other access methods

.NET Client API
JDBC
ODBC
RESTful HTTP API

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

JDBC
ODBC

Supported programming languages

C#
C++
Java

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

Java
Python
R
Scala

Server-side scripts

Stored procedures

yes

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

Implicit feature of the cloud service

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

yes

Implicit feature of the cloud service

none

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

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

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

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users, groups and roles

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.