40 engineers on Hacker News describe using memcached first-hand: 4 endorse it, 2 regret it, 0 are mixed.
“memcache had little to no observability, it made debugging cache issues a nightmare.”
regret · production · Mikushi · 2023-06-20 · source ↗ · wrong label?“We use memcached heavily in PROD but I would be hard pressed to replace it with an upstart competitor”
endorse · production · aftbit · 2021-12-12 · source ↗ · wrong label?“First memcache and then Redis sessions were a continuous centeralized source of failure we could remove”
regret · production · donatj · 2018-08-30 · source ↗ · wrong label?“We've just put so much work into making memcached reliable and easy to understand for developers”
endorse · production · gooeyblob · 2017-01-19 · source ↗ · wrong label?“for serving up API content from Memcache/MySQL - it is blazing fast with minimal footprint.”
endorse · production · blantonl · 2012-05-17 · source ↗ · wrong label?“the performance of memcache for what we use it for is better than redis.”
endorse · production · jedberg · 2011-02-27 · source ↗ · wrong label?“Aurora Postgres x 3 for now, a large ES cluster, 2x redis clusters, memcached etc.”
neutral · production · wlll · 2022-10-20 · source ↗ · wrong label?“running our backing services (RDS, Elasticsearch, Memcached, Redis) on AWS”
neutral · production · geoffharcourt · 2022-10-04 · source ↗ · wrong label?“I implemented a cache in there (early use of Memcache.”
neutral · production · carapace · 2022-07-22 · source ↗ · wrong label?“memcached would occasionally return corrupted data, that python couldn't un-pickle into an object”
neutral · production · Izkata · 2020-09-24 · source ↗ · wrong label?“tune the configuration for postgres and memcached to allocate resources in an appropriate way”
neutral · production · tabbott · 2019-12-02 · source ↗ · wrong label?“I have utilized ElasticSearch, Redis, couchbase and memcached for specific caching or search purposes”
neutral · production · davismwfl · 2018-12-28 · source ↗ · wrong label?“When I compared IncludeOS against the production kernels we run for memcache they were 1.5x bigger.”
neutral · production · tinktank · 2018-08-27 · source ↗ · wrong label?“causing memcached requests to get stuck”
neutral · production · madaxe_again · 2016-12-15 · source ↗ · wrong label?“lots of Thrift RPCs, and plenty of memcache”
neutral · production · boulos · 2016-11-11 · source ↗ · wrong label?“For development environments we are running MSSQL, Elasticsearch, Mongo, Kafka, Zookeeper, Redis, Memcached”
neutral · production · paultyng · 2016-11-01 · source ↗ · wrong label?“it's still not as fast as when we run memcached on AWS.”
neutral · production · optionalparens · 2015-11-01 · source ↗ · wrong label?“two memcache servers and 3 webservers behind a load balancer”
neutral · production · jakejake · 2015-06-23 · source ↗ · wrong label?“Do a failover from your master to the replica inside. 9) Same for memcached”
neutral · production · roncohen · 2014-10-23 · source ↗ · wrong label?“if we lost a single memcache server, it caused multi-gets that included the lost server to fail completely or hang”
neutral · production · rbranson · 2014-09-15 · source ↗ · wrong label?“in production I'm caching the more complex queries with memcached”
neutral · production · davb · 2013-11-19 · source ↗ · wrong label?“Elasticache has definitely been a winner and allowed us to replace our dedicated memcache instances.”
neutral · production · blantonl · 2012-12-19 · source ↗ · wrong label?“They all run OpenJDK on them and infrastructure items such as memcached, Postgres, couple of MQ solutions.”
neutral · production · meaty · 2012-12-08 · source ↗ · wrong label?“Still Postgres (with Slony, multiple clusters), Redis, Memcache, and some Cassandra for newer things”
neutral · production · zeeg · 2012-11-22 · source ↗ · wrong label?“our application servers (running Django, memcached and celery workers)”
neutral · production · simonw · 2012-11-13 · source ↗ · wrong label?“Add memcache to cache queries, and use Varnish as a caching proxy.”
neutral · production · 1 yr · byoung2 · 2012-11-11 · source ↗ · wrong label?“regularly run a five-VM stack (frontend, backend, memcached, database, Puppetmaster”
neutral · personal · eropple · 2012-11-04 · source ↗ · wrong label?“At the other extreme, we have to run memcached on windows otherwise ops will get all antsy.”
neutral · production · gouranga · 2012-04-27 · source ↗ · wrong label?“We run a WordPress instance just as a CMS that then gets pulled into memcache to be served up within our site.”
neutral · production · kevinpet · 2012-03-30 · source ↗ · wrong label?“There weren't a lot of memcached evictions, the db was doing fine, server loads were normal, etc.”
neutral · production · smokinn · 2011-11-18 · source ↗ · wrong label?“We run multiple Ruby processes per CPU so that when one process is waiting for the db or memcache, another can be doing useful work”
neutral · production · wladimir · 2011-10-05 · source ↗ · wrong label?“Currently using memcached (not memcachedb) for caching”
neutral · production · code_duck · 2011-06-23 · source ↗ · wrong label?“At Yammer we use Postgres, Vertica, Redis, Riak, and Memcache.”
neutral · production · bkudria · 2011-06-22 · source ↗ · wrong label?“a generic 'asset' module implementing something akin to ActiveRecord on the standard DB with memcache support”
neutral · personal · 0.8 yr · nikcub · 2010-11-19 · source ↗ · wrong label?“we use memcached to cache almost everything”
neutral · production · schammy · 2010-10-10 · source ↗ · wrong label?“I also use Redis and Memcached in production extensively.”
neutral · production · mmaunder · 2010-09-29 · source ↗ · wrong label?“We switched from Apache to nginx and are now running in a full MySQL / python / fcgi / nginx / memcached environment.”
neutral · production · omarish · 2010-06-29 · source ↗ · wrong label?“I was being warned off Memcached in Java... literally two years after I had it in production at BCC.”
neutral · production · patio11 · 2010-05-20 · source ↗ · wrong label?“I'm still using Memcache for a few legacy pieces”
neutral · production · rit · 2010-03-25 · source ↗ · wrong label?