DBMS > Amazon DynamoDB vs. Apache Phoenix vs. BigObject vs. Citus vs. Ingres

System Properties Comparison Amazon DynamoDB vs. Apache Phoenix vs. BigObject vs. Citus vs. Ingres

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

Analytic DBMS for real-time computations and queries

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

Well established RDBMS

Primary database model

Document store
Key-value store

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Secondary database models

Document store

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.19
Rank	#329	Overall
	#146	Relational DBMS

Score	2.15
Rank	#117	Overall
	#56	Relational DBMS

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Website

aws.amazon.com/dynamodb

phoenix.apache.org

bigobject.io

www.citusdata.com

www.actian.com/databases/ingres

Technical documentation

docs.aws.amazon.com/dynamodb

phoenix.apache.org

docs.bigobject.io

docs.citusdata.com

docs.actian.com/ingres

Developer

Amazon

Apache Software Foundation

BigObject, Inc.

Actian Corporation

Initial release

2012

2014

2015

2010

1974

originally developed at University Berkely in early 1970s

Current release

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

8.1, December 2018

11.2, May 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2.0

commercial

free community edition available

Open Source

AGPL, commercial license also available

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

Server operating systems

hosted

Linux
Unix
Windows

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux

AIX
HP Open VMS
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.

yes

specific XML type available, but no XML query functionality

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

yes

standard, with numerous extensions

yes

APIs and other access methods

RESTful HTTP API

JDBC

fluentd
ODBC
RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

user defined functions

Lua

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

none

Source-replica replication

other methods possible by using 3rd party extensions

Ingres Replicator

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

none

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

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

Read/write lock on objects (tables, trees)

yes

MVCC

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

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.