DBMS > Amazon DynamoDB vs. Apache Phoenix vs. Axibase vs. EJDB

System Properties Comparison Amazon DynamoDB vs. Apache Phoenix vs. Axibase vs. EJDB

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

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Primary database model

Document store
Key-value store

Relational DBMS

Time Series DBMS

Document store

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

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	0.29
Rank	#292	Overall
	#25	Time Series DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Website

aws.amazon.com/dynamodb

phoenix.apache.org

axibase.com/docs/atsd/finance

github.com/Softmotions/ejdb

Technical documentation

docs.aws.amazon.com/dynamodb

phoenix.apache.org

github.com/Softmotions/ejdb/blob/master/README.md

Developer

Amazon

Apache Software Foundation

Axibase Corporation

Softmotions

Initial release

2012

2014

2013

2012

Current release

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

15585

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2.0

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

Open Source

GPLv2

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

Server operating systems

hosted

Linux
Unix
Windows

Linux

server-less

Data scheme

schema-free

yes

late-bound, schema-on-read capabilities

yes

schema-free

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

yes

string, integer, double, bool, date, object_id

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

SQL-like query language

APIs and other access methods

RESTful HTTP API

JDBC

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

in-process shared library

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

Go
Java
PHP
Python
R
Ruby

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Hadoop integration

yes

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

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

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

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

Durability

Support for making data persistent

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 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

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.