DBMS > Amazon Redshift vs. Apache Druid vs. IBM Db2 warehouse vs. SQLite vs. Yanza

System Properties Comparison Amazon Redshift vs. Apache Druid vs. IBM Db2 warehouse vs. SQLite vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

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

Cloud-based data warehousing service

Widely used embeddable, in-process RDBMS

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Relational DBMS
Time Series DBMS

Relational 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	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	1.37
Rank	#160	Overall
	#74	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

aws.amazon.com/redshift

druid.apache.org

www.ibm.com/products/db2/warehouse

www.sqlite.org

yanza.com

Technical documentation

docs.aws.amazon.com/redshift

druid.apache.org/docs/latest/design

www.sqlite.org/docs.html

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation and contributors

IBM

Dwayne Richard Hipp

Yanza

Initial release

2012

2014

2000

2015

Current release

29.0.1, April 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Apache license v2

commercial

Open Source

Public Domain

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

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
Unix

hosted

server-less

Windows

Data scheme

yes

schema-less columns are supported

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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/export of XML data possible

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL for querying

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC

JDBC
RESTful HTTP/JSON API

.NET Client API
JDBC
ODBC
OLE DB

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

in Python

PL/SQL, SQL PL

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, via HDFS, S3 or other storage engines

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

via file-system locks

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

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

fine grained access rights 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.