4 ms·
Numbered databases are (de facto) deprecated. Run separate processes, instead. (Redis is single-threaded, anyways. You probably don't want to run production an
by guywithabike 13y ago
Numbered databases are (de facto) deprecated. Run separate processes, instead.
(Redis is single-threaded, anyways. You probably don't want to run production and staging on the same Redis process.)
- dabeeeenster 13y agoStill not a suitable solution IMHO. Now you have to deal with multiple ports, startup scripts etc etc Every other database on the planet has database names pretty much. I LOVE Redis but this is just a bonkers limitation IMHO...
- moe 13y agoNone of the reasons why many traditional databases have multi-tenancy support was ever relevant for redis. And in a world that increasingly moves to containerization you should really look into adding automation to your admin workflow (e.g. ansible). 'port' and 'startup script' should become 'service' and 'template' in your mind.
- janerik 13y agoantirez once commented on this: https://groups.google.com/forum/#!msg/redis-db/vS5wX8X4Cjg/8ounBXitG4sJ https://groups.google.com/forum/#!msg/redis-db/vS5wX8X4Cjg/8...
- stiff 13y agoI have seen this explanation and frankly I find it ridiculous. Multiple databases as a dictionary layer?
- seiji 13y agoNow you have to deal with multiple ports, startup scripts etc etc That's just what happens when you live with production systems. Not every service in the world gives you a dev/staging/production server with "curl github.com/my-bespoke-database/install-and-run.sh" The last place I worked had 60 physical mysql servers. We had to deal with ports and servers and startup scripts quite a bit.
- erichmond 13y agoWith tools like Chef, Puppet, Pallet, Ansible, this is a unbelievably solved problem.