Redis

“For redis compatibility, we run redis' own unit test and e2e test suite with every change”

“have no motivation to go back to Redis.”

“I don't think we're using anything in Valkey that wouldn't work in Redis.”

“Redis for external state (added complexity)”

“Redis (optional) for sessions and caching”

“an older one built on top of Redis, and a newer one built on PG + S3”

“Not really interested in moving back to Redis at this point.”

“lambda, sqs, and elasticache/redis costs and the work was done in 1/8th the time”

“We generally try to stay in line with the supported versions of the technologies we use: Postgres, NodeJS, Redis, etc.”

“everything in prod still works on plain ol redis and Postgres”

“in prod, we just switch to our mysql, clickhouse, redis etc cluster”

“We switched from a redis backed queue (bullmq) to rabbit at our company”

“we did end up with lua to talk to redis or memcached to do some traffic shaping at one point.”

“We migrated from an in-house redis queuing system.”

“We migrated of a large redis cluster overnight; 0 software changes.”

“Redis is currently used for caching in cluster mode.”

“I am also excited to start replacing our Redis cache with Solid Cache to make everything simpler and cached longer.”

“In the end we switched back to postgres + redis because it was cheaper.”

“We've migrated staging and testing to a DO Droplet with DO MySQl/Redis stack.”

“Aurora Postgres x 3 for now, a large ES cluster, 2x redis clusters, memcached etc.”

“Our stack is (per country) 3 nodejs services, PostgreSQL, redis and some frontend services.”

“running our backing services (RDS, Elasticsearch, Memcached, Redis) on AWS”

“We added a managed redis, database, and elasticsearch to this.”

“We already use Redis for some things so I implemented a quick proof-of-concept”

“now directly manage our own Redis.”

“it has no test, no type hints, no pluggable error handling, not fall back when the redis instance dies”

“We are using paid dynos but free tier redis and Postgres.”

“We use both MemoryStore and normal instances... we run a redis process on each core and the client picks the right one.”

“Elasticache redis.”

“A little bit of Redis”

“a redis cluster that costs the same as Heroku with far fewer limitations”

“pubsub (on GCP) backed by redis for message storage”

“Celery with RabbitMQ/Redis for task processing.”

“The Rails application is a normal API with Sidekiq (aka Redis) workers, which handle asynchronous tasks.”

“are backed by mysql and redis, etc.”

“a handful more infrastructure services (redis etc.)”

“We solved the problem with redis, nginx and the cheapest naked vps possible.”

“Postgresql, Redis and Docker Compose.”

“We still used redis extensively but not as a persistence layer.”

“Everything related to caching and session handling goes into Redis.”

“We used to have on-prem redis and a devops engineer to manage it, then we moved to redis in the cloud”

“These are the services we used.”

“We run a local instance of send.firefox.com, redis, metabase, docker registry”

“Mission critical systems like our registry, api, redis servers, and much more are all running as fly apps in firecracker.”

“using rq + redis was one less thing to deploy and/or fail.”

“Internally we use Redis sorted sets to merge the errors into one entry on the inbox.”

“our endpoints were still accepting new socket connections without processing responses from backend services (eg redis, other nodejs endpoints, auth services)”

“At work we run a few dozen cache nodes serving several million QPS during peak. We were debating switching some of this workload to memcached from redis”

“The other implementation uses Redis (so, yet another component to take care of) and is quite brittle as well.”

“Redis for cache.”

“we have a custom queue solution and a pool of redis nodes that we have some custom quorum logic around.”

“We run 3 instances of our process on each VM along with Redis taking about 60GB of memory in total”

“Most often we have at least 3 database nodes 3 x nodes, 3 redis nodes, whatever.”

“pushes to REDIS and then deletes with a .25 second delay”

“We run our own MySQL and Redis on an Ec2 instance.”

“Yes, it's a Redis vulnerability (caused by bad config on our part) in one container where the firewall was down.”

“I wrote Gimel[0] - an A/B testing backend using Labmda and Redis... It's used in production for a few months now”

“Using helm has let us define a redis cluster configuration that we know works well”

“We run many different types of data services, mysql/hadoop/hbase/kafka/redis/zookeeper/elasticsearch/etc”

“For development environments we are running MSSQL, Elasticsearch, Mongo, Kafka, Zookeeper, Redis, Memcached”

“We use Redis heavily, but only for ephemeral or reconstructable data.”

“we run redis and elastic search on CentOS”

“if the code needs redis, or elasticsearch or whatever it's easier to spin up a local container”

“Toss a JSON object into redis with a rpush then logstash shoves it in elasticsearch”

“I was using Celery+Redis to handle the schedulation”

“At Uber we use redis as a broker for 10k+ requests per second (pushing 50k one some days) with up to several million items backed up.”

“It could run on one server or (as it did in production) twelve.”

“We do this for all of our services: mysql, redis, sphinx, the web app itself”

“I've been using Redis -- naively, with hashes -- as a lat/lon cache for some path analysis on my website.”

“You still have to have redis, postgresql, and whatever other system dependencies installed.”

“We use an async worker via Redis pubsub to call for expiration on individual files locally on proxy servers”

“We use Redis as a cache in front to reduce the unnecessary repetitive load on MongoDB for common operations.”

“shovels 10 second intervals of data into Redis with disk snapshots turned off”

“we use LAPP (PHP, Postgres) with Laravel, Backbone - also with Redis for caching.”

“I've been using data-only containers to mount directories into these app containers (i.e. Redis and PostgreSQL).”

“We use (Resque/Jesque) redis-backed queues extensively in our applications/APIs”

“the ecosystem has supported all of our needs: Postgresql, redis, rest, soap, 0mq, AWS”

“Redis would have been my last pick to do that. Redis I only use when to keep high-volatile non-essential data in memory”

“We do the same thing for redis, Elasticsearch, etc.”

“in which we run redis + logstash”

“Erlang, haproxy, rabbitmq, redis, postgres, cassandra, chef”

“We use local redis as a cache for the most recent messages.”

“Postgres/Redis/JVM all running on the same machine, as well as Vagrant”

“We use linux for: redis, elasticsearch, HAProxy, DNS (bind), nginx, mail (exim) apache, wordpress, mysql, nexpose, backups, puppet, asterix, android builds and our internal mercurial.”

“We run everysecond and very frequently see "Asynchronous AOF fsync is taking too long"”

“At Instagram we use PostgreSQL, Redis, and Cassandra.”

“Still Postgres (with Slony, multiple clusters), Redis, Memcache, and some Cassandra for newer things”

“significantly meatier servers for our backends running PostgreSQL/Solr/Redis.”

“I have used RedisToGo, and it was one of the worst products I've ever had the displeasure of dealing with.”

“we've had this same experience with every database technology we use - including MySQL and Redis.”

“The Redis MQ Support is heavily utilized, where all offline tasks and sync services go through”

“At my company, we use MongoDB, Postgres, Redis, and Solr”

“we run every Redis master with an attached slave and manually failover for now.”

“We're building a web service driven by PHP, Javascript, Elastic Search, and Redis.”

“I've been using Redis extensively for a while and your tutorial is quite good.”

“At Yammer we use Postgres, Vertica, Redis, Riak, and Memcache.”

“we are currently maintain a social game ... we use Redis as db backend”

“we use for A/B testing. It uses redis to store data”

“I also use Redis and Memcached in production extensively.”