Elasticsearch vs InfluxDB

Need advice about which tool to choose?Ask the StackShare community!

Elasticsearch

33.9K
26.4K
+ 1
1.6K
InfluxDB

1K
1.2K
+ 1
174
Add tool

Elasticsearch vs InfluxDB: What are the differences?

Introduction: Elasticsearch and InfluxDB are both popular open-source databases used in different scenarios. However, they have key differences that set them apart from each other.

  1. Data Model: Elasticsearch uses a document-based data model, where data is stored in structured JSON documents. It provides flexible and schema-less indexing, allowing for dynamic addition of new fields. In contrast, InfluxDB is a time-series database designed specifically for handling time-stamped data. It organizes data into measurements, tags, and fields, optimizing for efficient storage and retrieval of time-based data.

  2. Querying: Elasticsearch is known for its powerful and extensive search capabilities, offering full-text search, filtering, and aggregations across large datasets. It supports complex querying using a query DSL (Domain-specific Language) and offers relevance scoring for search results. On the other hand, InfluxDB focuses more on time-series data querying, providing functions and operators tailored for time-based analysis, such as windowing, downsampling, and continuous queries.

  3. Scalability: Elasticsearch is designed to scale horizontally, allowing for clustering and distributing data across multiple nodes for increased storage and processing capacity. It leverages sharding and replication to ensure high availability and fault tolerance. InfluxDB also supports horizontal scaling, but it is more limited compared to Elasticsearch, often requiring manual sharding and replication configuration.

  4. Data Ingestion: Elasticsearch provides various methods for data ingestion, including bulk indexing, data streaming, and connectors to integrate with other systems like Logstash and Beats. It offers near real-time indexing, where data is indexed and available for search within a short timeframe. InfluxDB, being a time-series database, excels at ingesting and storing high volumes of time-stamped data, often through time-series-specific protocols like Influx Line Protocol.

  5. Data Retention: Elasticsearch is typically used for data retention of short-to-medium term, where data is expected to be frequently updated or expire over time. It offers features like time-based indices and index lifecycle management to manage data retention and archiving. In contrast, InfluxDB is designed for long-term data retention, providing built-in retention policies and the ability to downsample or roll-up data to reduce storage requirements as time goes by.

  6. Use Cases: Elasticsearch is widely used for various use cases beyond time-series data, such as full-text search, log analytics, and data exploration. It serves as a general-purpose distributed search and analytics engine, with a rich ecosystem of plugins and integrations. In comparison, InfluxDB's strength lies in storing and analyzing time-series data, making it a popular choice for monitoring, IoT data, sensor data, and analytics related to time-stamped events.

In Summary, Elasticsearch and InfluxDB differ in their data model, querying capabilities, scalability, data ingestion methods, data retention strategies, and use cases. They cater to different data storage and analysis needs, with Elasticsearch offering flexibility and powerful search features, while InfluxDB specializes in efficient handling of time-series data.

Advice on Elasticsearch and InfluxDB
Rana Usman Shahid
Chief Technology Officer at TechAvanza · | 6 upvotes · 366.9K views
Needs advice
on
AlgoliaAlgoliaElasticsearchElasticsearch
and
FirebaseFirebase

Hey everybody! (1) I am developing an android application. I have data of around 3 million record (less than a TB). I want to save that data in the cloud. Which company provides the best cloud database services that would suit my scenario? It should be secured, long term useable, and provide better services. I decided to use Firebase Realtime database. Should I stick with Firebase or are there any other companies that provide a better service?

(2) I have the functionality of searching data in my app. Same data (less than a TB). Which search solution should I use in this case? I found Elasticsearch and Algolia search. It should be secure and fast. If any other company provides better services than these, please feel free to suggest them.

Thank you!

See more
Replies (2)
Josh Dzielak
Co-Founder & CTO at Orbit · | 8 upvotes · 272.1K views
Recommends
on
AlgoliaAlgolia

Hi Rana, good question! From my Firebase experience, 3 million records is not too big at all, as long as the cost is within reason for you. With Firebase you will be able to access the data from anywhere, including an android app, and implement fine-grained security with JSON rules. The real-time-ness works perfectly. As a fully managed database, Firebase really takes care of everything. The only thing to watch out for is if you need complex query patterns - Firestore (also in the Firebase family) can be a better fit there.

To answer question 2: the right answer will depend on what's most important to you. Algolia is like Firebase is that it is fully-managed, very easy to set up, and has great SDKs for Android. Algolia is really a full-stack search solution in this case, and it is easy to connect with your Firebase data. Bear in mind that Algolia does cost money, so you'll want to make sure the cost is okay for you, but you will save a lot of engineering time and never have to worry about scale. The search-as-you-type performance with Algolia is flawless, as that is a primary aspect of its design. Elasticsearch can store tons of data and has all the flexibility, is hosted for cheap by many cloud services, and has many users. If you haven't done a lot with search before, the learning curve is higher than Algolia for getting the results ranked properly, and there is another learning curve if you want to do the DevOps part yourself. Both are very good platforms for search, Algolia shines when buliding your app is the most important and you don't want to spend many engineering hours, Elasticsearch shines when you have a lot of data and don't mind learning how to run and optimize it.

See more
Mike Endale
Recommends
on
Cloud FirestoreCloud Firestore

Rana - we use Cloud Firestore at our startup. It handles many million records without any issues. It provides you the same set of features that the Firebase Realtime Database provides on top of the indexing and security trims. The only thing to watch out for is to make sure your Cloud Functions have proper exception handling and there are no infinite loop in the code. This will be too costly if not caught quickly.

