Doesn't this point to a design issue with redis? The single threaded, blocking operation of it
works, but it seems to present more problems than it solves for a large quantity of use cases. While it works, and works quickly for a narrow range of use cases, it comes at a huge loss in flexibility when compared to an SQL DB.
While I think it is possible to use redis well, I'm at a loss for what redis does for the average user, that a decent use of SQL doesn't do. My gut feeling is that if people would spend 30 minutes reading up on how to read a postgres query plan maybe they wouldn't reach for redis so quickly.