DBMS > Ehcache vs. Google Cloud Datastore vs. RDF4J vs. Sadas Engine

System Properties Comparison Ehcache vs. Google Cloud Datastore 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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

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

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Website

www.ehcache.org

cloud.google.com/datastore

rdf4j.org

www.sadasengine.com

Technical documentation

www.ehcache.org/documentation

cloud.google.com/datastore/docs

rdf4j.org/documentation

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

Developer

Terracotta Inc, owned by Software AG

Google

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

SADAS s.r.l.

Initial release

2009

2008

2004

2006

Current release

3.10.0, March 2022

8.0

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

free trial version available

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

C++

Server operating systems

All OS with a Java VM

hosted

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

yes, details here

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 (GQL)

yes

APIs and other access methods

JCache

gRPC (using protocol buffers) API
RESTful HTTP/JSON 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
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java
PHP
Python

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

Server-side scripts

Stored procedures

using Google App Engine

yes

Triggers

yes

Cache Event Listeners

Callbacks using the Google Apps Engine

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 using Paxos

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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 for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

Best cloud storage of 2024
29 April 2024, TechRadar

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Inside Google’s strategic move to eliminate customer cloud data transfer fees
12 January 2024, Network World

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

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