DBMS > 4D vs. Amazon DynamoDB vs. Apache Phoenix vs. Cachelot.io vs. Riak TS

System Properties Comparison 4D vs. Amazon DynamoDB vs. Apache Phoenix vs. Cachelot.io vs. Riak TS

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

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

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

In-memory caching system

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Key-value store

Time Series DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

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

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

www.4d.com

aws.amazon.com/dynamodb

phoenix.apache.org

cachelot.io

Technical documentation

developer.4d.com

docs.aws.amazon.com/dynamodb

phoenix.apache.org

www.tiot.jp/riak-docs/riak/ts/latest

Developer

4D, Inc

Amazon

Apache Software Foundation

Open Source, formerly Basho Technologies

Initial release

1984

2012

2014

2015

Current release

v20, April 2023

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

3.0.0, September 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2.0

Open Source

Simplified BSD License

Open Source

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

Erlang

Server operating systems

OS X
Windows

hosted

Linux
Unix
Windows

FreeBSD
Linux
OS X

Linux
OS X

Data scheme

yes

schema-free

yes

late-bound, schema-on-read capabilities

schema-free

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

Secondary indexes

yes

restricted

SQL

Support of SQL

yes

close to SQL 92

yes

yes, limited

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

RESTful HTTP API

JDBC

Memcached protocol

HTTP API
Native Erlang Interface

Supported programming languages

4D proprietary IDE
PHP

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

yes

user defined functions

Erlang

Triggers

yes

by integration with AWS Lambda

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication
Source-replica replication

none

selectable replication factor

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency or Eventual Consistency

none

Eventual Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

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

Users and groups

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.