AWS hearts multi-cloud? It's gonna happen
21–30 of 38 posts
Re: AWS hearts multi-cloud? It's gonna happen
#22...And 8 hours after I wrote this piece, AWS announces their public container registry. [0] Is that the "multi-cloud management tool" The Information heard about? Not exactly how I would have characterized it... [0] https://aws.amazon.com/blogs/containers/advice-for-customers...
Re: AWS hearts multi-cloud? It's gonna happen
#23Speaking of which, has anyone ever seen a company use Anthos? (Software so seems a lower lift)
Anyone seen a company use AWS Outposts? (Hardware so seems hard to imagine anyone actually using but I'd love to be proved wrong).
I'm thinking AWS may realize the hardware model of Outposts is prohibitive so may target a software solution.
Re: AWS hearts multi-cloud? It's gonna happen
#24Re: AWS hearts multi-cloud? It's gonna happen
#25Re: AWS hearts multi-cloud? It's gonna happen
#26Response to Anthos I suppose. Speaking of which, has anyone ever seen a company use Anthos? (Software so seems a lower lift) Anyone seen a company use AWS Outposts? (Hardware so seems hard to imagine anyone actually using but I'd love to be proved wrong). I'm thinking AWS may realize the hardware model of Outposts is prohibitive so may target a software solution.
Re: AWS hearts multi-cloud? It's gonna happen
#27This article is not far off in its prediction that AWS would support multi-cloud natively eventually if that's what the market demands (See also: AWS Marketplace). We are very early in our journey and are multi-cloud already and because we're bootstrapped, cost ultimately decides what we use. And no, I don't mean multi-cloud in a way Netflix does it, but in a way where different parts of our system are hosted wholly…
How do you keep the costs down with egress pricing? If the parts of your applications are distributed through cloud providers you all the time are exporting data to egress. Thats not a cheap concept or did you build your software with this in mind?
egress cost is really not as bad as people expect. if you're willing to pay for double the instances and storage, as required to run in multiple regions/clouds, the bandwidth costs are really not that outstanding in the grand scheme of things.
The usual problem is poor architecture and non-distributed systems. You're not going multi region when everything relies on a single MySQL instance somewhere.
Re: AWS hearts multi-cloud? It's gonna happen
#28Re: AWS hearts multi-cloud? It's gonna happen
#29Ultimately, lock-in in the cloud is a real issue for companies, and the open source community will figure out how to address this issue. AWS and other platforms will fight this a bit, but ultimately they'll adopt whatever approach emerges.
This isn't too say all cloud-services will be commoditized, but the interop between similar services will be.
Re: AWS hearts multi-cloud? It's gonna happen
#30I have no faith in AWS executing on this successfully. I'd imagine an offering like the suggested one would have some kind of: a) UI to inspect the state of other clouds, b) provisioning capability that allows creation of resources in other clouds. On the UI front: - AWS UI toolkit has aged by this point and each day it feels more dated - CloudFormation, as their main cloud management UI is particularly bad (e.g. lim…
Do you have practical experience with Pulumi in large deploymenets? Is it bug free and dependable? I would like to try it out as a Terraform replacement, but but the popularity and corresponding module availability and maturity is hard to match.
https://github.com/hashicorp/terraform-cdk
For those that don’t follow this space very closely - this allows yiu to model infrastructure in your favorite programming language, such as Python.