tag:blogger.com,1999:blog-768233104244702633.post721935786293684533..comments2023-11-16T03:16:54.746-08:00Comments on The Scale-Out Blog: Life in the Amazon JungleRobert Hodgeshttp://www.blogger.com/profile/05379726998057344092noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-768233104244702633.post-42051186707188359422012-09-04T08:50:59.020-07:002012-09-04T08:50:59.020-07:00@Brian, that's my point. Anyone operating at ...@Brian, that's my point. Anyone operating at scale has seen these issues already and dealt with them or suffered for it. However, Amazon is flakey <i>by design</i> so even small businesses cannot evade building in availability. You can't push it off onto the ops team any more.Robert Hodgeshttps://www.blogger.com/profile/05379726998057344092noreply@blogger.comtag:blogger.com,1999:blog-768233104244702633.post-83716216529292231992012-09-04T07:45:51.137-07:002012-09-04T07:45:51.137-07:00Actually, this is not an Amazon thing. If you went...Actually, this is not an Amazon thing. If you went inside any reliable server infrastructure you would find the same thing. We don't use AWS, but we replicate data two different geographic locations. Everything is a cluster with load balancing. We queue and cache 3rd party services to ensure up time. This is not new. AWS did not cause this to be needed. This has always been needed if you want to stay up. We learned this in 2000. I fear we are failing the new generation since so many people are still learning this.Brian Moonhttps://www.blogger.com/profile/10147638743111625798noreply@blogger.com