DBMS > Ehcache vs. Microsoft Azure Cosmos DB vs. STSdb vs. TerminusDB

System Properties Comparison Ehcache vs. Microsoft Azure Cosmos DB vs. STSdb vs. TerminusDB

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

Globally distributed, horizontally scalable, multi-model database service

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Key-value store

Graph DBMS

Secondary database models

Spatial DBMS

Document store
RDF store

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

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

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

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

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

www.ehcache.org

azure.microsoft.com/services/cosmos-db

github.com/STSSoft/STSdb4

terminusdb.com

Technical documentation

www.ehcache.org/documentation

learn.microsoft.com/azure/cosmos-db

terminusdb.github.io/terminusdb/#

Developer

Terracotta Inc, owned by Software AG

Microsoft

STS Soft SC

DataChemist Ltd.

Initial release

2009

2014

2011

2018

Current release

3.10.0, March 2022

4.0.8, September 2015

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

GPLv2, commercial license available

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

All OS with a Java VM

hosted

Windows

Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

yes

primitive types and user defined types (classes)

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

All properties auto-indexed by default

SQL

Support of SQL

SQL-like query language

SQL-like query language (WOQL)

APIs and other access methods

JCache

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

.NET Client API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

Java

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C#
Java

JavaScript
Python

Server-side scripts

Stored procedures

JavaScript

yes

Triggers

yes

Cache Event Listeners

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

Implicit feature of the cloud service

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

yes

Implicit feature of the cloud service

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

in-memory journaling

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 can be defined down to the item level

Role-based access control

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.