> while writing up a recipe  on how to work with multiple databases,
> i started to wonder: why is there no way in redis to give databases
> a name? is there any deeper reason?
> if you came across the statement
> SELECT web-sessions
> somewhere in your (or somebody elses) code, wouldn't that be much
> clearer and easier to understand / debug than a cryptic
> SELECT 7
I understand how this can be useful, but unfortunately I consider
Redis multiple database errors my worst decision in Redis design at
all... without any kind of real gain, it makes the internals a lot
more complex. The reality is that databases don't scale well for a
number of reason, like active expire of keys and VM. If the DB
selection can be performed with a string I can see this feature being
used as a scalable O(1) dictionary layer, that instead it is not.
With DB numbers, with a default of a few DBs, we are communication
better what this feature is and how can be used I think. I hope that
at some point we can drop the multiple DBs support at all, but I think
it is probably too late as there is a number of people relying on this
feature for their work.
Salvatore 'antirez' Sanfilippo
"Once you have something that grows faster than education grows,
you’re always going to get a pop culture.", Alan Kay