People accept a surprising amount of unreliability.
For example, I've been using SharePoint to modify excel files at scale.
We kept running into issues with cache that we would write to a file, the service would respond with success, but then when we read the file, it shows the old cached value, not the new one we just WROTE! And there was no reliable way to check when the newly written value had been completely flushed using that API.
Microsoft will call this 'optimized'. They'll say that caching is good; it's a feature, not a bug!
But really, it's unreliable! It's not doing the job it claims to do.
Microsoft will call this 'optimized'. They'll say that caching is good; it's a feature, not a bug!
But really, it's unreliable! It's not doing the job it claims to do.