DBMS > Amazon Redshift vs. Blueflood vs. Cachelot.io vs. Datomic vs. Dolt

System Properties Comparison Amazon Redshift vs. Blueflood vs. Cachelot.io vs. Datomic vs. Dolt

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Scalable TimeSeries DBMS based on Cassandra

In-memory caching system

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

A MySQL compatible DBMS with Git-like versioning of data and schema

Primary database model

Secondary database models

Document store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.06
Rank	#353	Overall
	#34	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Website

aws.amazon.com/redshift

blueflood.io

cachelot.io

www.datomic.com

github.com/dolthub/dolt
www.dolthub.com

Technical documentation

docs.aws.amazon.com/redshift

github.com/rax-maas/blueflood/wiki

docs.datomic.com

docs.dolthub.com

Developer

Amazon (based on PostgreSQL)

Rackspace

Cognitect

DoltHub Inc

Initial release

2012

2013

2015

2012

2018

Current release

1.0.6735, June 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Simplified BSD License

commercial

limited edition free

Open Source

Apache Version 2.0

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

Java, Clojure

Server operating systems

hosted

Linux
OS X

FreeBSD
Linux
OS X

All OS with a Java VM

Linux
macOS
Windows

Data scheme

yes

predefined scheme

schema-free

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

HTTP REST

Memcached protocol

RESTful HTTP API

CLI Client
HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

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

Clojure
Java

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

yes

currently in alpha release

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

But extensive use of caching in the application peers

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

none

But extensive use of caching in the application peers

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

none

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

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

Only one user is configurable, and must be specified in the config file at startup

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.