DBMS > Datomic vs. Geode vs. RocksDB vs. Solr vs. Trafodion

System Properties Comparison Datomic vs. Geode vs. RocksDB vs. Solr vs. Trafodion

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

A widely used distributed, scalable search engine based on Apache Lucene

Transactional SQL-on-Hadoop DBMS

Primary database model

Secondary database models

Spatial DBMS

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

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

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

Technical documentation

docs.datomic.com

geode.apache.org/docs

github.com/facebook/rocksdb/wiki

solr.apache.org/resources.html

trafodion.apache.org/documentation.html

Developer

Cognitect

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Facebook, Inc.

Apache Software Foundation

Apache Software Foundation, originally developed by HP

Initial release

2012

2002

2013

2006

2014

Current release

1.0.6735, June 2023

1.1, February 2017

8.11.4, April 2024

9.5.0, February 2024

2.3.0, February 2019

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

BSD

Open Source

Apache Version 2

Open Source

Apache 2.0

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

Java

C++

Java

C++, Java

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Linux

Data scheme

yes

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

yes

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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 search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language (OQL)

Solr Parallel SQL Interface

yes

APIs and other access methods

RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

C++ API
Java API

Java API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

Supported programming languages

Clojure
Java

.Net
All JVM based languages
C++
Groovy
Java
Scala

C
C++
Go
Java
Perl
Python
Ruby

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

Transaction Functions

user defined functions

Java plugins

Java Stored Procedures

Triggers

By using transaction functions

yes

Cache Event Listeners

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Multi-source replication

yes

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

yes

optimistic locking

ACID

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

yes

User concepts

Access control

Access rights per client and object definable

yes

fine grained access rights according to SQL-standard

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.