DNS go boom https://aws.amazon.com/message/101925/
-
DNS go boom https://aws.amazon.com/message/101925/
It's interesting to consider how you build bulkheads around different zones in your distributed system, especially when colocation is inherently preferred. So you have a distributed system (nice), and it's isolated to the granularity of an availability area (also good), so that all your customers hook themselves up to that one endpoint (ruh roe), to reduce latency and cost (oh no), because physics favors locality (dammit)
-
DNS go boom https://aws.amazon.com/message/101925/
It's interesting to consider how you build bulkheads around different zones in your distributed system, especially when colocation is inherently preferred. So you have a distributed system (nice), and it's isolated to the granularity of an availability area (also good), so that all your customers hook themselves up to that one endpoint (ruh roe), to reduce latency and cost (oh no), because physics favors locality (dammit)
So fundamentally speaking, bulkheads are deliberately introducing significant inefficiency into your system, in order to improve its ability to survive in degraded mode. This is a really good idea, but you need to make people actually *utilize* it somehow or they will take shortcuts. Doing this stuff 'properly' is something which is going to look bad on a cost sheet in the short term, and then in the long term if it works, is going to look like nothing happened.
-
undefined oblomov@sociale.network shared this topic on