DBMS > Amazon Redshift vs. Blueflood vs. Dolt vs. Immudb vs. Warp 10

System Properties Comparison Amazon Redshift vs. Blueflood vs. Dolt vs. Immudb vs. Warp 10

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

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

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Secondary database models

Document store

Relational DBMS

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.96
Rank	#193	Overall
	#90	Relational DBMS

Score	0.24
Rank	#305	Overall
	#43	Key-value stores

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

aws.amazon.com/redshift

blueflood.io

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

github.com/codenotary/immudb
immudb.io

www.warp10.io

Technical documentation

docs.aws.amazon.com/redshift

github.com/rax-maas/blueflood/wiki

docs.dolthub.com

docs.immudb.io

www.warp10.io/content/02_Getting_started

Developer

Amazon (based on PostgreSQL)

Rackspace

DoltHub Inc

Codenotary

SenX

Initial release

2012

2013

2018

2020

2015

Current release

1.2.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

Open Source

Apache License 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

Server operating systems

hosted

Linux
OS X

Linux
macOS
Windows

BSD
Linux
macOS
Solaris
Windows
z/OS

Linux
OS X
Windows

Data scheme

yes

predefined 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

yes

SQL-like syntax

APIs and other access methods

JDBC
ODBC

HTTP REST

CLI Client
HTTP REST

gRPC protocol
PostgreSQL wire protocol

HTTP API
Jupyter
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

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

.Net
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

currently in alpha release

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

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

selectable replication factor

based on HBase

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

Immediate Consistency

based on HBase

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

In-memory capabilities

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

yes

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

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.