DBMS > Amazon Redshift vs. Apache Drill vs. Blueflood vs. Microsoft Azure Cosmos DB

System Properties Comparison Amazon Redshift vs. Apache Drill vs. Blueflood vs. Microsoft Azure Cosmos DB

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

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Scalable TimeSeries DBMS based on Cassandra

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Document store
Relational DBMS

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	0.13
Rank	#346	Overall
	#33	Time Series DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

aws.amazon.com/redshift

drill.apache.org

blueflood.io

azure.microsoft.com/services/cosmos-db

Technical documentation

docs.aws.amazon.com/redshift

drill.apache.org/docs

github.com/rax-maas/blueflood/wiki

learn.microsoft.com/azure/cosmos-db

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Rackspace

Microsoft

Initial release

2012

2013

2014

Current release

1.20.3, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Apache 2.0

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

Server operating systems

hosted

Linux
OS X
Windows

Linux
OS X

hosted

Data scheme

yes

schema-free

predefined scheme

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL SELECT statement is SQL:2003 compliant

SQL-like query language

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

HTTP REST

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

All languages supporting JDBC/ODBC

C++

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Depending on the underlying data source

yes

In-memory capabilities

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

yes

Depending on the underlying data source

User concepts

Access control

fine grained access rights according to SQL-standard

Depending on the underlying data source

Access rights can be defined down to the item level

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.