Need advice about which tool to choose?Ask the StackShare community!
InfluxDB vs Redis: 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 Redis? An in-memory database that persists on disk. Redis is an open source, BSD licensed, advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets.
InfluxDB belongs to "Databases" category of the tech stack, while Redis can be primarily classified under "In-Memory Databases".
"Time-series data analysis" is the top reason why over 35 developers like InfluxDB, while over 842 developers mention "Performance" as the leading cause for choosing Redis.
InfluxDB and Redis are both open source tools. Redis with 37.1K GitHub stars and 14.3K forks on GitHub appears to be more popular than InfluxDB with 16.6K GitHub stars and 2.37K GitHub forks.
reddit, Instacart, and Slack are some of the popular companies that use Redis, whereas InfluxDB is used by Impossible Software, SimpleCrypto, and capscale. Redis has a broader approval, being mentioned in 3239 company stacks & 1732 developers stacks; compared to InfluxDB, which is listed in 116 company stacks and 38 developer stacks.
What is InfluxDB?
What is Redis?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose InfluxDB?
Why do developers choose Redis?
- Performance844
- Super fast521
- Ease of use500
- Open source186
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using InfluxDB?
What are the cons of using Redis?
What companies use InfluxDB?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Redis?
Sign up to get full access to all the tool integrationsMake informed product decisions
I use Redis because, based on the case studies I have reviewed, it appears to be the most performant cache database for my Django projects. The ease of configuration and deployment is also a big plus.
Using both higher level view caching as well as low-level QuerySet caching with Redis has allowed me to improve HTTP request times by an order of magnitude.
RedisRedis is a good caching tool for a cluster, but our application had performance issues while using Aws Elasticache Redis since some page had 3000 cache hits per a page load and Redis just couldn't quickly process them all in once + latency and object deseialization time - page load took 8-9 seconds. We create a custom hybrid caching based on Redis and EhCache which worked great for our goals. Check it out on github, it's called HybriCache - https://github.com/batir-akhmerov/hybricache.
InfluxDBInflux doesn't currently natively support horizontal distribution. Hard to recommend it until they implement that.
RedisRedis is used for storing all ephemeral (that's data you don't necessarily want to store permanently) user data, such as mapping of session IDs (stored in cookies) to current session variables at Cloudcraft.co. The many datastructures supported by Redis also makes it an excellent caching and realtime statistics layer. It doesn't hurt that the author, Antirez, is the nicest guy ever! These days, I would be really hard pressed to find any situation where I would pick something like Memcached over Redis.
RedisTrello uses Redis for ephemeral data that needs to be shared between server processes but not persisted to disk. Things like the activity level of a session or a temporary OpenID key are stored in Redis, and the application is built to recover gracefully if any of these (or all of them) are lost. We run with allkeys-lru enabled and about five times as much space as its actual working set needs, so Redis automatically discards data that hasnโt been accessed lately, and reconstructs it when necessary.
RedisThe UI has message inbox that is sent a message when you get a new badge, receive a message, significant event, etc. Done using WebSockets and is powered by redis. Redis has 2 slaves, SQL has 2 replicas, tag engine has 3 nodes, elastic has 3 nodes - any other service has high availability as well (and exists in both data centers).
RedisRedis makes certain operations very easy. When I need a high-availability store, I typically look elsewhere, but for rapid development with the ability to land on your feet in prod, Redis is great. The available data types make it easy to build non-trivial indexes that would require complex queries in postgres.
InfluxDBWe use InfluxDB as a store for our data that gets fed into Grafana. It's ideal for this as it's a lightweight storage engine that can be modified on the fly by scripts without having to log into the server itself and manage tables. The HTTP API also makes it ideal for integrating with frontend services.
RedisI use Redis for cacheing, data storage, mining and augmentation, proprietary distributed event system for disparate apps and services to talk to each other, and more. Redis has some very useful native data types for tracking, slicing and dicing information.
InfluxDBTo track time-series of course, utilizing few retention rules and continuous queries to keep time-series data fast and maintanable
InfluxDBInfluxDB ingests information from various sources (mostly Telegraf instances) into one place for monitoring purposes.
InfluxDBAll our metrics go through InfluxDB, both applicative and system