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

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

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.

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Relational DBMS

Relational DBMS
Time Series DBMS

Key-value store
Wide column store

Search engine

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

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	41.02
Rank	#24	Overall
	#3	Search engines

Website

aws.amazon.com/redshift

druid.apache.org

cloud.google.com/bigtable

solr.apache.org

Technical documentation

docs.aws.amazon.com/redshift

druid.apache.org/docs/latest/design

cloud.google.com/bigtable/docs

solr.apache.org/resources.html

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation and contributors

Google

Apache Software Foundation

Initial release

2012

2015

2006

Current release

29.0.1, April 2024

9.6.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache license v2

commercial

Open Source

Apache Version 2

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
Unix

hosted

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

yes

schema-less columns are supported

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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.

yes

Secondary indexes

restricted

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL for querying

Solr Parallel SQL Interface

APIs and other access methods

JDBC
ODBC

JDBC
RESTful HTTP/JSON API

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

Java API
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

Java plugins

Triggers

yes

User configurable commands triggered on index changes

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

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

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

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

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

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)

yes

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.