Or when the devs don’t want to rewrite their schemata in a way that would massively reduce I/O requirements. Then when you lose a cache node, the DB gets slamm

Or when the devs don’t want to rewrite their schemata in a way that would massively reduce I/O requirements. Then when you lose a cache node, the DB gets slammed and falls over, because when the DB team implemented service-based rate-limiting, the teams cried that they were violating their SLOs so the rate limits were bumped waaaay up.