Choosing the right database is a critical choice when building any software application. All databases have different strengths and weaknesses when it comes to performance, so deciding which database has the most benefits and the most minor downsides for your specific use case and data model is an important decision. Below you will find an overview of the key concepts, architecture, features, use cases, and pricing models of Apache Druid and OpenTSDB so you can quickly see how they compare against each other.

The primary purpose of this article is to compare how Apache Druid and OpenTSDB perform for workloads involving time series data, not for all possible use cases. Time series data typically presents a unique challenge in terms of database performance. This is due to the high volume of data being written and the query patterns to access that data. This article doesn’t intend to make the case for which database is better; it simply provides an overview of each database so you can make an informed decision.

Apache Druid vs OpenTSDB Breakdown


 
Database Model

Columnar database

Time series database

Architecture

Druid can be deployed on-premises, in the cloud, or using a managed service

OpenTSDB can be deployed on-premises or in the cloud, with HBase running on a distributed cluster of nodes.

License

Apache 2.0

GNU LGPLv2.1

Use Cases

Real-time analytics, OLAP, time series data, event-driven data, log analytics, ad tech, user behavior analytics

Monitoring, observability, IoT, log data storage

Scalability

Horizontally scalable, supports distributed architectures for high availability and performance

Horizontally scalable across multiple nodes using HBase as its storage backend

Looking for the most efficient way to get started?

Whether you are looking for cost savings, lower management overhead, or open source, InfluxDB can help.

Apache Druid Overview

Apache Druid is an open-source, real-time analytics database designed for high-performance querying and data ingestion. Originally developed by Metamarkets in 2011 and later donated to the Apache Software Foundation in 2018, Druid has gained popularity for its ability to handle large volumes of data with low latency. With a unique architecture that combines elements of time series databases, search systems, and columnar storage, Druid is particularly well-suited for use cases involving event-driven data and interactive analytics.

OpenTSDB Overview

OpenTSDB (Open Time Series Database) is an open-source, distributed, and scalable time series database built on top of Apache HBase, a NoSQL database. OpenTSDB was designed to address the growing need for storing and processing large volumes of time series data generated by various sources, such as IoT devices, sensors, and monitoring systems. It was initially developed by StumbleUpon in 2010 and later became an independent project with an active community of contributors.


Apache Druid for Time Series Data

Apache Druid is designed for real time analytics and can be a good fit for working with time series data that needs to be analyzed quickly after being written. Druid also offers integrations for storing historical data in cheaper object storage so historical time series data can also be analyzed using Druid.

OpenTSDB for Time Series Data

OpenTSDB is designed for time series data storage and analysis, making it an ideal choice for managing large scale time series datasets. Its architecture enables high write and query performance, and it can handle millions of data points per second with minimal resource consumption. OpenTSDB’s flexible querying capabilities allow users to perform complex analysis on time series data efficiently.


Apache Druid Key Concepts

  • Data Ingestion: The process of importing data into Druid from various sources, such as streaming or batch data sources.
  • Segments: The smallest unit of data storage in Druid, segments are immutable, partitioned, and compressed.
  • Data Rollup: The process of aggregating raw data during ingestion to reduce storage requirements and improve query performance.
  • Nodes: Druid’s architecture consists of different types of nodes, including Historical, Broker, Coordinator, and MiddleManager/Overlord, each with specific responsibilities.
  • Indexing Service: Druid’s indexing service manages the process of ingesting data, creating segments, and publishing them to deep storage.

OpenTSDB Key Concepts

  • Data Point: A single measurement in time consisting of a timestamp, metric, value, and associated tags.
  • Metric: A named value that represents a specific aspect of a system, such as CPU usage or temperature.
  • Tags: Key-value pairs associated with data points that provide metadata and help categorize and query the data.


Apache Druid Architecture

Apache Druid is a powerful distributed data store designed for real-time analytics on large datasets. Within its architecture, several core components play pivotal roles in ensuring its efficiency and scalability. Here is an overview of the core components that power Apache Druid.

  • Historical Nodes are fundamental to Druid’s data-serving capabilities. Their primary responsibility is to serve stored data to queries. To achieve this, they load segments from deep storage, retain them in memory, and then cater to the queries on these segments. When considering deployment and management, these nodes are typically stationed on machines endowed with significant memory and CPU resources. Their scalability is evident as they can be expanded horizontally simply by incorporating more nodes.
  • Broker Nodes act as the gatekeepers for incoming queries. Their main function is to channel these queries to the appropriate historical nodes or real-time nodes. Intriguingly, they are stateless, which means they can be scaled out to accommodate an increase in query concurrency.
  • Coordinator Nodes have a managerial role, overseeing the data distribution across historical nodes. Their decisions on which segments to load or drop are based on specific configurable rules. In terms of deployment, a Druid setup usually requires just one active coordinator node, with a backup node on standby for failover scenarios.
  • Overlord Nodes dictate the assignment of ingestion tasks, directing them to either middle manager or indexer nodes. Their deployment mirrors that of the coordinator nodes, with typically one active overlord and a backup for redundancy.
  • MiddleManager and Indexer Nodes are the workhorses of data ingestion in Druid. While MiddleManagers initiate short-lived tasks for data ingestion, indexers are designed for long-lived tasks. Given their intensive operations, these nodes demand high CPU and memory resources. Their scalability is flexible, allowing horizontal expansion based on the volume of data ingestion.
  • Deep Storage is a component that serves as Druid’s persistent storage unit. Druid integrates with various blob storage solutions like HDFS, S3, and Google Cloud Storage.
  • Metadata Storage is the repository for crucial metadata about segments, tasks, and configurations. Druid is compatible with popular databases for this purpose, including MySQL, PostgreSQL, and Derby.

