It was one AZ. Kinda surprised those guys are built in a way where a single AZ failure takes them down.

dietr1ch 10 hours ago | parent | next [-]

AWS makes it annoying to be resilient as AZs aren't transparent to their users, so I'm more surprised some were prepared for it.

It seems to me these day people are OK with AWS going down and just blaming it on AWS rather than on themselves for not being prepared for big outages.

"Oh, nothing we can do because AWS/Cloudflare is down"

▲

baronvonsp 9 hours ago | parent [-]

> AWS makes it annoying to be resilient as AZs aren't transparent to their users

What does transparent mean here? AWS is super clear what resources are zonal and provides tons of guidance around making things multi-AZ. AZ outages aren't exactly frequent but they're reasonably likely.

Being susceptible to AZ (or region) outages is very much an architectural decision. Or a bug that needs to be fixed (I'm sure Coinbase didn't YOLO single-AZ, they've undoubtedly learned about some edge case that needs to be fixed). Sure it may not be worth the cost/complexity for some systems but resiliency is like job one for anything in the cloud that costs money when it's down.

	▲	dietr1ch 9 hours ago \| parent [-]
		> What does transparent mean here? Transparent as a system/box can be, meaning that you can't see / know about it. (Yeah, I guess you can read that not transparent as obscure in disclosure of how their system works, but it shouldn't make much sense) > AWS is super clear what resources are zonal and provides tons of guidance around making things multi-AZ. Yeah, they allow people cheaping out for zonal resources and then going down with their zone.

▲

uproarchat 9 hours ago | parent | prev [-]

For a while there was a joke that if us-east-2 goes down it's not as big a deal because everything is down.

	▲	temp0826 8 hours ago \| parent [-]
		Dynamodb going down in us-east-1 essentially causes an all service, worldwide outage