For search; Algolia is a great option, but cost is a real consideration. Indexing large number of records can be cost prohibitive for most projects. Elasticsearch is a solid alternative, but requires a little additional work to configure and maintain if you want to self-host.

Hope this helps.

See more
Needs advice
on
InfluxDBInfluxDBMongoDBMongoDB
and
TimescaleDBTimescaleDB

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

See more
Replies (3)
Yaron Lavi
Recommends
on
PostgreSQLPostgreSQL

We had a similar challenge. We started with DynamoDB, Timescale, and even InfluxDB and Mongo - to eventually settle with PostgreSQL. Assuming the inbound data pipeline in queued (for example, Kinesis/Kafka -> S3 -> and some Lambda functions), PostgreSQL gave us a We had a similar challenge. We started with DynamoDB, Timescale and even InfluxDB and Mongo - to eventually settle with PostgreSQL. Assuming the inbound data pipeline in queued (for example, Kinesis/Kafka -> S3 -> and some Lambda functions), PostgreSQL gave us better performance by far.

See more
Recommends
on
DruidDruid

Druid is amazing for this use case and is a cloud-native solution that can be deployed on any cloud infrastructure or on Kubernetes. - Easy to scale horizontally - Column Oriented Database - SQL to query data - Streaming and Batch Ingestion - Native search indexes It has feature to work as TimeSeriesDB, Datawarehouse, and has Time-optimized partitioning.

See more
Ankit Malik
Software Developer at CloudCover · | 3 upvotes · 317.6K views
Recommends
on
Google BigQueryGoogle BigQuery

if you want to find a serverless solution with capability of a lot of storage and SQL kind of capability then google bigquery is the best solution for that.

See more
Decisions about Elasticsearch and InfluxDB
Benoit Larroque
Principal Engineer at Sqreen · | 2 upvotes · 132.2K views

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

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Elasticsearch
Pros of InfluxDB
  • 326
    Powerful api
  • 315
    Great search engine
  • 230
    Open source
  • 214
    Restful
  • 199
    Near real-time search
  • 97
    Free
  • 84
    Search everything
  • 54
    Easy to get started
  • 45
    Analytics
  • 26
    Distributed
  • 6
    Fast search
  • 5
    More than a search engine
  • 3
    Highly Available
  • 3
    Awesome, great tool
  • 3
    Great docs
  • 3
    Easy to scale
  • 2
    Fast
  • 2
    Easy setup
  • 2
    Great customer support
  • 2
    Intuitive API
  • 2
    Great piece of software
  • 2
    Reliable
  • 2
    Potato
  • 2
    Nosql DB
  • 2
    Document Store
  • 1
    Not stable
  • 1
    Scalability
  • 1
    Open
  • 1
    Github
  • 1
    Elaticsearch
  • 1
    Actively developing
  • 1
    Responsive maintainers on GitHub
  • 1
    Ecosystem
  • 1
    Easy to get hot data
  • 0
    Community
  • 58
    Time-series data analysis
  • 30
    Easy setup, no dependencies
  • 24
    Fast, scalable & open source
  • 21
    Open source
  • 20
    Real-time analytics
  • 6
    Continuous Query support
  • 5
    Easy Query Language
  • 4
    HTTP API
  • 4
    Out-of-the-box, automatic Retention Policy
  • 1
    Offers Enterprise version
  • 1
    Free Open Source version

Sign up to add or upvote prosMake informed product decisions

Cons of Elasticsearch
Cons of InfluxDB
  • 7
    Resource hungry
  • 6
    Diffecult to get started
  • 5
    Expensive
  • 4
    Hard to keep stable at large scale
  • 4
    Instability
  • 1
    Proprietary query language
  • 1
    HA or Clustering is only in paid version

Sign up to add or upvote consMake informed product decisions

What is Elasticsearch?

Elasticsearch is a distributed, RESTful search and analytics engine capable of storing data and searching it in near real time. Elasticsearch, Kibana, Beats and Logstash are the Elastic Stack (sometimes called the ELK Stack).

What is InfluxDB?

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.

Need advice about which tool to choose?Ask the StackShare community!

Jobs that mention Elasticsearch and InfluxDB as a desired skillset
What companies use Elasticsearch?
What companies use InfluxDB?
See which teams inside your own company are using Elasticsearch or InfluxDB.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Elasticsearch?
What tools integrate with InfluxDB?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

May 21 2019 at 12:20AM

Elastic

ElasticsearchKibanaLogstash+4
12
5146
GitHubPythonReact+42
49
40682
GitHubPythonNode.js+47
54
72275
What are some alternatives to Elasticsearch and InfluxDB?
Datadog
Datadog is the leading service for cloud-scale monitoring. It is used by IT, operations, and development teams who build and operate applications that run on dynamic or hybrid cloud infrastructure. Start monitoring in minutes with Datadog!
Solr
Solr is the popular, blazing fast open source enterprise search platform from the Apache Lucene project. Its major features include powerful full-text search, hit highlighting, faceted search, near real-time indexing, dynamic clustering, database integration, rich document (e.g., Word, PDF) handling, and geospatial search. Solr is highly reliable, scalable and fault tolerant, providing distributed indexing, replication and load-balanced querying, automated failover and recovery, centralized configuration and more. Solr powers the search and navigation features of many of the world's largest internet sites.
Lucene
Lucene Core, our flagship sub-project, provides Java-based indexing and search technology, as well as spellchecking, hit highlighting and advanced analysis/tokenization capabilities.
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.
Algolia
Our mission is to make you a search expert. Push data to our API to make it searchable in real time. Build your dream front end with one of our web or mobile UI libraries. Tune relevance and get analytics right from your dashboard.
See all alternatives