DBMS > EXASOL vs. Geode vs. Oracle Coherence vs. RDF4J vs. Snowflake

System Properties Comparison EXASOL vs. Geode vs. Oracle Coherence vs. RDF4J vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

Oracles in-memory data grid solution

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

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

Score	1.66
Rank	#138	Overall
	#64	Relational DBMS

Score	1.51
Rank	#147	Overall
	#25	Key-value stores

Score	1.90
Rank	#127	Overall
	#21	Key-value stores

Score	0.72
Rank	#222	Overall
	#9	RDF stores

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

www.exasol.com

geode.apache.org

www.oracle.com/java/coherence

rdf4j.org

www.snowflake.com

Technical documentation

www.exasol.com/resources

geode.apache.org/docs

docs.oracle.com/en/middleware/standalone/coherence

rdf4j.org/documentation

docs.snowflake.net/manuals/index.html

Developer

Exasol

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

Oracle

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Snowflake Computing Inc.

Initial release

2000

2002

2007

2004

2014

Current release

1.1, February 2017

14.1, August 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

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

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

All OS with a Java VM

Linux
OS X
Unix
Windows

hosted

Data scheme

yes

schema-free

yes

RDF Schemas

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (OQL)

yes

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

Java Client API
Memcached protocol
RESTful HTTP API

JCache
JPA
RESTful HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

CLI Client
JDBC
ODBC

Supported programming languages

Java
Lua
Python
R

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

.Net
C++
Java

Java
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Triggers

yes

Cache Event Listeners

yes

Live Events

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes, with selectable consistency level

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Eventual Consistency
Immediate 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

configurable

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optionally

yes

in-memory storage is supported as well

yes

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users, groups and roles according to SQL-standard

Access rights per client and object definable

authentification to access the cache via certificates or http basic authentication

Users with fine-grained authorization concept, user roles and pluggable authentication

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.