Formerly known as Wikibon
Close this search box.

Action Item: Journey to Multicloud

On 1 November 2018 we conducted an Action Item digital community event to discuss the journey to multicloud. In a digital community event, we gather practitioners to a Crowdchat, present our ideas in video form, and catalyze conversation by pondering a few questions to the smart folk that assemble. We’ll be conducting online Action Items events every Thursday at 9:00 Pacific Time, so feel free to join us, hear what is being said, and offer up your insights.

One benefit of participating is that you have access to everything done or said in this event; the raw data is open. For example, this blog is based on my analysis of this Crowdchat. All told, over 2,000 people have viewed the Crowdchat. There’s a lot of great insight in it that I won’t directly cover here. Here are some of the highlights:

What’s the Difference Between Hybrid Cloud and Multicloud?

I know. It’s sounds like a typical analyst question (as some in the Wikibon community pointed out). But like most goods and services, as cloud proliferates, it specializes. That will affect architectures, service level agreements, and management platforms. Generally, the community took this stance:

  1. Hybrid cloud – same environment, multiple locations. An Azure application that runs in both Azure public cloud and Azure Stack private cloud would be a hybrid cloud application. Same for VMware on-premises and on AWS or IBM Cloud. Or Oracle Cloud at Customer.
  2. Multicloud – multiple environments, multiple locations. A multicloud application exploits services from multiple cloud types. For example, a multicloud recommendation engine might use Salesforce services for customer records, AWS services for ecommerce, and an on-premises fraud detection application.

Thus, in this particular Action Item digital community event, we were discussing (2): How enterprises are going to fashion very rich applications out of services from multiple cloud sources, including private cloud sources.

@stu (in response to @sarbjeetjohal) – hybrid tends to be public+private, multi = many and definitely needs to include Saas, public and private options

@steve_pao – Multicloud generally refers to using multiple publc cloud providers, where hybrid cloud generally refers to mixing private and public clouds.

@discoposse – Multicloud generally refers to using multiple public cloud providers, where hybrid cloud generally refers to mixing private and public clouds.

Are Enterprises Preparing to Bridge Cloud and Legacy Apps In 2019?

High-value legacy applications (HVLA) pose special challenges to a business’s cloud strategy. They’re applications that perform vital operational function and often feature technologies or application attributes that aren’t easy to move to the cloud. It’s one of the key reasons why we believe in the “true private cloud” (TPC) concept. Our research suggests that as TPC technologies improve (including technology originating in AWS, Google, and MSFT Azure), business will attempt to bring the cloud experience on-premises to the HVLA, rather than attempt to “lift and shift” the HVLA and migrate it to the cloud. Of course, we still advise clients that if a cloud-native substitute (e.g., SaaS) is available, that should be the first choice. Wikibon’s research suggests that enterprises are budgeting to begin bridging HVLA and cloud in 2019. Generally, the community agreed: 2019 is the year.

@bjfjallen. The first question customers are looking to answer is whether there’s a Saas option that meets the spirit of the legacy application requirements so they can “outsource” it and focus on business value vs. software development and infrastructure.

@billmew. This needs to be a pragmatic migration. Most of the new workloads are being developed as #cloudnative and most of the low hanging fruit that can be migrated easily has already been moved to the #cloud. Meaning that what is left is the challenging stuff.

@discoposse. Absolute agreement. Field experiences I’m having can back this up. 2019 is bringing a lot of EOS/EOL conversations and enterprises know that building toward cloud models is a win, even on-premises. [EOS = End of Selling; EOL = End of Life.]

What Priorities Should CIOs Focus On in Efforts to Modernize Legacy Apps with Cloud Technology?

If 2019 is the year enterprises start a serious effort to weave HVAL and cloud together, how should they go about doing it? This was an especially fruitful conversation in the community. To summarize the top priorities:

  1. Get the data right. This includes knowing what data has to move, clearly articulating before/after data architectures, and establishing clear IP controls for running things in the cloud.
  2. Move apps that can be moved “As Is” first. Why? Three reasons emerged: (a) gets the business involved early and often; (b) risk mitigation of transformation failure; and (3) focuses reskilling efforts.
  3. Security + Agility. Need to build security into DevOps and AppDev and then accelerate the speed of feature iterations.
  4. Cost and automation. Cost always takes one of the top spots in any list of CIO priorities, but the community especially focused on establishing the trust-based relations required to introduce greater automation to improve productivity (and cost). As @discoposse stated, “Let the machines do the work.”
  5. Have an exit strategy as part of a pragmatic roadmap. Call this one “mitigating the risk of vendor relationship failure.”

@sarbjeetjohal. When doing migrations, the first thing which must happen is Application Portfolio Analysis. Reason is that you ease into cloud consumption as your people and processes have to change as well. So go slow in the beginning. handle low hanging fruit while you adapt.

@morpheusdude. Don’t fall into an Ops-centric trap. Get Dev teams and Business units at the table day 1 to address people and process as much as tools and technology.

@steve_pao. Depends on the maturity of the org in their journey to cloud. The biggest barriers are usually skill sets, so it’s often best for those early in the journey to start with low-risk apps.

@ellenfeaheny. Efficient DevOps across many microservices architecture for pub cloud, dedicated hosted priv cloud, and on-prem. Cloud-first/smart design forces good constraints.

What Role Will Kubernetes Play In Bringing Cloud to HVLA?

Peppered throughout the Crowdchat were references to the role that Kubernetes (K8s) might play in multicloud generally, but specifically in absorbing HVLAs. Generally, the observation is that Kuberetes by itself can help, but needs a fair amount of new invention to cross the gap between stateless container-based apps and typically stateful HVLAs. One area that might be especially fruitful, though, is multicloud management and the possible that Kubernetes emerges as a platform for building “managers of managers.” In any event, the community believes that Kubernetes is at the epicenter of something important.

@discoposse. Containerization came with API-first mentality. It became a programmatic way to deploy workloads. That’s why we loved it but immediately moved on to container scheduling which is the real bottleneck as apps scale.

@sarbjeetjohal. As long as your application can scale horizontally, your bottleneck is infrastructure elasticity and Kubernetes solves that problem. Kubernetes lets you [build] container clusters at a rapid rate and it keeps it manageable.

@billmew. The capabilities of containers (including K8s) has been evolving rapidly. Once containers were Linux-only. Nw you can have Windows apps in containers; even zOS. We should assume that this capability evolution will continue.

Action Item. Work with the business to establish a roadmap for absorbing HVLA applications into cloud strategies. Establish clear priorities based on your enterprise’s needs, but ensuring that you’re maximizing the value of enterprise data is a good place to start.

Article Categories
You may also be interested in

Book A Briefing

Fill out the form , and our team will be in touch shortly.
Skip to content