2 ms·
My problem with the term 'cache' here is that people have expectations about what cache is and when you violate them you tend to discover that they've returned
by hinkley 4y ago
My problem with the term 'cache' here is that people have expectations about what cache is and when you violate them you tend to discover that they've returned the favor.
> push the updates directly to cache instead of relying client to trigger cache filling
You can use cache software to fulfill such a role but it's not exactly a cache anymore, and keeping people from treating it like one is some kind of cat herding.
You're using it as a data store at this point, which for one has very different eviction semantics - exactly 1 copy of each concept, no more, no less. You can store such things in Consul, for instance, and get very low stale read latency. The cache implementation scales higher but breaks sooner. Pick your poison.
- ilyt 4y agoWell, it depends on your data model. Like, if you write only a little (compared to reads), write-thru model of cache (write to cache as well as to backing store) will lose you tiny % of hit ratio at profit of never having to worry about stale data. > My problem with the term 'cache' here is that people have expectations about what cache is and when you violate them you tend to discover that they've returned the favor. That's with everything that have any level of complexity, just see how many people got transaction isolation wrong just because they had some simplistic view on how it works in database they use.