DBMS > Datomic vs. EsgynDB vs. Geode vs. OrigoDB

System Properties Comparison Datomic vs. EsgynDB vs. Geode vs. OrigoDB

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

A fully ACID in-memory object graph database

Primary database model

Relational DBMS

Key-value store

Document store
Object oriented DBMS

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Website

Technical documentation

docs.datomic.com

geode.apache.org/docs

origodb.com/docs

Developer

Cognitect

Esgyn

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

Robert Friberg et al

Initial release

2012

2015

2002

2009

under the name LiveDB

Current release

1.0.7075, December 2023

1.1, February 2017

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

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

C++, Java

Java

Server operating systems

All OS with a Java VM

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (OQL)

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

.NET Client API
HTTP API
LINQ

Supported programming languages

Clojure
Java

All languages supporting JDBC/ODBC/ADO.Net

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

.Net

Server-side scripts

Stored procedures

yes

Transaction Functions

Java Stored Procedures

user defined functions

yes

Triggers

By using transaction functions

yes

Cache Event Listeners

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Multi-source replication between multi datacenters

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

depending on model

Transaction concepts

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

ACID

yes, on a single node

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

Write ahead log

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

fine grained access rights according to SQL-standard

Access rights per client and object definable

Role based authorization

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

Recent citations in the news

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

James Dixon Imagines A Data Lake That Matters
26 January 2015, Forbes

Zoona Case Study
16 December 2017, AWS Blog

provided by Google News

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

Victor I. Cazares Wants NYTW to Call for Ceasefire in Gaza
22 February 2024, Vulture

Event-Driven Architectures with Apache Geode and Spring Integration
20 March 2019, InfoQ.com

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, O'Reilly Media

HPE buys query acceleration platform Ampool to boost Ezmeral hybrid cloud analytics
7 July 2021, SiliconANGLE News

provided by Google News

Share this page