4 ms·

So, this would mean every call you make to redis (not just the del) would need to be guarded against all of these reasons you have cited. To me that's just over

So, this would mean every call you make to redis (not just the del) would need to be guarded against all of these reasons you have cited. To me that's just overkill. If transactionality is that important, redis may not be the right tool.

eis 15y ago
Yes you need to make sure all your modifications lead to consistent states. If you don't do this, then you end up with inconsistent states and depending on your app deadlocks. Then it would only be useful as a cache and even then only if the temporary inconsistencies were tollerable. Using a datastore without guaranteeing (and be it only eventual) consistency is calling for trouble for any data that is worth something. Redis CAN be used for many things, but it's not always trivial to do it right even though at first glance it might look so and most web developers are lazy or just don't know better.