3 ms·
This is not all that novel. Lots of consistent systems have caches. The standard approach is to let the client decide: do you need a 100% consistent value (ve
by lokar 3y ago
This is not all that novel. Lots of consistent systems have caches. The standard approach is to let the client decide: do you need a 100% consistent value (very rare) or would you rather set a staleness threshold. If the cache is not sure it is within that threshold (via some feed of invalidations) the read fails and you try another cache server.
- user32489318 3y agoIn distributed storage! 100% consistent storage (not eventual consistent storage like s3) is still important for many transactional cases.
- belter 3y agoOr you end up with a broken container orchestrator: https://news.ycombinator.com/item?id=38834345 https://news.ycombinator.com/item?id=38834345