DBMS > Amazon Redshift vs. Apache Druid vs. IBM Cloudant vs. Linter vs. Sadas Engine

System Properties Comparison Amazon Redshift vs. Apache Druid vs. IBM Cloudant vs. Linter vs. Sadas Engine

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Database as a Service offering based on Apache CouchDB

RDBMS for high security requirements

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Relational DBMS

Relational DBMS
Time Series DBMS

Document store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Website

aws.amazon.com/redshift

druid.apache.org

www.ibm.com/products/cloudant

linter.ru

www.sadasengine.com

Technical documentation

docs.aws.amazon.com/redshift

druid.apache.org/docs/latest/design

cloud.ibm.com/docs/Cloudant

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation and contributors

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

relex.ru

SADAS s.r.l.

Initial release

2012

2010

1990

2006

Current release

29.0.1, April 2024

8.0

License

Commercial or Open Source

commercial

Open Source

Apache license v2

commercial

free trial version 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

Erlang

C and C++

C++

Server operating systems

hosted

Linux
OS X
Unix

hosted

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

AIX
Linux
Windows

Data scheme

yes

schema-less columns are supported

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

SQL for querying

yes

APIs and other access methods

JDBC
ODBC

JDBC
RESTful HTTP/JSON API

RESTful HTTP/JSON API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

JDBC
ODBC
Proprietary protocol

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

View functions (Map-Reduce) in JavaScript

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, via HDFS, S3 or other storage engines

Multi-source replication
Source-replica replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

managed by 'Learn by Usage'

User concepts

Access control

fine grained access rights according to SQL-standard

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

Access rights for users, groups and roles according to SQL-standard

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.