DBMS > Amazon DynamoDB vs. Apache Phoenix vs. Ehcache vs. Faircom DB

System Properties Comparison Amazon DynamoDB vs. Apache Phoenix vs. Ehcache vs. Faircom DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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

A widely adopted Java cache with tiered storage options

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

Key-value store
Relational DBMS

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

Score	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	0.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

Website

aws.amazon.com/dynamodb

phoenix.apache.org

www.ehcache.org

www.faircom.com/products/faircom-db

Technical documentation

docs.aws.amazon.com/dynamodb

phoenix.apache.org

www.ehcache.org/documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

Developer

Amazon

Apache Software Foundation

Terracotta Inc, owned by Software AG

FairCom Corporation

Initial release

2012

2014

2009

1979

Current release

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

3.10.0, March 2022

V12, November 2020

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available

commercial

Restricted, free version 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

ANSI C, C++

Server operating systems

hosted

Linux
Unix
Windows

All OS with a Java VM

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

Data scheme

schema-free

yes

late-bound, schema-on-read capabilities

schema-free

schema free, schema optional, schema required, partial schema,

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

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

SQL

Support of SQL

yes

yes, ANSI SQL with proprietary extensions

APIs and other access methods

RESTful HTTP API

JDBC

JCache

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

Java

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

Server-side scripts

Stored procedures

user defined functions

yes

.Net, JavaScript, C/C++

Triggers

yes

by integration with AWS Lambda

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

by using Terracotta Server

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency or Eventual Consistency

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID

yes

supports JTA and can work as an XA resource

tunable from ACID to Eventually Consistent

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

Yes, tunable from durable to delayed durability to in-memory

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 and roles can be defined via the AWS Identity and Access Management (IAM)

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 with additional protections for files

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.