Druid is an open-source distributed real-time data store designed for business intelligence (OLAP) queries. It is optimized for time series scans and aggregations. It supports loading data from both deep storage system like HDFS and streaming sources like Kafka. Internally, Druid uses Zookeeper for cluster node coordinations, a relational database like MySQL or Postgres to keep track of metadata, and a deep storage system such as HDFS for storing data. Druid also has low latency between the event creation and when it can be queried, which makes Druid desirable for real-time analytics. Druid stores incoming data in a unique format called segment to allow fast aggregations for arbitrary dimensionalities of data. It is used by various companies including Netflix, eBay, Airbnb, PayPal and Alibaba.[03][04]
- Developer
- Country of Origin
- US
- Start Year
- 2011 [05]
- Project Type
- Open Source
- Supported Languages
- Java
- License
- Apache v2
Druid is an open-source distributed real-time data store designed for business intelligence (OLAP) queries. It is optimized for time series scans and aggregations. It supports loading data from both deep storage system like HDFS and streaming sources like Kafka. Internally, Druid uses Zookeeper for cluster node coordinations, a relational database like MySQL or Postgres to keep track of metadata, and a deep storage system such as HDFS for storing data. Druid also has low latency between the event creation and when it can be queried, which makes Druid desirable for real-time analytics. Druid stores incoming data in a unique format called segment to allow fast aggregations for arbitrary dimensionalities of data. It is used by various companies including Netflix, eBay, Airbnb, PayPal and Alibaba.[03][04]
History[05]
Druid was originally developed by engineers at Metamarkets to solve the problem of analyzing high dimensional data set in real-time. Scan and aggregation of billions of records in traditional relational databases are not fast enough, and pre-computing aggregations with NoSQL architecture requires unacceptably long processing time which creates high latency between event occurrence and its availability for querying. Druid was released in April, 2011 to address the need for fast, real-time analytics for high dimensional time series data. It was open sourced in Oct, 2012 and is under active developments.
Indexes
Druid index documents into data segment when data are first ingested.
Query Interface[09]
Druid uses customized query interface expressed in JSON for metadata, aggregation and search.
Storage Architecture[10][11]
Druid was built with all in-memory. However such choice is costly given large amount of data. It then switches to use a combination of memory and disk pages and allow users to customize the behavior.
Storage Model[12]
Druid uses segments files to stores its index. A segment file is a basically a columnar storage model consists of three basic column types: timestamp columns, dimension columns and metric columns. This structure allows fast aggregation across different fields.
Citations
13 sources- Apache Druid | Apache® Druid apache.org
- Apache Druid - Wikipedia wikipedia.org
- https://druid.apache.org/druid.html apache.org
- Powered by Apache Druid | Apache® Druid apache.org
- https://druid.apache.org/blog/2011/04/30/introducing-druid.html apache.org
- https://druid.apache.org/blog/2012/10/24/introducing-druid.html apache.org
- Joins | Apache® Druid apache.org
- https://druid.apache.org/docs/latest/dependencies/deep-storage.html apache.org
- https://druid.apache.org/docs/latest/querying/querying.html apache.org
- Frequently Asked Questions | Apache® Druid apache.org
- Introduction to Apache Druid | Apache® Druid apache.org
- Segments | Apache® Druid apache.org
- http://static.druid.io/docs/druid.pdf druid.io