DBMS > Amazon DynamoDB vs. Apache Phoenix vs. H2GIS vs. jBASE vs. SiriDB

System Properties Comparison Amazon DynamoDB vs. Apache Phoenix vs. H2GIS vs. jBASE vs. SiriDB

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

Spatial extension of H2

A robust multi-value DBMS comprising development tools and middleware

Open Source Time Series DBMS

Primary database model

Document store
Key-value store

Secondary database models

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	0.08
Rank	#368	Overall
	#7	Spatial DBMS

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	0.07
Rank	#378	Overall
	#42	Time Series DBMS

Website

aws.amazon.com/dynamodb

phoenix.apache.org

www.h2gis.org

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

siridb.com

Technical documentation

docs.aws.amazon.com/dynamodb

phoenix.apache.org

www.h2gis.org/docs/home

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

docs.siridb.com

Developer

Amazon

Apache Software Foundation

CNRS

Rocket Software (formerly Zumasys)

Cesbit

Initial release

2012

2014

2013

1991

2017

Current release

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

5.7

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2.0

Open Source

LGPL 3.0

commercial

Open Source

MIT License

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

AIX
Linux
Windows

Linux

Data scheme

schema-free

yes

late-bound, schema-on-read capabilities

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

optional

yes

Numeric data

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

Embedded SQL for jBASE in BASIC

APIs and other access methods

RESTful HTTP API

JDBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

HTTP API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

Java

.Net
Basic
Jabbascript
Java

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

user defined functions

yes

based on H2

yes

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

based on H2

yes

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

Immediate Consistency

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

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

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

yes

based on H2

Access rights can be defined down to the item level

simple rights management via user accounts

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.