DBMS > Ehcache vs. Google Cloud Datastore vs. Heroic vs. Transbase

System Properties Comparison Ehcache vs. Google Cloud Datastore vs. Heroic vs. Transbase

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

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

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

www.ehcache.org

cloud.google.com/datastore

github.com/spotify/heroic

www.transaction.de/en/products/transbase.html

Technical documentation

www.ehcache.org/documentation

cloud.google.com/datastore/docs

spotify.github.io/heroic

www.transaction.de/en/products/transbase/features.html

Developer

Terracotta Inc, owned by Software AG

Google

Spotify

Transaction Software GmbH

Initial release

2009

2008

2014

1987

Current release

3.10.0, March 2022

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

Apache 2.0

commercial

free development license

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 and C++

Server operating systems

All OS with a Java VM

hosted

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

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

via Elasticsearch

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

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Java

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Multi-source replication using Paxos

yes

Source-replica replication

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.

Eventual Consistency
Immediate Consistency

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

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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 based on Google Cloud Identity and Access Management (IAM)

fine grained access rights 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

Scaling Australia's Most Popular Online News Sites with Ehcache
6 December 2010, InfoQ.com

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

Hazelcast signs Java speed king to its in-memory data-grid crew
21 January 2014, The Register

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

provided by Google News

Best cloud storage of 2024
4 June 2024, TechRadar

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

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

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

Google says it'll stop charging fees to transfer data out of Google Cloud
11 January 2024, TechCrunch

provided by Google News

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

Share this page