LocalData

What is #multicloud mean anyway? Can anyone define it?

#multicloud = ability to get unpredictable bills from more than one place! ;)

Multi-cloud in my opinion is the ability to deploy work as appropriate to the cloud of your choice. #localdata

smaller capital outlays make CFO's feel better

Companies are starting to ask the business continuity question. Business leaders view what AWS offers as HA. BC/DR is the ability to spread risk across providers.

Latency is huge issue imo

seriously though, to the degree I see #multicloud it's an app by app decision between AWS, Azure, and Google based on the characteristics of the app. Brings real operational overhead right now though...

@andriven that's classic

Latency will continue to be a major driver to choices for workload location and provider.

yes to "risk mitigation". Honest IT shops realize today that Google/MS/AWS can deliver far more reliability/uptime than on-premise. Years of excacale engineering on hostile networks pay real dividends

@mthiele10 do you mean some workloads on one cloud other workloads on others? silo'd?

IT is always additive, we are seeing companies choosing different clouds (including on-premises) for different functionality/SLA/cost - result is multi-cloud.

I don't see it as silo'd. I see it as distributed risk combined with the ability to leverage best of any given cloud for work purpose.

Multi-cloud is a must. It is like saying you are only going to buy your groceries from Costco. Sucks to drive 10 miles just to get a gallon of milk.

back to the "all eggs in one basket" concern. It might not just be #multicloud but at least multi-region since both #multicloud and multi-region require serious work by the customer.

I see it more of a multi SaaS

In my opinion multi-cloud "complexity" depends on deployment and management tools/strategy.

@johna_white Worse is that your people are only trained how to buy milk from Costco. If there's a shift in the business relationship it could be difficult to impossible to shift to a different provider.

multi-cloud still hard given difference in API's/services - if using the services/API's to get real development acceleration, there's now sunk cost from a development perspective

@andriven I love that term "all eggs in one basket" wrote a blog with that in the title for cloud about 5 years ago. :)

@CTOAdvisor That's why supermarkets are always moving the milk and eggs around so you get lost to buy more other stuff :-)

@andriven Plug for Rubrik. It doesn't seem hard for that type of application. At scale for all other data center apps yes. But for your specific use case, not so much a technical hurdle.

@mthiele10 share that link that would be great Mark

Supermarkets = Regional MSP/CSP

@johna_white whole foods :-) couldn't resist

@johna_white I think that Amazon heard a grocery store analogy for cloud, and that led to the Whole Foods acquisition 😳

Here's the link to my "All eggs in one basket" blog ; https://gigaom.com/2...

I wonder if they will have snow mobile parking?

@CTOAdvisor Thanks. :) I try to keep it at a architecture/conceptual level in these conversations to be a good citizen....but appreciate it and agree.

@csharney Agree that there's lots of O365 and salesforce.com SaaS usage, forcing some multi-PaaS, too!

Kubernetes = DoorDash

@stu I think of it as building the stack higher and higher and eventually some of the lower layers collapse together due to the increasing operational weight of the upper layers and lack of differentiation that we care about on the lower layers.

We see a variety of multi-cloud use case models in our customers - Specific capability I.e., Analytics on GCP and distributed for performance, risk, price

@andriven What's a bit sad is when you have a great product in the lower layers of the stack that is differentiated but no one cares about differentiation in that category anymore.

@mthiele10 Will have to look up that blog post :)

@andriven It's old now, but the theory of why is still true. Thanks.

I just started writing a blog on multi-cloud this morning. There are risks due to businesses not having proper op model for 1 cloud let alone 2 or more

@mthiele10 with the network and interconnect becoming a critical part to select best of breed in designing an end to end business solution. The network is multi-cloud glue!

@andriven Agreed that API's are key

Cloud bursting is definitely one. Elastic compute in cloud, long term storage in datacenter.

federated ID management across multi-organizations , bursting, backup and cost reduction (by moving systems out of managed service provider claws)

just working with a VFX house who had their busiest pilot season ever, bought zero new gear, burst to cloud for everything

Absolutely Archive with Backup a close second - are seeing lots of customers replace tape with cloud archives. Cloud Bursting is great in theory but still really hard in practice given the weight of data and LAN vs. WAN speeds.

Also seeing test/dev drive it...spot pricing on AWS can even help there. This works given an underlying mechanism to move data around and leverage EC2/Azure instances on the fly.

Backup is an easy way to get started with #hybridcloud. On-premises secondary copies, with tiering to cloud.

@andriven agree cloud bursting is a huge challenge, also think if you can make it happen, it provides the most obvious value

There's dreams around DR but still automation/orchestration to be worked out there - it's variable across the space how much is baked out there.

All three but bursting has broader use cases that drive variable revenue. backup and archival must be standard so it's a hard decision different both valuable use cases

I think archive and backup is a dominant use case. I'm not sure for how long. Enterprises will figure out Object storage and offer a comparable cost to cloud based storage.

Archive in hybrid cloud is real. Just needs to be paired with analytics to understand what might need to be retrieved.

@dinisco Absolutely agree - there's huge potential value/market there that no one has truly unlocked yet.

But you have to think beyond the IaaS layer. SAP is a good example. Cloud hosted enterprise apps make sense as cloud providers show greater ability to support the app than the enterprise. SAP in the cloud, bolt on in the private DC.

I'm starting to see an interesting edge case where people arbitrage against discounted bandwidth from the cloud providers. For instance US-Europe connectivity between branch offices may be cheaper routed through an AWS transit VPC

@CTOAdvisor There are even some providers (Cerner for instance) that will host just not just their own app but specific other apps that integrate closely or need to be at LAN speeds to the core app.

@steve_pao cloud-bursting? please explain/defend, because moving data is challenging

Obviously Saleforce dominates the conversation. How many data center managers are building operations based on SF integration?

@CTOAdvisor totally agree, very ez to demonstrate the value of SaaS that works, IaaS is harder

@CTOAdvisor Agree with integrating IaaS layer with apps. Azure get more interesting because of Azure AD + O365.

@andriven All of the serious providers are offering colocation of the ecosystem of enterprise apps.

@CTOAdvisor Hosted @Epic hosted @cerner - there's a long list...

@CTOAdvisor Yes. Amazing how even condo HOA's use prem.force.com!

@CTOAdvisor great point about vertical cloud bc that speaks to hybrid use cases expanding imho

IaaS becomes an enablement for legacy software providers to remain relevant. Elastic compute allows for a business model where they run software they write for the customer with heavy capital investment.

without.

@CTOAdvisor I would add to that also by saying moving from large capital investments to operational model key transition factor

@CTOAdvisor yes agree totally