DBMS > Ehcache vs. IBM Cloudant vs. Oracle Coherence vs. SAP SQL Anywhere vs. Snowflake

System Properties Comparison Ehcache vs. IBM Cloudant vs. Oracle Coherence vs. SAP SQL Anywhere vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

Database as a Service offering based on Apache CouchDB

Oracles in-memory data grid solution

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Cloud-based data warehousing service for structured and semi-structured data

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	2.75
Rank	#104	Overall
	#19	Document stores

Score	1.97
Rank	#129	Overall
	#22	Key-value stores

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.ehcache.org

www.ibm.com/products/cloudant

www.oracle.com/java/coherence

www.sap.com/products/technology-platform/sql-anywhere.html

www.snowflake.com

Technical documentation

www.ehcache.org/documentation

cloud.ibm.com/docs/Cloudant

docs.oracle.com/en/middleware/standalone/coherence

help.sap.com/docs/SAP_SQL_Anywhere

docs.snowflake.net/manuals/index.html

Developer

Terracotta Inc, owned by Software AG

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Oracle

SAP

formerly Sybase

Snowflake Computing Inc.

Initial release

2009

2010

2007

1992

2014

Current release

3.10.0, March 2022

14.1, August 2023

17, July 2015

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

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

Erlang

Java

Server operating systems

All OS with a Java VM

hosted

All OS with a Java VM

AIX
HP-UX
Linux
OS X
Solaris
Windows

hosted

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

JCache

RESTful HTTP/JSON API

JCache
JPA
RESTful HTTP API

ADO.NET
HTTP API
JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

Java

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C++
Java

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

yes, in C/C++, Java, .Net or Perl

user defined functions

Triggers

yes

Cache Event Listeners

yes

Live Events

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Multi-source replication
Source-replica replication

yes, with selectable consistency level

Source-replica replication

Database mirroring

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency

Eventual Consistency
Immediate Consistency

Immediate 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

atomic operations within a document possible

configurable

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

optionally

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 can be defined per database

authentification to access the cache via certificates or http basic authentication

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.