(b) go dominantly on one cloud and build apps, infra, tooling for that ... the secondary cloud suffers ... and a few other choices in between. #eweekchat crowdchat.net/s/06bcc

I think there's a definition of multi-cloud thats important to articulate here. Is it independent parallel clouds (with diff workloads in each and not inter-related) or is it different workloads all talking to each other across clouds. The fo... #eweekchat crowdchat.net/s/96bcp

A2. Prior trends continue - industry cloud, workload specific choices (e.g. infra heavy vs analytics etc). Now increasingly cost leverage is a factor...and I think we'll see more of this in the coming months. #eweekchat crowdchat.net/s/16bd6

Apps and data, as we know lead the way. As much as I'd love to say infrastructure choices (e.g. cloud networking, security) weigh in - its generally the apps and data that rule the choices #eweekchat crowdchat.net/s/36bde

Early to cloud customers are trying to get those apps running - so they don't feel the pain of cost as much. Minute you go past 20-30 VPCs etc - the cost suddenly shoots to the forefront. #eweekchat crowdchat.net/s/16bdv

That said - we've seen enough enterprises focus on their careabouts well. If they care about speed of operations, and getting apps to deliver on their digital experience, then cost is the price you pay for that... given current macro climate,... #eweekchat crowdchat.net/s/06bdy

A4. (1) Be clear on the architectural choices driving workload placement in single vs multiple clouds. (2) Invest in skillset, tooling, operations - DevNetOps, DevSecOps etc. #eweekchat crowdchat.net/s/26be2

Interesting quote I heard from a recent Enterprise on multi-cloud networking. "I don't want to gold plate my infrastructure and later find that my apps don't deliver". "I'd rather start with the most problematic apps, and then build infra und... #eweekchat crowdchat.net/s/56beb

A5. Unfortunately there isn't a thing called "right blueprint" for multi-cloud. Too many nuances and considerations (tech stack, latency, operational tools, skill-set) ... and each ends up creating their own version. #eweekchat crowdchat.net/s/96bet

That said - start small with a few workloads that need to operate across clouds, decide if they are independent parallel clouds or you need interaction. If latter, ensure the experience is good before scaling out. Cloud elasticity is great an... #eweekchat crowdchat.net/s/66bez

it becomes unmanageable fairly quickly #eweekchat crowdchat.net/s/66bf1

A6. Oh related but also different. I think use-cases like industry 4.0, autonomous capabilities, gaming, drones etc do make legitimate edge use-cases. However there's also the edge or AI-washing - things that make you go "is that really neede... #eweekchat crowdchat.net/s/26bfg

A7. I think any Enterprise that has been around for 5+ years knows hybrid & multi-cloud together are the new normal & are here to stay. Edge is a good example of this, so are the on-premise ones (hospital floor, manufacturing floor, onsite ma... #eweekchat crowdchat.net/s/66bg5

This does bring up an interesting operating model choice. Do I start with cloud operational model and homogenize that to DC, or the other way around. Or are these 2 going to be different altogether. #eweekchat crowdchat.net/s/96bgf

A8. A lot more diversity - I mean the right cloud for the right workload. Today the app teams are happy to run in the cloud of their choice. Its Infra, operations and common services that poses as an impediment. Some abstractions can help. #eweekchat crowdchat.net/s/66bgk

Also it will be interesting to see if the hyperscalers will whole heartedly start building common services for other clouds. Seen that in GCP Anthos, Oracle to Azure interconnects etc - but nothing mainstream. #eweekchat crowdchat.net/s/76bgn

We should visit this thread in a couple of years :-) #eweekchat crowdchat.net/s/36bh3

(1) Apps and data rule the choices today - but infra & shared services make those choices unbearable at-times... consciously move those security and networking choices to the fore-front, and not "after" the fact #eweekchat crowdchat.net/s/76bh6

(2) Careabouts are different at each stage. What you look at during the first 20 workloads - very different when you are operating at 100 workloads, and very different at 500+. Cost, latency, performance, operational choices, skill-set gap ar... #eweekchat crowdchat.net/s/06bhd