so, when I'm thinking about designing for high availability, I start by really digging into what 'high' actually means

Hey everyone, I've been thinking a lot about designing systems that can keep running even if things go wrong, you know, without a ton of downtime. Besides just having backups, what are some of your go-to strategies or architectural patterns for making sure stuff is always available? Are there any specific trade-offs you usually consider when you're trying to balance availability with other things like cost or how complicated it all gets?