DBMS > Apache Phoenix vs. Ehcache vs. H2 vs. IBM Cloudant vs. Snowflake

System Properties Comparison Apache Phoenix vs. Ehcache vs. H2 vs. IBM Cloudant vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

A widely adopted Java cache with tiered storage options

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Database as a Service offering based on Apache CouchDB

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

Primary database model

Secondary database models

Spatial DBMS

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

Score	1.90
Rank	#125	Overall
	#59	Relational DBMS

Score	4.79
Rank	#66	Overall
	#8	Key-value stores

Score	7.57
Rank	#47	Overall
	#30	Relational DBMS

Score	2.85
Rank	#95	Overall
	#18	Document stores

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

phoenix.apache.org

www.ehcache.org

www.h2database.com

www.ibm.com/products/cloudant

www.snowflake.com

Technical documentation

phoenix.apache.org

www.ehcache.org/documentation

www.h2database.com/html/main.html

cloud.ibm.com/docs/Cloudant

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Terracotta Inc, owned by Software AG

Thomas Mueller

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Snowflake Computing Inc.

Initial release

2014

2009

2005

2010

2014

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

3.10.0, March 2022

2.2.220, July 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available

Open Source

dual-licence (Mozilla public license, Eclipse public license)

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

Server operating systems

Linux
Unix
Windows

All OS with a Java VM

hosted

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

yes

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

JDBC

JCache

JDBC
ODBC

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

Java

C#
Java
JavaScript
Objective-C
PHP
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Java Stored Procedures and User-Defined Functions

View functions (Map-Reduce) in JavaScript

user defined functions

Triggers

yes

Cache Event Listeners

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

by using Terracotta Server

With clustering: 2 database servers on different computers operate on identical copies of a database

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

supports JTA and can work as an XA resource

ACID

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Optimistic locking

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 Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

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.