4 ms·
Having an internal network like this that everything on the main AWS network so heavily depends on is just bad design. One does not create a stable high tech sp
by soheil 5y ago
Having an internal network like this that everything on the main AWS network so heavily depends on is just bad design. One does not create a stable high tech spacecraft and then fuels it with coal.
- discodave 5y agoIt's 2006, you work for an 'online book store' that's experimenting with this cloud thing. Are you going to build a whole new network involving multi-million dollar networking appliances?
- jvolkman 5y agoDeveloping EC2 did involve building a whole new network. It was a new service, built from the ground up to be a public product.
- soheil 5y agoNo but one would hope 15 years and 1 trillion dollars later you would stop running it on the computer under your desk.
- discodave 5y agoHehe true! But it's real hard to "move fast and not break things" when you're talking about millions of servers, exabytes of data, and tens of thousands of engineers.
- ripper1138 5y agoMight seem that way because of what happened, but the main network is probably more likely to fail than the internal network. In those cases, running monitoring on a separate network is critical. EC2 control plane same story.
- soheil 5y agoThe entire value proposition for AWS is "migrate your internal network to us so it's more stable with less management." I buy that 100%, and I think you're wrong to assume their main network is more likely to fail than their internal one. They have every incentive to continuously improve it because it's not made just for one client.
- zeckalpha 5y agoWhat would you recommend instead? Control plane/data plane is a well known pattern.