DBMS > Datomic vs. GeoMesa vs. Google Cloud Datastore vs. InterSystems Caché vs. RocksDB

System Properties Comparison Datomic vs. GeoMesa vs. Google Cloud Datastore vs. InterSystems Caché vs. RocksDB

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A multi-model DBMS and application server

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Relational DBMS

Spatial DBMS

Document store

Key-value store
Object oriented DBMS
Relational DBMS

Key-value store

Secondary database models

Document store

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

www.datomic.com

www.geomesa.org

cloud.google.com/datastore

www.intersystems.com/products/cache

rocksdb.org

Technical documentation

docs.datomic.com

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

cloud.google.com/datastore/docs

docs.intersystems.com

github.com/facebook/rocksdb/wiki

Developer

Cognitect

CCRi and others

Google

InterSystems

Facebook, Inc.

Initial release

2012

2014

2008

1997

2013

Current release

1.0.6735, June 2023

4.0.5, February 2024

2018.1.4, May 2020

8.11.4, April 2024

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache License 2.0

commercial

Open Source

BSD

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

Java, Clojure

Scala

C++

Server operating systems

All OS with a Java VM

hosted

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

Linux

Data scheme

yes

schema-free

depending on used data model

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL

Support of SQL

SQL-like query language (GQL)

yes

APIs and other access methods

RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

.NET Client API
JDBC
ODBC
RESTful HTTP API

C++ API
Java API

Supported programming languages

Clojure
Java

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
C++
Java

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

using Google App Engine

yes

Triggers

By using transaction functions

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

depending on storage layer

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

depending on storage layer

Multi-source replication using Paxos

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights for users, groups and roles

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.