Redis vs. MemSQL vs. VoltDB

Trello 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.

I'm using Redis to support Sidekiq to support background processing.

The 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).

Caching and Que

Slowly migrating from ASP .Net state service to Redis

400,000 QPS!

For task management (Celery) and shared sessions.

Cache, distributed lock, pub/sub

Replaced memcache and alleviated lots of issues on the spot absolutely amazing caching, with memory-based storage it's a win-win.

Session and caching in Rails apps.

Used as a cache for monitors and reactions, can be used when RethinkDB is having issues.

Redis is used as a socket store

Redis and Resque for background jobs.

memcached 와 비슷한 퍼포먼스를 내면서 persistence 지원을 통해 in-memory cache 의 단점을 충분히 극복합니다. 메인 캐시서버로 사용하고 있습니다.

Caching

Caching layer, transient data storage, message queuing, and chat

cache and pubsub

Redis is used as a complement to MySQL for storing data counts.

We use Redis as a key-value store, a cache, and a message queue. It's a ridiculously fast and simple-to-maintain jack-of-all-trades.

For WordPress object-cache

• On-demand message queue/storage
• Notification queue

We also have support for Redis databases so that developers can interact with their data.

Distributed caching for different applications to use.

I use a lot to organize my queue workers

Session management, Leaderboards, instant messages, and many others use Redis (cluster with Redis Sentinel)

We use Redis for several different things, but majoritively for server or frontend caching, and session management, both things it excels at.

Speed things up a bit.

We use Redis for caching and publish/subscribe coordination for our microservices.

Easy persistence with json semantics that fits my program structure: No searches and no indices where I just have direct references.

Redis 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.

Cache in front of PG DB

Pub/sub event bus.

Key/Value store used as NoSQL data source. It also is used as a cache system.

LRU cache.

Redis is used for caching and advanced key-value storage to maintain quick access objects and counters. It also used to back resque workers

Caching for our API endpoints.

Cache/Message Queue

All data not yet commited to PostgreSQL, lives in multiple redis instances. We are heavy users of lua in redis to enable custom queue behavior.

Messaging queue for Resque (messaging broker)

Redis is used as a message queue for dispatching users' changes for documents.

Loooong term for performance.. Super fast but not suited for prototyping

we use redis for json caching and token storing

HA redis for cluster level shared memory

I used Redis to store subscriber preferences (such as language), for which a database would have been overkill.

Redis is used to cache data which is rarely changed but often requested like huge JSON structures.

Caching and sessions

Cache for data we need fast. Local regions. We sync some tables with either mysql or mongo.

We use it as a fast session storage

Wordpress object cache

Redis is uses in so many places in our stack that we actually can't count it.

Persistent cache, centralized locking, global sessions.

Primary communication bidirectional between NodeJS and Lumen

Use Redis as our cache.

Used for high-speed view and object caching.

Put value, get value...

We used Redis to cache server requests, which cut down response times on most requests by at least 1/10.

Used Redis database and messaging service for a web forum.

Light weight queueing and smart caching for our data collection processes.

Distributed locking, ephemeral counters

Cache backend for Rails app

As our in-memory database, to temporarily store individual object properties and query results, which in turn powers our live feed and quick filtering of driver data.

Fast cache is used to store short term information from devices and detect change in status of the device.

The backend for the express session store.

basic

Queue to speed up requests of long running operations (e.g. sending email, push notifications)

It is used as a caching tool. If a query is made, it is cached in Redis. For 2 minutes, other users see Redis query cache, instead of keeping crawling ESHOT page.

We use it as main cache for service data such as metadata hashes

Used as a caching layer (when we need more functionality than simple key-value storage); keeping lists of online users, used for our smart-assigning feature, keeping track of sliding-window rate limiting information.

We use Redis managed on Amazon ElastiCache.

API Response Caching.

used at talenthouse as our cache layer and non-persistent data.

Experience with Redis a caching layer. Used in several API projects.

We use redis as a cache. Nothing too fancy here. At one point we were using it to cache character information, but we've since moved that entirely to DynamoDB and are evaluating the performance before we bring redis back in.

cache, ETL activities - roll-up. Anything speed-worthy.

Redis is our in-app cache and session storage data layer.

Used as cache at Chaordic, fube and cloudfind.

Best session/cache storage system for Magento. Very simply to integrate.

I 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.

Redis 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.

API 인증토큰 저장
Cache Data 저장

Store key:value pairs for local cache

Provides a super-fast cache layer between our API and database, allowing us to handle surprise bursts of users without overloading database. Response time on a cached request is usually <20ms processing, compared to ~500ms on a heavy database request.

Redis is probably the single piece of software we love the most. We just love its simplicity, speed and we use it for caching data, storing user sessions, and making leaderboards. It just works perfectly for us.

Mostly using it for cache and using it as a distributed queue job broker.

Inter-server communication via PubSub as well as non-relational data storage

Session management.

Queueing

Simple caching, tightly tied into Rails. Optimized caching without any work to implement. Done.

We make extensive use of Redis for our caches and use it as a way to save "semi-permanent" stuff like user-submit settings (that get refreshed on each login) or cooldowns that expire very fast.

We used Redis to implement a locking mechanism for ensuring consistency while multiple users were editing the same file.

缓存、内存数据库

A high performance and full features proxy for redis

Session Storage, Data Caching

Redis makes it easy to synchronize state over multiple nodes in the realtime cluster.

Document Cache

In-memory Key-Value DB used as a cache or as a message broker

Cache and some other small use cases

Saving user session and entity cache.

used with pattern publish/subscribe

Key-value database that runs the site, including click tracking

Lightning fast caching.

Communication channel & fast cache.

We use Redis for a fast and scalable solution to caching data within our API.

We use Redis to optimize our queries handling

Server-side caching

Caching to create highly scalable applications

High performance cache for managing reliable and quick data access