DBMS > Amazon Redshift vs. Datomic vs. Prometheus vs. RavenDB

System Properties Comparison Amazon Redshift vs. Datomic vs. Prometheus vs. RavenDB

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

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

Open-source Time Series DBMS and monitoring system

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Relational DBMS

Time Series DBMS

Document store

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Website

aws.amazon.com/redshift

www.datomic.com

prometheus.io

ravendb.net

Technical documentation

docs.aws.amazon.com/redshift

docs.datomic.com

prometheus.io/docs

ravendb.net/docs

Developer

Amazon (based on PostgreSQL)

Cognitect

Hibernating Rhinos

Initial release

2012

2015

2010

Current release

1.0.7075, December 2023

5.4, July 2022

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache 2.0

Open Source

AGPL version 3, commercial license available

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, Clojure

Server operating systems

hosted

All OS with a Java VM

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Import of XML data possible

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (RQL)

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

RESTful HTTP/JSON API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

yes

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

yes

by Federation

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

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

ACID, Cluster-wide transaction available

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

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

User concepts

Access control

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

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.