Our beloved products from Adobe, Roku, Spotify, and Flickr went down together with AWS. Our hearts go out to these companies and their users. Amazon Web Services (AWS) is having a major outage today. Widely utilized services like Amazon API Gateway, Lambda, DynamoDB, CloudWatch, CloudTrail, CloudFormation, Autoscaling, Athena and others were affected.
“Multi-cloud is the worst practice” – is it, really? Earlier in August, Last Week In AWS published an interesting and insightful article written by Corey Quinn, the Chief Cloud Economist at The Duckbill Group. The Duckbill Group specializes in reducing the AWS bills for their customers, a much-needed service in today’s cloud environment.
We’ve had an idea for years since we first had to deal with the problem everyone who works with cloud services encountered. We ended up locked into public cloud providers and moving was just too complicated. Our developers were spending a lot of time on managing the cloud infrastructure they could instead dedicate to the innovations they wanted to build.
Going multi cloud presents a challenge: It requires compute and other cloud-native resources from at least 2 cloud providers to be located “nearby” from the perspective of latency. For instance, 5ms and 10ms become natural barriers to federating resources into one pool. Beyond these figures, applications start to break.