OpenTSDB Architecture

OpenTSDB is built on top of Apache HBase, a distributed and scalable NoSQL database, and relies on its architecture for data storage and management. OpenTSDB stores time series data in HBase tables, with data points organized by metric, timestamp, and tags. The database uses a schema-less data model, which allows for flexibility when adding new metrics and tags. The OpenTSDB architecture also supports horizontal scaling by distributing data across multiple HBase nodes.

Free Time-Series Database Guide

Get a comprehensive review of alternatives and critical requirements for selecting yours.

Apache Druid Features

Data Ingestion

Apache Druid supports both real-time and batch data ingestion, allowing it to process data from various sources like Kafka, Hadoop, or local files. With built-in support for data partitioning, replication, and roll-up, Druid ensures high availability and efficient storage.

Scalability and Performance

Druid is designed to scale horizontally, providing support for large-scale deployments with minimal performance degradation. Its unique architecture allows for fast and efficient querying, making it suitable for use cases requiring low-latency analytics.

Columnar Storage

Druid stores data in a columnar format, enabling better compression and faster query performance compared to row-based storage systems. Columnar storage also allows Druid to optimize queries by only accessing relevant columns.

Time-optimized Indexing

Druid’s indexing service creates segments with time-based partitioning, optimizing data storage and retrieval for time-series data. This feature significantly improves query performance for time-based queries. Data Rollups

Druid’s data rollup feature aggregates raw data during ingestion, reducing storage requirements and improving query performance. This feature is particularly beneficial for use cases involving high-cardinality data or large volumes of similar data points.

OpenTSDB Features

Scalability

OpenTSDB’s distributed architecture allows for horizontal scaling, ensuring that the database can handle growing volumes of time series data.

Data Compression

OpenTSDB uses various compression techniques to reduce the storage footprint of time series data.

Query Language with time series support

OpenTSDB features a flexible query language that supports aggregation, downsampling, filtering, and other operations for analyzing time series data.


Apache Druid Use Cases

Geospatial Analysis

Apache Druid provides support for geospatial data and queries, making it suitable for use cases that involve location-based data, such as tracking the movement of assets, analyzing user locations, or monitoring the distribution of events. Its ability to efficiently process large volumes of geospatial data enables users to gain insights and make data-driven decisions based on location information.

Machine Learning and AI

Druid’s high-performance data processing capabilities can be leveraged for preprocessing and feature extraction in machine learning and AI workflows. Its support for real-time data ingestion and low-latency querying make it suitable for use cases that require real-time predictions or insights, such as recommendation systems or predictive maintenance.

Real-Time Analytics

Apache Druid’s low-latency querying and real-time data ingestion capabilities make it an ideal solution for real-time analytics use cases, such as monitoring application performance, user behavior, or business metrics.

OpenTSDB Use Cases

Monitoring and Alerting

OpenTSDB is well-suited for large-scale monitoring and alerting systems that generate vast amounts of time series data from various sources.

IoT Data Storage

OpenTSDB can store and analyze time series data generated by IoT devices, such as sensors and smart appliances, enabling real-time insights and analytics.

Performance Analysis

OpenTSDB’s flexible querying capabilities make it an ideal choice for analyzing system and application performance metrics over time.


Apache Druid Pricing Model

Apache Druid is an open source project, and as such, it can be self-hosted at no licensing cost. However, organizations that choose to self-host Druid will incur expenses related to infrastructure, management, and support when deploying and operating Druid in their environment. These costs will depend on the organization’s specific requirements and the chosen infrastructure, whether it’s on-premises or cloud-based.

For those who prefer a managed solution, there are cloud services available that offer Apache Druid as a managed service, such as Imply Cloud. With managed services, the provider handles infrastructure, management, and support, simplifying the deployment and operation of Druid. Pricing for these managed services will vary depending on the provider and the selected service tier, which may include factors such as data storage, query capacity, and data ingestion rates.

OpenTSDB Pricing Model

OpenTSDB is open-source software, which means it is free to use without any licensing fees. However, the cost of running OpenTSDB depends on the infrastructure required to support the underlying HBase database, such as cloud services or on-premises hardware.