3 ms·
> they had downloaded a cached/older version of the software we had uploaded to the same URL This is a great example (to me) of how weak consistency is useful.
by 0xbadcafebee 6y ago
> they had downloaded a cached/older version of the software we had uploaded to the same URL
This is a great example (to me) of how weak consistency is useful. It exposed a problem you otherwise wouldn't notice.
You were deploying offline artifacts to customers without giving the customer the version of the new artifact. Regardless of backend consistency, the customer will not be able to tell (from the URL, anyway) what version they are downloading. Nor will they be able to, say, download the old version if the new version introduces bugs. By changing your deployment method to use unique URLs per version, your customer gains useful functionality and you avoid having to depend on strong consistency (which actually removes expensive requirements).
If you design for weak consistency, your system ends up more resilient to multiple problems.