Lets say you are doing an
update_option() and because of some temporary network glitches updating the value in Redis/Memcached fails and you end up with a stale cache for a specific option key. The core APIs does not seem to care about the response from
wp_cache_set() and they move forward with the rest of the process. Then the subsequent updates could delete or revert that option value in DB and that could have major consequences for the app depending on what that option value is used for. How do you handle this? How is this handled in large-scale WP setups? Anything that can be improved in core?