This kind of metastability _should_ be detectable through fairly simple load till failure testing and recovery monitoring. The 10x load cited is a red herring when pulling static config during recovery is their bottleneck
What you don’t know about are all the other attacks that did not impact the service, because the way load testing was performed already lead to some mesures being taken.
Was this a global outage for 90+% of deno deploy hosted projects? “A large chunk” doesn’t give me much faith that it was isolated to any one region
The framework provides a clean way to define expectations and to produce data that can then be visualized in grafana.