Apache Druid vs Mimir
A detailed comparison
Compare Apache Druid and Mimir for time series and OLAP workloads
Learn About Time Series DatabasesChoosing 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 Mimir so you can quickly see how they compare against each other.
The primary purpose of this article is to compare how Apache Druid and Mimir 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 Mimir Breakdown
 |
 |
|
| Database Model | Columnar database |
Time series database |
| Architecture | Druid can be deployed on-premises, in the cloud, or using a managed service |
Grafana Mimir is a time series database designed for high-performance, real-time monitoring, and analytics. It features a distributed architecture, allowing for horizontal scaling across multiple nodes to handle large volumes of data and queries. It can be deployed on-prem due to being open source or as a managed solution hosted by Grafana |
| License | Apache 2.0 |
APGL 3.0 |
| Use Cases | Real-time analytics, OLAP, time series data, event-driven data, log analytics, ad tech, user behavior analytics |
Monitoring, observability, IoT |
| Scalability | Horizontally scalable, supports distributed architectures for high availability and performance |
Horizontally scalable |
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.
Mimir Overview
Grafana Mimir is an open-source software project that provides a scalable long-term storage solution for Prometheus. Started at Grafana Labs and announced in 2022, Grafana Mimir aims to become the most scalable and performant open-source time series database for metrics. The project incorporates the knowledge and experience gained by Grafana Labs engineers from running Grafana Enterprise Metrics and Grafana Cloud Metrics at massive scale.
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.
Mimir for Time Series Data
Grafana Mimir is well-suited for handling time series data, making it a suitable choice for scenarios involving metric storage and analysis. It provides long-term storage capabilities for Prometheus, a popular open-source monitoring and alerting system. With Grafana Mimir, users can store and query time series metrics over extended periods, allowing for historical analysis and trend detection. It is especially useful for applications that require scalable and performant storage of time series data for metrics monitoring and observability purposes.
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.
Mimir Key Concepts
- Metrics: In Grafana Mimir, metrics represent the measurements or observations tracked over time. They can include various types of data, such as system metrics, application performance metrics, or sensor data.
- Long-term Storage: Grafana Mimir provides a storage solution specifically tailored for long-term retention of time series data, allowing users to store and query historical metrics over extended periods.
- Microservices: Grafana Mimir adopts a microservices-based architecture, where the system consists of multiple horizontally scalable microservices that can operate independently and in parallel.
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.
Mimir Architecture
Grafana Mimir adopts a microservices-based architecture, where the system comprises multiple horizontally scalable microservices. These microservices can operate independently and in parallel, allowing for efficient distribution of workload and scalability. Grafana Mimir’s components are compiled into a single binary, providing a unified and cohesive system. The architecture is designed to be highly available and multi-tenant, enabling multiple users and applications to utilize the database concurrently. This distributed architecture ensures scalability and resilience in handling large-scale metric storage and retrieval scenarios.
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.
Mimir Features
Scalability
Grafana Mimir is designed to scale horizontally, enabling the system to handle growing data volumes and increasing workloads. Its horizontally scalable microservices architecture allows for seamless expansion and improved performance.
High Availability
Grafana Mimir provides high availability by ensuring redundancy and fault tolerance. It allows for replication and distribution of data across multiple nodes, ensuring data durability and continuous availability of stored metrics.
Long-term Storage
Grafana Mimir offers a dedicated solution for long-term storage of time series metrics. It provides efficient storage and retrieval mechanisms, allowing users to retain and analyze historical metric data over extended periods.
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.
Mimir Use Cases
Metrics Monitoring and Observability
Grafana Mimir is well-suited for monitoring and observability use cases. It enables the storage and analysis of time series metrics, allowing users to monitor the performance, health, and behavior of their systems and applications in real-time.
Long Term Metric Storage
With its focus on providing scalable long-term storage, Grafana Mimir is ideal for applications that require retaining and analyzing historical metric data over extended periods. It allows users to store and query large volumes of time series data generated by Prometheus.
Trend and anomaly detection
By using Mimir for storing long term historical data it can be useful for detecting trends in your metrics and also for comparing current metrics to historical data to detect outliers and anomalies
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.
Mimir Pricing Model
Grafana Mimir is an open-source project, which means it is freely available for usage and does not require any licensing fees. Users can download the source code and deploy Grafana Mimir on their own infrastructure without incurring direct costs. However, it’s important to consider the operational costs associated with hosting and maintaining the database infrastructure.
Get started with InfluxDB for free
InfluxDB Cloud is the fastest way to start storing and analyzing your time series data.
