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

InfluxDB

1K
1.2K
+ 1
175
TempoDB

4
11
+ 1
0
Add tool

InfluxDB vs TempoDB: What are the differences?

What is InfluxDB? An open-source distributed time series database with no external dependencies. 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..

What is TempoDB? Store & analyze time series data from sensors, smart meters, servers & more. TempoDB is the first database service for time series data (ex: measuring thermostat temperatures, network latencies, heart rates). Time series is a unique Big Data problem that breaks traditional databases (MySQL, MongoDB, etc). Today, businesses spend months and millions attempting to build solutions to manage all this data and yet still fail to store as much as they need or analyze it effectively. TempoDB is a purpose-built database service that enables businesses to store and analyze massive streams of time series data, so they can learn from the past, understand the present, and predict the future.

InfluxDB and TempoDB are primarily classified as "Databases" and "SQL Database as a Service" tools respectively.

Some of the features offered by InfluxDB are:

  • Time-Centric Functions
  • Scalable Metrics
  • Events

On the other hand, TempoDB provides the following key features:

  • Flexible, powerful API
  • Store as much high resolution (1 ms max) time series data as you need for long range historical analysis
  • We guarantee data availability and protect against loss by replicating each live datapoint 3x and using geographically distributed backup environments

InfluxDB is an open source tool with 16.7K GitHub stars and 2.39K GitHub forks. Here's a link to InfluxDB's open source repository on GitHub.

Advice on InfluxDB and TempoDB
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 · 324.5K 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 InfluxDB and TempoDB
Benoit Larroque
Principal Engineer at Sqreen · | 2 upvotes · 134.6K 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 InfluxDB
Pros of TempoDB
  • 59
    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
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    Cons of InfluxDB
    Cons of TempoDB
    • 4
      Instability
    • 1
      Proprietary query language
    • 1
      HA or Clustering is only in paid version
      Be the first to leave a con

      Sign up to add or upvote consMake informed product decisions

      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.

      What is TempoDB?

      TempoDB is the first database service for time series data (ex: measuring thermostat temperatures, network latencies, heart rates). Time series is a unique Big Data problem that breaks traditional databases (MySQL, MongoDB, etc). Today, businesses spend months and millions attempting to build solutions to manage all this data and yet still fail to store as much as they need or analyze it effectively. TempoDB is a purpose-built database service that enables businesses to store and analyze massive streams of time series data, so they can learn from the past, understand the present, and predict the future.

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

      What companies use InfluxDB?
      What companies use TempoDB?
      See which teams inside your own company are using InfluxDB or TempoDB.
      Sign up for StackShare EnterpriseLearn More

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

      What tools integrate with InfluxDB?
      What tools integrate with TempoDB?

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

      Blog Posts

      What are some alternatives to InfluxDB and TempoDB?
      TimescaleDB
      TimescaleDB: An open-source database built for analyzing time-series data with the power and convenience of SQL — on premise, at the edge, or in the cloud.
      Redis
      Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams.
      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.
      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).
      Prometheus
      Prometheus is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true.
      See all alternatives