eWeekChat

A8: Multicloud will be the future of enterprise cloud computing, and we will continue to see double-digit growth in consumption.

A8: The future of multi-cloud is one where more powerful abstractions (e.g. serverless) allow for more sophisticated strategies. As we’ve seen with other tech paradigms the increased sophistication will make it easier for some and more challenging for others.

A8 Cloud vendor independence is key - nobody wants to repeat the commercial software mistakes of the past. Open source software is the answer - it runs on all clouds, and provides vendor and platform independence #eweekchat

A8: Edge compute will get as much mindshare as cloud native in the core

@dangit_hub Will edge overtake cloud, or merge with it?

@dangit_hub Do you see the need to be on multiple clouds to get geo coverage?

It will merge and form one ubiquitous cloud.

A8: As a result, multicloud as a term will encompass all compute as a service scenarios

Important to see Cloud == Compute as Service, as opposed to Cloud == Data Center in the Cloud

@MarcLinster Yes. To serve consumers and address local regulation and compliance needs across various geographies.

(edited)

My own opinion, edge native will be its own domain as a subdomain of cloud native

@digitalmarks I don't agree on this one. Edge will have a major gravitational pull -- as much or more than cloud.

@MarcLinster For some enterprise clients, absolutely. Majority? Not yet clear to me

A8: In the future multicloud will be more seamless. PAAS is out performing IAAS so there will be less emphasis on the implementation and where the service is running.

Agree to the extent that data provides that gravitational "pull"

re: edge, absolutely! I consider it an abstraction.

A8: The market will be quite mature, as cloud migrations hasten and multicloud is part of the implementations

@MarcLinster Agree. It doesn't make sense for organizations to learn three or four different ways to do the same workload with security and governance.

A7: Not precisely a vendor, but CNCF projects (and their associated vendors)

Who is CNCF?

A7: Multicloud strategies benefit #cloud providers and #hyperscalers first. Solution and service providers who are able to provide integrated cloud services and manage it effectively for reliability, #resiliency and cost optimization will also benefit.

A7 Postgres has benefited tremendously from multicloud (see Stackoverflow developer survey https://insights.stackoverflow.com/survey/2021) - it has become the database of choice on all major clouds #eweekchat

Cloud Native Computing Foundation https://www.cncf.io

(edited)

Cloud native computing foundation to drive open-source projects and solutions.

(edited)

@KPHariHitachi Why hyperscalers first? They find more competition.

A7: @JamesMaguire tks for the acronym check. ;) The Cloud Native Computing Foundation, home of the Kubernetes project and many other container ecosystem projects.

Hyperscalers first because their consumption with multicloud strategy will increase across the board.

A7: The jury is still out. Multicloud offers more options that make it easier to bring a workload and consume more both on premise and in the cloud. Ease of delivering business value drives consumption.

A7: Vendors who provide capabilities in any technology category that can operate consistently across the clouds. Data management, infrastructure configuration, CI/CD tooling, governance and compliance...

A7: Major providers. They’ll be chosen as the primary provider for their reach, which the strategy relies on, as well as the de facto complement to niche players.

A6: That if you’re not doing multi-cloud, you’re doing something wrong. Not to undermine any of the advantages we’ve been discussing, but if you’re happy with a single provider, that’s OK!

A6: Multi-cloud introduces complexity, and you want to go in with your eyes wide open. If a single provider is meeting your business needs, you should really take the time to weigh your motivations, the perceived benefits, against the complexity you are introducing.

A6: The biggest myth with multicloud is that it provides a straightforward approach for increased #reliability, cost efficiency and optimized ways of working.

A6: In reality, having the right design, architecture and operations of a workload in a multicloud environment is a must to unlock the true potential of multicloud.

A6: Going multicloud mitigates vendor lockin

@KPHariHitachi It's anything but straight forward, surely!

A6 IT execs may think that multicloud is easy-it is not. E.g., one can easily drift from RDS Postgres to Aurora for Postgres for a specific project, but that just put an end to the multicloud option. Data gravity is a problem too - apps tend to go where the data is

(edited)

@dangit_hub So true. Multicloud also includes vendor lock-in.

@dangit_hub My point too!

A6: Taking a deliberate, planned approach to abstraction can mitigate some lockin risk. Multicloud in and of itself is no panacea.

Until the vendor changes their pricing or licensing, and then you are stuck. You are back to where you were with conventional software vendors - locked in

Exactly. Multi-cloud is often being locked into multiple clouds.

Which brings us back to two very different multi-cloud strategies: 1. Trying to make everything portable across clouds for future migration, and 2. Assuming things built in any cloud will stay there, and determining which workloads/data should live in each cloud.

(edited)

A6: In a way here, the natural portability of open source in the architecture.

(edited)

Enterprises needs to make this choice and follow through with people / process / technology to achieve it

No doubt those words are often uttered!

@JamesMaguire A5: @HitachiVantara we believe that an effective #multicloud strategy or implementation is underpinned by a strong design and architecture.

(edited)

Infrastructure as Code (IaC). Always. Everywhere. For cloud infrastructure teams, your multicloud platform is your product, and development/operations/security (DevSecOps) teams are the consumers

A5: Here are three key considerations: 1) look at a workload in a holistic manner as compared to individual cloud resources – infrastructure, network, application, data and security etc.

A5: 2) design, build and operate with a right balance of reliability, efficiency and cost management. 3) manage multicloud environments with a consistent and automated set of configuration and policies for seamless integration.

A5: Lean on their vendors to help solve cloud challenges as unbiased experts. Partners and solutions will emerge.

(edited)

A5: Designate a group to own strategy and management. At a minimum, task them with instituting controls around performance and spending. Tools, capabilities, and standards are evolving, and this group should regularly evaluate those in conjunction with stakeholders and real data

A5 Use Postgres - it is available on every cloud PaaS and IaaS. Using Postgres provides complete cloud portability and vendor independence. Outside of Postgres: use standard open source software, not the cloud-specific forks. Avoid lock-in like the plague #eweekchat

A5: We have proven that even for mainly IaaS workloads distributed across multiple CSP's, using a common IaC approach is the single greatest lever to mitigate complexity

@dangit_hub I agree - manual deployment at scale, without Infrastructure as Code is a losing proposition

A5: If a companies objective with multi-cloud is avoiding lock-in, then they have to carefully govern the architecture and services decisions for each project. Easier said than done with the real-world pressures on project velocity.

A5: enterprises can help project teams by building out enterprise-wide best-practices of DevOps processes and tools, technologies, open-source components and multi-cloud software capabilities to leverage.

A5: Choose a partner and platform designed for secure multicloud that can scale and grow as your data needs change.