Recent searches
Search options
A rare, and very in-depth, overview and guidance on “multi-cloud” from Amazon. It still, characteristically, ignores private cloud/on-premises, but sure. https://aws.amazon.com/blogs/enterprise-strategy/proven-practices-for-developing-a-multicloud-strategy/
This is the definition I use: all your computer stuff used for your apps and custom stuff (e.g. IaaS minus SaaS, as pointed out by OP). And, sure, that makes the term kind of meaningless. But…that’s the point? I think it makes it clearer and actionable. https://tanzu.vmware.com/content/blog/state-of-kubernetes-2023-multi-cloud?utm_source=cote&utm_campaign=devrel&utm_content=multicloud20230615
Also, like: yeah: good advice. Figure out what works for you, and do that. Make sure you know the escape plan if needed, don’t get too obsessed with cost over functionality (at first), prove your theories before you make enterprise-wide policy.
The regulatory point is, uh, on-point: just go talk to your auditors and show them what your new tools/stack can do. Most likely, the current governance is based on 2000s, at beast, 2010s assumptions about your app stack.
I guess you could say I'm thinking of hybrid cloud? But, like, could we just have one term that we just reduce down even further?
@cote oh my
“In on-premises environments, companies are driven to large long-term capital investments and are often governed by lengthy, complicated service contracts. These are big one-way door decisions (i.e., difficult and costly to reverse) for companies and necessitate a strong focus on lowering risk.” 
So, AWS Outposts is next to HPE Greenlake, Dell APEX, and other opex options being thrown under the proverbial bus?
Is AWS Local inferior to AWS?
Is Edge/5G chopped liver?
