DBMS > Datomic vs. GeoMesa vs. Heroic vs. Oracle NoSQL

System Properties Comparison Datomic vs. GeoMesa vs. Heroic vs. Oracle NoSQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Primary database model

Relational DBMS

Spatial DBMS

Time Series DBMS

Document store
Key-value store
Relational DBMS

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	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Website

www.datomic.com

www.geomesa.org

github.com/spotify/heroic

www.oracle.com/database/nosql/technologies/nosql

Technical documentation

docs.datomic.com

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

spotify.github.io/heroic

docs.oracle.com/en/database/other-databases/nosql-database/index.html

Developer

Cognitect

CCRi and others

Spotify

Oracle

Initial release

2012

2014

2011

Current release

1.0.6735, June 2023

5.0.0, May 2024

23.3, December 2023

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, Clojure

Scala

Java

Server operating systems

All OS with a Java VM

Linux
Solaris SPARC/x86

Data scheme

yes

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

Typing

predefined data types such as float or date

yes

optional

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

via Elasticsearch

yes

SQL

Support of SQL

SQL-like DML and DDL statements

APIs and other access methods

RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

RESTful HTTP API

Supported programming languages

Clojure
Java

C
C#
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Transaction Functions

Triggers

By using transaction functions

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

depending on storage layer

yes

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Eventual Consistency
Immediate Consistency

depending on configuration

Foreign keys

Referential integrity

Transaction concepts

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

ACID

configurable

ACID within a storage node (=shard)

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

off heap cache

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users 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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Atomic Canyon and ORNL develop revolutionary nuclear AI
16 May 2024, energynews.pro

Nubank buys firm behind Clojure programming language
28 July 2020, Finextra

Architecting Software for Leverage
13 November 2021, InfoQ.com

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

Brazil’s Nubank acquires US software firm Cognitect, creator of Clojure and Datomic
24 July 2020, LatamList

provided by Google News

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

OpenWorld 2013: Oracle NoSQL Database On the Rise?
13 December 2023, Channel Futures

Blog Theme - Details
21 August 2023, Oracle

We built a geo-distributed, serverless modern app using the Oracle NoSQL Database Cloud Service
18 November 2021, Oracle

Oracle Defends Relational DBs Against NoSQL Competitors
25 November 2015, eWeek

Oracle Adds New AI-Enabling Features To MySQL HeatWave
23 March 2023, Forbes

provided by Google News

Share this page