StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Databases
  4. Databases
  5. Druid vs InfluxDB

Druid vs InfluxDB

OverviewDecisionsComparisonAlternatives

Overview

InfluxDB
InfluxDB
Stacks1.0K
Followers1.2K
Votes175
Druid
Druid
Stacks376
Followers867
Votes32

Druid vs InfluxDB: What are the differences?

Introduction

Markdown code formatting has been applied to the text below to be used on a website. The key differences between Druid and InfluxDB have been identified, highlighting six specific distinctions. The generic and declarative sentences have been extracted and removed for better clarity.

  1. Data Model and Query Language: Druid is column-oriented and supports a multi-dimensional data model, while InfluxDB is a time series database that organizes data in fields, tags, and time. Druid uses a SQL-like query language called Druid Query Language (DQL), whereas InfluxDB uses its own query language called InfluxQL.

  2. Scalability and Performance: Druid is designed for high performance and scalability, with the ability to handle large-scale data sets and complex queries. InfluxDB also offers scalability but is optimized for time series data specifically. Druid achieves better performance for multi-dimensional queries, while InfluxDB excels in querying time series data efficiently.

  3. Storage Format: Druid stores data in compressed, immutable segments that allow for efficient query processing and storage optimization. InfluxDB utilizes a compact binary storage format called the Time-Structured Merge Tree (TSM), which is tailored to optimize time series data storage and retrieval.

  4. Real-time Ingestion: Both Druid and InfluxDB support real-time data ingestion. Druid processes real-time data by ingesting it into real-time indexing tasks, while InfluxDB provides a continuous query capability that allows for real-time data ingestion and processing.

  5. Data Retention Policy: Druid offers native support for both time-based and non-time-based data retention policies. It allows defining data retention rules at the ingestion level. InfluxDB provides data retention policies based on time durations, allowing users to specify the duration for which data should be retained.

  6. Ecosystem and Integrations: Druid has a rich ecosystem with integrations with various data ingestion frameworks, such as Apache Kafka and Apache Samza. It also has integrations with popular BI tools and SQL-on-Hadoop systems. InfluxDB has a growing ecosystem with integrations for data collection, visualization, and alerting tools like Telegraf, Grafana, and Kapacitor.

Summary

In summary, Druid and InfluxDB differ in their data models and query languages, scalability and performance characteristics, storage formats, real-time ingestion approaches, data retention policies, and ecosystem integrations.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on InfluxDB, Druid

Anonymous
Anonymous

Apr 21, 2020

Needs advice

We are building an IOT service with heavy write throughput and fewer reads (we need downsampling records). We prefer to have good reliability when comes to data and prefer to have data retention based on policies.

So, we are looking for what is the best underlying DB for ingesting a lot of data and do queries easily

381k views381k
Comments
Benoit
Benoit

Principal Engineer at Sqreen

Sep 21, 2019

Decided

I chose TimescaleDB because to be the backend system of our production monitoring system. We needed to be able to keep track of multiple high cardinality dimensions.

The drawbacks of this decision are our monitoring system is a bit more ad hoc than it used to (New Relic Insights)

We are combining this with Grafana for display and Telegraf for data collection

155k views155k
Comments
pionell
pionell

Sep 16, 2020

Needs adviceonMariaDBMariaDB

I have a lot of data that's currently sitting in a MariaDB database, a lot of tables that weigh 200gb with indexes. Most of the large tables have a date column which is always filtered, but there are usually 4-6 additional columns that are filtered and used for statistics. I'm trying to figure out the best tool for storing and analyzing large amounts of data. Preferably self-hosted or a cheap solution. The current problem I'm running into is speed. Even with pretty good indexes, if I'm trying to load a large dataset, it's pretty slow.

159k views159k
Comments

Detailed Comparison

InfluxDB
InfluxDB
Druid
Druid

InfluxDB is a scalable datastore for metrics, events, and real-time analytics. It has a built-in HTTP API so you don't have to write any server side code to get up and running. InfluxDB is designed to be scalable, simple to install and manage, and fast to get data in and out.

Druid is a distributed, column-oriented, real-time analytics data store that is commonly used to power exploratory dashboards in multi-tenant environments. Druid excels as a data warehousing solution for fast aggregate queries on petabyte sized data sets. Druid supports a variety of flexible filters, exact calculations, approximate algorithms, and other useful calculations.

Time-Centric Functions;Scalable Metrics; Events;Native HTTP API;Powerful Query Language;Built-in Explorer
-
Statistics
Stacks
1.0K
Stacks
376
Followers
1.2K
Followers
867
Votes
175
Votes
32
Pros & Cons
Pros
  • 59
    Time-series data analysis
  • 30
    Easy setup, no dependencies
  • 24
    Fast, scalable & open source
  • 21
    Open source
  • 20
    Real-time analytics
Cons
  • 4
    Instability
  • 1
    HA or Clustering is only in paid version
  • 1
    Proprietary query language
Pros
  • 15
    Real Time Aggregations
  • 6
    Batch and Real-Time Ingestion
  • 5
    OLAP
  • 3
    OLAP + OLTP
  • 2
    Combining stream and historical analytics
Cons
  • 3
    Limited sql support
  • 2
    Joins are not supported well
  • 1
    Complexity
Integrations
No integrations available
Zookeeper
Zookeeper

What are some alternatives to InfluxDB, Druid?

MongoDB

MongoDB

MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.

MySQL

MySQL

The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.

PostgreSQL

PostgreSQL

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.

Microsoft SQL Server

Microsoft SQL Server

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

SQLite

SQLite

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.

Cassandra

Cassandra

Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

Memcached

Memcached

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

MariaDB

MariaDB

Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

RethinkDB

RethinkDB

RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.

ArangoDB

ArangoDB

A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase