3 ms·
I'd like to pose a Redis question to the community at large. On HN, I keep hearing about how awesome it is, how readable the codebase is, how efficient and well
by pork 15y ago
I'd like to pose a Redis question to the community at large. On HN, I keep hearing about how awesome it is, how readable the codebase is, how efficient and well thought out it generally is.
That's all fine, but there is incredible resistance in many enterprises to adopting new technology. I recently faced a similar problem trying to get people to move to Redis, and the feeling is that there isn't enough "enterprise social proof".
So my questions to anyone who has deployed a large enough Redis cluster (and by cluster, I mean replication, since sharding isn't apparently supported yet):
-- What is the largest instance you have run?
-- How reliable has that instance been?
-- How easy is it to maintain and administer?
-- What are some issues you would warn other enterprise users about?
- antirez 15y agoI can't understand this comment now, after the youporn success story... Isn't this enough for enterprise people? Ok seriously now... Groupon did an event a few days ago about how they use Redis with success, Twitter uses Redis for caching timelines, Github does a good use of Redis, and similarly do many other non trivial companies, like Craigslist, Stack Overflow, Digg, ... Those are not "enterprise" companies, but the problems they solve are not different, so IMHO the real problem is a cultural barrier. I think that this is just a matter of time.
- pork 15y agoSeriously, neither can I, and you're right that it's a culture problem. I am genuinely trying to do my part to overcome that. Towards that, it would be nice to see more in-depth expositions of setups, and above all, an honest description of any issues and problems. I'm trying, antirez, I'm trying... :)
- spenrose 15y agoOne tried-and-true solution is to use it on "non-enterprise" projects (small, invisible, failure-tolerant) within your enterprise, then mention that you've used it, then use it on something slightly less obscure and mention it again ... worked for Linux in the '90's.
- thibaut_barrere 15y agoWhat worked for me: I tried new things (ie: ruby, continuous integration, redis...) first on low-risk projects, then used that feedback as a self-proof (look! it works - maybe it can go a bit further?).
- ironchef 15y agoThe other simple thing to point out is all of the issues with "enterprise" software you guys use. That label doesn't mean software doesn't have bugs. That being said...i agree with the others to use it on smaller projects (to get used to oddities with it, etc.) and to show the "higher ups" ... look..it's fine..we've been using it in X, Y, and Z for months. Also, I think it would become _more_ prevalent once a 10gen / datastax / percona like place pops up for it (so mgmt can put a checkbox next to "support")
- wampwamp 15y agoMy group are using Redis at a really big Canadian company. It's a 'VMware' database if they ever ask! Haha.
- famousactress 15y agoDon't work in enterprise. I'm not joking, and this isn't a trite stab or troll. I'm totally serious. I think most of the companies that folks describe as 'enterprise' shops ought to go away, along with the all of the expensive, broken, 'best practice' mentalities. Also, you don't need proof. You're up against complacency, not suspicion.