DBMS > Ehcache vs. Microsoft Azure Table Storage vs. OrigoDB vs. Sadas Engine vs. Yanza

System Properties Comparison Ehcache vs. Microsoft Azure Table Storage vs. OrigoDB vs. Sadas Engine vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A widely adopted Java cache with tiered storage options

A Wide Column Store for rapid development using massive semi-structured datasets

A fully ACID in-memory object graph database

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

Time Series DBMS for IoT Applications

Primary database model

Key-value store

Wide column store

Document store
Object oriented DBMS

Relational DBMS

Time Series DBMS

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

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

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Website

www.ehcache.org

azure.microsoft.com/en-us/services/storage/tables

origodb.com

www.sadasengine.com

yanza.com

Technical documentation

www.ehcache.org/documentation

origodb.com/docs

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

Developer

Terracotta Inc, owned by Software AG

Microsoft

Robert Friberg et al

SADAS s.r.l.

Yanza

Initial release

2009

2012

2009

under the name LiveDB

2006

2015

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

commercial

free trial version available

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

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
Windows

AIX
Linux
Windows

Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

JCache

RESTful HTTP API

.NET Client API
HTTP API
LINQ

JDBC
ODBC
Proprietary protocol

HTTP API

Supported programming languages

Java

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

Triggers

yes

Cache Event Listeners

yes

Domain Events

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

Implicit feature of the cloud service

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Source-replica 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)

Immediate Consistency

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

yes

supports JTA and can work as an XA resource

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

Write ahead log

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 based on private key authentication or shared access signatures

Role based authorization

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

provided by Google News

Working with Azure to Use and Manage Data Lakes
7 March 2024, Simplilearn

Azure Cosmos DB Data Migration tool imports from Azure Table storage | Azure updates
5 May 2015, Microsoft

How to Use C# Azure.Data.Tables SDK with Azure Cosmos DB
9 July 2021, hackernoon.com

How to use Azure Table storage in .Net
14 January 2019, InfoWorld

Quick Guide to Azure Storage Pricing
16 May 2023, DevOps.com

provided by Google News

Share this page