Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Operating a large distributed system in a reliable way: practices I learned. Parent comment
Software deliveries/releases can often realistically be non-perfect. (Don't have direct experience with Canary releases TBH though)
In case anything goes wrong any objective evidence which helps to reconstruct the failure scenario is valuable.
Also... Murphy's Law.
>If you've designed software where the whole service can degrade based on the CPU consumption of a single machine.
Typically, if such software is indeed released, I think it will be several CPUs on several hosts.
There are no comments on this comment yet.
Software deliveries/releases can often realistically be non-perfect. (Don't have direct experience with Canary releases TBH though)
In case anything goes wrong any objective evidence which helps to reconstruct the failure scenario is valuable.
Also... Murphy's Law.
>If you've designed software where the whole service can degrade based on the CPU consumption of a single machine.
Typically, if such software is indeed released, I think it will be several CPUs on several hosts.