
James Maguire33


















Q4. How do you recommend addressing these multicloud challenges?

Ramesh Prabagaran
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.

Arnaldo "Arnie" Lopez
A4:
Observability tools can help with managing usage and cost, also need a cloud agnostic security solution to keep your users and data protected
Observability tools can help with managing usage and cost, also need a cloud agnostic security solution to keep your users and data protected
(edited)

BMC Software
A4: Optimize your spend vs. your actual need so that you can proactively avoid unnecessary costs by understanding organic growth trends and future planned events. Like insurance or cell phone plan, it’s important to pick a #cloud provider that is right for your needs & plan ahead

Ganesh Janakiraman
A4: We have leveraged Kubernetes operators that could run in any k8s environment – using cloud agnostic open source or other enterprise software will be critical to success in multi-cloud. There are cross cloud cost or configuration management solutions in the market today.

Cody Hosterman
A4: Ask yourself: "what is my business trying to achieve?" "what are my risks to that result?" if you can answer those it can push towards a decision. Is the main risk time? money? complexity? politics? Work the risks backward

Ramesh Prabagaran
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 underneath"

BMC Software
A4: Ultimately it comes down to making sure you can deliver service levels customers expect without going over budgeted spend. Proactive scenario planning to understand how business driver growth can impact your IT resources and spend is important

Arnaldo "Arnie" Lopez
@GaneshJKRam agreed on the Kubernetes talent, very useful, especially if they know security too

Jeff Wittich
@ramsba agree, workload considerations should be top of mind. this isn't an all or nothing approach
Bernard Golden
A4 Understand the use case you are trying to address. In our work, we've identified 11 different use cases that all use the term 'multi-cloud.' Each providers different benefits and imposes different requirements and constraints. Use case drives everything else.

Lakshmi Sharma
@ramsba agree on DevOps, DEvSecOps tooling and making it simple to build, deploy , debug/monitor the apps.

Ganesh Janakiraman
@ramsba - Interesting thought. Goldplating is definitely bad - in the cloud can be cost prohibitive and unnecessary architectural complexities.

Ramesh Prabagaran
@bernardgolden Nice one. In that same order. Use-case > architectural choice

Ganesh Janakiraman
@bernardgolden - good one. Go multicloud only if you need to.

James Maguire
@bernardgolden @ramsba So that means we have to PLAN our deployment ahead of time???

Lakshmi Sharma
Q4: Make it easy to deploy applications, use standard practices like Terraform providers, automation frameworks , and Multi-Cloud Monitoring and Observability tools.

Mark D. Carlson
@bernardgolden +1 for "Start with the outcomes". However, these need to be actually business-centric outcomes and not just technology goals dressed up to pretend like they are biz goals.

Lakshmi Sharma
Q4: Offer specific use cases with some Code samples , API snippets, that work best for those use cases and a way to deploy those templates/code and APIs integration.

Thomas Graf
Open source and open standards, ideally end-user driven communities. Portability. Requiring app teams to have an data extraction strategy from day one. Don't be afraid to bring cloud concept to on-prem where it makes sense.


