Looks cool. What would be the prototypical use cases for something like this?<p>I'd imagine something like this would already have been possible with a proxy (i.e. hot swap upstream without closing client connections).<p>Also, any idea how this handles clients that execute scripts via EVALSHA? If a client already loaded the script, wouldn't this break that expectation or does the client contract not allow caching that?
I thought that, with the introduction of redis cluster in 3.x, they were moving away from multiple logical "dbs" that had indicies. Are they going to continue to multiple databases in 4?
Interesting. I can think of a number of scenarios where this makes sense if you're using Redis for caching and you don't have a proxy in your architecture.<p>Does redis cluster only support one database? If that's still the case, then this is probably not available for the larger redis deployments.
Couldn't one achieve the same thing simply by prefixing your DB keys with a blue/green bit and just atomically swap out which prefix should be used for reads?