DBMS > Amazon Redshift vs. Apache IoTDB vs. Datomic vs. Oracle Coherence

System Properties Comparison Amazon Redshift vs. Apache IoTDB vs. Datomic vs. Oracle Coherence

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Oracles in-memory data grid solution

Primary database model

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	1.31
Rank	#159	Overall
	#14	Time Series DBMS

Score	1.55
Rank	#144	Overall
	#67	Relational DBMS

Score	1.90
Rank	#127	Overall
	#21	Key-value stores

Website

aws.amazon.com/redshift

iotdb.apache.org

www.datomic.com

www.oracle.com/java/coherence

Technical documentation

docs.aws.amazon.com/redshift

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

docs.datomic.com

docs.oracle.com/en/middleware/standalone/coherence

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Cognitect

Oracle

Initial release

2012

2018

2012

2007

Current release

1.1.0, April 2023

1.0.7180, July 2024

14.1, August 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

limited edition free

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

Java, Clojure

Java

Server operating systems

hosted

All OS with a Java VM (>= 1.8)

All OS with a Java VM

Data scheme

yes

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

APIs and other access methods

JDBC
ODBC

JDBC
Native API

RESTful HTTP API

JCache
JPA
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Go
Java
Python
Scala

Clojure
Java

.Net
C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

Triggers

yes

By using transaction functions

yes

Live Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

none

But extensive use of caching in the application peers

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

none

But extensive use of caching in the application peers

yes, with selectable consistency level

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

configurable

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

optionally

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes

authentification to access the cache via certificates or http basic authentication

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.