DBMS > DataFS vs. Datomic vs. EsgynDB vs. Geode

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

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

Primary database model

Object oriented DBMS

Relational DBMS

Key-value store

Secondary database models

Graph DBMS

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

Score	0.09
Rank	#360	Overall
	#17	Object oriented DBMS

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

Website

Technical documentation

dev.mobiland.com/Overview.xsp

docs.datomic.com

geode.apache.org/docs

Developer

Mobiland AG

Cognitect

Esgyn

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

Initial release

2018

2012

2015

2002

Current release

1.1.263, October 2022

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

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

Windows

All OS with a Java VM

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Data scheme

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

yes

schema-free

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (OQL)

APIs and other access methods

.NET Client API
Proprietary client DLL
WinRT client

RESTful HTTP API

ADO.NET
JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

Supported programming languages

.Net
C
C#
C++
VB.Net

Clojure
Java

All languages supporting JDBC/ODBC/ADO.Net

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

Server-side scripts

Stored procedures

yes

Transaction Functions

Java Stored Procedures

user defined functions

Triggers

no, except callback-events from server when changes happened

By using transaction functions

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Proprietary Sharding system

none

But extensive use of caching in the application peers

Sharding

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

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

Transaction concepts

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

ACID

yes, on a single node

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

Windows-Profile

fine grained access rights according to SQL-standard

Access rights per client and object definable

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