PROFILBARU.COM

Apache Druid^[1]
Original author(s)	Metamarkets
Developer(s)	Apache Software Foundation
Stable release	31.0.0 / 22 October 2024; 42 days ago
Repository	github.com/apache/druid
Written in	Java
Operating system	Cross-platform
Type	distributed; real-time; time-series; column-oriented data store;
License	Apache License 2.0
Website	druid.apache.org

Druid is a column-oriented, open-source, distributed data store written in Java. Druid is designed to quickly ingest massive quantities of event data, and provide low-latency queries on top of the data.^[3] The name Druid comes from the shapeshifting Druid class in many role-playing games, to reflect that the architecture of the system can shift to solve different types of data problems.

Druid is commonly used in business intelligence-OLAP applications to analyze high volumes of real-time and historical data.^[4] Druid is used in production by technology companies such as Alibaba,^[4] Airbnb,^[4] Cisco,^[5]^[4] eBay,^[6] Lyft,^[7] Netflix,^[8] PayPal,^[4] Pinterest,^[9] Reddit,^[10] Twitter,^[11] Walmart,^[12] Wikimedia Foundation^[13] and Yahoo.^[14]

History

Druid was started in 2011 by Eric Tschetter, Fangjin Yang, Gian Merlino and Vadim Ogievetsky^[15] to power the analytics product of Metamarkets. The project was open-sourced under the GPL license in October 2012,^[16]^[17]^[18] and moved to an Apache License in February 2015.^[19]^[20]

Architecture

Fully deployed, Druid runs as a cluster of specialized processes (called nodes in Druid) to support a fault-tolerant architecture^[21] where data is stored redundantly, and there is no single point of failure.^[22] The cluster includes external dependencies for coordination (Apache ZooKeeper), metadata storage (e.g. MySQL, PostgreSQL, or Derby), and a deep storage facility (e.g. HDFS, or Amazon S3) for permanent data backup.

Query management

Client queries first hit broker nodes, which forward them to the appropriate data nodes (either historical or real-time). Since Druid segments may be partitioned, an incoming query can require data from multiple segments and partitions (or shards) stored on different nodes in the cluster. Brokers are able to learn which nodes have the required data, and also merge partial results before returning the aggregated result.

Cluster management

Operations relating to data management in historical nodes are overseen by coordinator nodes. Apache ZooKeeper is used to register all nodes, manage certain aspects of internode communications, and provide for leader elections.

Features

Low latency (streaming) data ingestion.
Arbitrary slice and dice data exploration.
Sub-second analytic queries.
Approximate and exact computations.

Performance

In 2019, researchers compared the performance of Hive, Presto, and Druid using a denormalized Star Schema Benchmark based on the TPC-H standard. Druid was tested using both a “Druid Best” configuration using tables with hashed partitions and a “Druid Suboptimal” configuration which does not use hashed partitions.^[23]

Tests were conducted by running the 13 TPC-H queries using TPC-H Scale Factor 30 (a 30GB database), Scale Factor 100 (a 100GB database), and Scale Factor 300 (a 300GB database).


Scale Factor	Hive	Presto	Druid Best	Druid Suboptimal
30	256s	33s	2.09s	3.21s
100	424s	90s	6.12s	8.08s
300	982s	452s	7.60s	20.02s

Druid performance was measured as at least 98% faster than Hive and at least 90% faster than Presto in each scenario, even when using the Druid Suboptimized configuration.