DBMS > Amazon DynamoDB vs. Apache Phoenix vs. JaguarDB vs. MaxDB

System Properties Comparison Amazon DynamoDB vs. Apache Phoenix vs. JaguarDB vs. MaxDB

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

Performant, highly scalable DBMS for AI and IoT applications

A robust and reliable RDBMS optimized to run all major SAP solutions

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

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.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Website

aws.amazon.com/dynamodb

phoenix.apache.org

www.jaguardb.com

maxdb.sap.com

Technical documentation

docs.aws.amazon.com/dynamodb

phoenix.apache.org

www.jaguardb.com/support.html

maxdb.sap.com/documentation

Developer

Amazon

Apache Software Foundation

DataJaguar, Inc.

SAP, acquired from Software AG (Adabas-D) in 1997

Initial release

2012

2014

2015

1984

Current release

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

3.3 July 2023

7.9.10.12, February 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2.0

Open Source

GPL V3.0

commercial

Limited community edition free

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

C++

the server part. Clients available in other languages

C++

Server operating systems

hosted

Linux
Unix
Windows

Linux

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

yes

late-bound, schema-on-read capabilities

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

RESTful HTTP API

JDBC

JDBC
ODBC

ADO.NET
JDBC
ODBC
WebDAV

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

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

.Net
C#
Java
Perl
PHP
Python

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

Multi-source replication

Source-replica replication

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

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

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

rights management via user accounts

fine grained access rights according to SQL-standard

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.