DBMS > Ehcache vs. Google Cloud Datastore vs. Hawkular Metrics vs. NSDb vs. STSdb

System Properties Comparison Ehcache vs. Google Cloud Datastore vs. Hawkular Metrics vs. NSDb vs. STSdb

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

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

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.00
Rank	#379	Overall
	#40	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

www.ehcache.org

cloud.google.com/datastore

www.hawkular.org

nsdb.io

github.com/STSSoft/STSdb4

Technical documentation

www.ehcache.org/documentation

cloud.google.com/datastore/docs

www.hawkular.org/hawkular-metrics/docs/user-guide

nsdb.io/Architecture

Developer

Terracotta Inc, owned by Software AG

Google

Community supported by Red Hat

STS Soft SC

Initial release

2009

2008

2014

2017

2011

Current release

3.10.0, March 2022

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2.0

Open Source

GPLv2, commercial license 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

Java, Scala

Server operating systems

All OS with a Java VM

hosted

Linux
OS X
Windows

Linux
macOS

Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

yes: int, bigint, decimal, string

yes

primitive types and user defined types (classes)

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

all fields are automatically indexed

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like query language

APIs and other access methods

JCache

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

HTTP REST

gRPC
HTTP REST
WebSocket

.NET Client API

Supported programming languages

Java

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

Go
Java
Python
Ruby

Java
Scala

C#
Java

Server-side scripts

Stored procedures

using Google App Engine

Triggers

yes

Cache Event Listeners

Callbacks using the Google Apps Engine

yes

via Hawkular Alerting

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

based on Cassandra

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Multi-source replication using Paxos

selectable replication factor

based on Cassandra

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.

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

Using Apache Lucene

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)

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

provided by Google News

Best cloud storage of 2024
21 May 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

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

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

provided by Google News

Waiting for Red Hat OpenShift 4.0? Too late, 4.1 has already arrived… • DEVCLASS
5 June 2019, DevClass

provided by Google News

Share this page