Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It sounds like they want to avoid split-brain scenarios as much as possible while sacrificing resilience. For things like DNS, this is probably unavoidable. So, not all the responsibility can be placed on AWS. If my application relies on receipts (such as an airline ticket), I should make sure I have an offline version stored on my phone so that I can still check in for my flight. But I can accept not to be able to access Reddit or order at McDonalds with my phone. And always having cash at hand is a given, although I almost always pay with my phone nowadays.

I hope they release a good root cause analysis report.



It's not unavoidable for DNS. DNS is inherently eventually consistent anyway, due to time-based caching.


Sure, but you want to make sure that changes propagate as soon as possible from the central authority. And for AWS, the control plane for that authority happens to be placed in US-EAST-1. Maybe Blockchain technology can decentralize the control plane?


Or Paxos or Raft...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: