DBMS > Amazon Redshift vs. Apache Druid vs. Google Cloud Bigtable vs. KeyDB

System Properties Comparison Amazon Redshift vs. Apache Druid vs. Google Cloud Bigtable vs. KeyDB

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

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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Primary database model

Relational DBMS

Relational DBMS
Time Series DBMS

Key-value store
Wide column store

Key-value store

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	2.85
Rank	#96	Overall
	#50	Relational DBMS
	#6	Time Series DBMS

Score	2.97
Rank	#92	Overall
	#15	Key-value stores
	#8	Wide column stores

Score	0.63
Rank	#232	Overall
	#32	Key-value stores

Website

aws.amazon.com/redshift

druid.apache.org

cloud.google.com/bigtable

github.com/Snapchat/KeyDB
keydb.dev

Technical documentation

docs.aws.amazon.com/redshift

druid.apache.org/docs/latest/design

cloud.google.com/bigtable/docs

docs.keydb.dev

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation and contributors

Google

EQ Alpha Technology Ltd.

Initial release

2012

2015

2019

Current release

30.0.0, June 2024

License

Commercial or Open Source

commercial

Open Source

Apache license v2

commercial

Open Source

BSD-3

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

Server operating systems

hosted

Linux
OS X
Unix

hosted

Linux

Data scheme

yes

schema-less columns are supported

schema-free

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL for querying

APIs and other access methods

JDBC
ODBC

JDBC
RESTful HTTP/JSON API

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Proprietary protocol

RESP - REdis Serialization Protoco

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C#
C++
Go
Java
JavaScript (Node.js)
Python

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, via HDFS, S3 or other storage engines

Internal replication in Colossus, and regional replication between two clusters in different zones

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Eventual Consistency
Strong eventual consistency with CRDTs

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

Atomic single-row operations

Optimistic locking, atomic execution of commands blocks and scripts

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

simple password-based access control and ACL

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.