DBMS > Ehcache vs. Geode vs. RDF4J vs. Sadas Engine

System Properties Comparison Ehcache vs. Geode vs. RDF4J vs. Sadas Engine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

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

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

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Key-value store

RDF store

Relational DBMS

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

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

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

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Website

Technical documentation

www.ehcache.org/documentation

geode.apache.org/docs

rdf4j.org/documentation

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Terracotta Inc, owned by Software AG

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

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

SADAS s.r.l.

Initial release

2009

2002

2004

2006

Current release

3.10.0, March 2022

1.1, February 2017

8.0

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

free trial version available

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

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Unix
Windows

AIX
Linux
Windows

Data scheme

schema-free

yes

RDF Schemas

yes

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

SQL-like query language (OQL)

yes

APIs and other access methods

JCache

Java Client API
Memcached protocol
RESTful HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

JDBC
ODBC
Proprietary protocol

Supported programming languages

Java

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

Java
PHP
Python

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Cache Event Listeners

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

supports JTA and can work as an XA resource

yes, on a single node

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

managed by 'Learn by Usage'

User concepts

Access control

Access rights per client and object definable

Access rights for users, groups and roles 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.

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

Atlassian asks customers to patch critical Jira vulnerability
22 July 2021, BleepingComputer

Critical Jira Flaw in Atlassian Could Lead to RCE
22 July 2021, Threatpost

DZone Coding Java JBoss 5 to 7 in 11 steps
9 January 2014, dzone.com

provided by Google News

Apache Geode Spawns 'All Sorts of In-Memory Things'
4 January 2017, The New Stack

Where Does Apache Geode Fit in CQRS Architectures?
18 December 2016, InfoQ.com

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, oreilly.com

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

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

provided by Google News

GraphDB Goes Open Source
27 January 2020, iProgrammer

Ontotext's GraphDB 8.10 Makes Knowledge Graph Experience Faster and Richer
13 June 2019, Markets Insider

provided by Google News

Share this page