A CTO’s Guide to Cloud-Native: Answering the Top 10 FAQs

Cloud-native is emerging as a concept and more for leveraging cloud computing. We answer the most common client questions related to the multiple uses of the term that will guide CTOs and enterprise architecture and technology innovation leaders to make sound decisions.

Overview

Key Findings

• Enterprise architecture and technology innovation leaders are already investing in cloud-native initiatives for many reasons, including digital transformation.?Digital transformation efforts require real change at the business level. Cloud is necessary, but not sufficient, for that change.
• The interest in cloud-native is directly a result of interest around cloud computing?itself. While hype has somewhat subsided, cloud adoption is growing and mainstream today. It is enabling infrastructure and application modernization as well as migration. Organizations simply want to take advantage?of cloud.
• The confusion around the meaning and definition of cloud-native is a result of multiple interpretations of the term becoming widely used. Some of these interpretations are contradictory.?There is considerable “cloud-native washing” that is attributable to vendors and users.
• Concepts such as cloud-native (and others such as multicloud) are increasingly showing up in organizations’ cloud strategies as principles that drive cloud decision making.?Cloud-native is a concept that is not binary. Rather, it can be expressed in degrees or on a continuum. The more something aligns with core cloud characteristics, the more we consider it to be cloud-native and the more cloud-native outcomes can be enabled.

Recommendations

CTOs and enterprise architecture?and technology innovation leaders driving?business transformation through technology innovation should:

• Improve the likelihood of success by examining and learning about the cloud-native concept. Establish a strong business and technology linkage, and identify appropriate use cases before embarking on cloud-native initiatives.
• Use more precise terms such as “container-native” and “cloud service provider (CSP)-native” when appropriate, rather than “cloud-native,” to better describe and minimize confusion. Cloud-native can be applied to architecture, infrastructure, applications or operations, as well as thinking.
• Refrain from avoiding the use of the term “cloud-native,” but be prepared to explain what you mean. Focus on the actual outcomes enabled and desired. The more their use cases align with the core cloud attributes, the more likely they will be to recognize the full benefits of using cloud.
• Make informed decisions regarding the extent to which they invest in cloud-native for traditional workloads and processes. The investment required to move existing applications to become cloud-native may not be worth the expense in some cases.?Be realistic about what portability can be achieved, and at what cost.?Also, assess the real value of portability; organizations can go to extreme measures to ensure a level of portability that is not?needed.

Strategic Planning Assumption

By 2025,?cloud-native platforms?will serve as the foundation for more than 95% of new digital initiatives, up from less than 40% in 2021.

Introduction

“Cloud-native” has been growing in popularity as a term. Referring to optimally leveraging cloud characteristics, it is increasingly being used as a principle in cloud strategies and?digital transformation efforts. We answer the most common client questions (summarized in Table 1) that will help guide CTOs and enterprise architecture and technology innovation leaders to benefit from and adopt cloud-native where appropriate.

Table?1:?CTO’s Top 10 FAQ on Cloud-Native

What is cloud-native, and why is everyone so excited about it?

Cloud-native refers to something created to enable or optimally leverage cloud characteristics.?Cloud-native excitement is a direct result of excitement around cloud computing itself. Organizations simply want to take advantage?of cloud.

Why is there so much confusion around cloud-native?

The confusion around the term “cloud-native” is a result of multiple interpretations of the term becoming widely used. Some of these meanings are contradictory.

How does cloud-native compare with multicloud and hybrid cloud?

Cloud-native represents a concept that applies to multi- and hybrid?cloud.?Cloud-native applies in both hybrid and multicloud scenarios.

Are cloud-native and distributed?cloud?synergistic?

Synergy lies primarily in the path to?distributed cloud utopia.?There are multiple paths to the ideal future in which public cloud services can be seamlessly delivered to any location.

How does cloud-native impact your overall cloud strategy?

Cloud-native (and other terms) are increasingly showing up in organizations’ cloud strategies as principles that drive cloud decision making.

How do we assess vendor claims about cloud-native?

Assess vendor claims with skepticism. Focus on the outcomes you want from using cloud rather than focusing purely on the definition of cloud-native.

Is moving to cloud-native the same as digital transformation?

Digital transformation requires change at the business model level and requires effective leverage of digital capabilities, including cloud. Use of cloud technologies and cloud-native approaches does not guarantee transformation at the digital business level, but can be a key technology enabler for digital transformation.

What are the common use cases for cloud-native?

The primary driver for cloud-native is a desire to “get the most out?of cloud.”?What drives people to cloud-native varies by the meaning of the term.

How does cloud-native affect architecture?

Cloud-native can affect architecture in multiple ways.?CSP-native and container-native?approaches have an?impact?on overall architecture. Unsurprisingly, it is when the term “cloud-native” refers to cloud-native architecture?when the most impact is seen.

Is “lift and shift” the opposite of cloud-native?

At a very high level, yes, it is a type of?opposite. While there may be some cloud benefits, the possibility to optimally leverage cloud characteristics is very small.

Source: Gartner (December 2021)

Analysis

Examine and Learn About the Cloud-Native Concept

Much confusion exists about the cloud-native concept. To make matters worse, different people use the term “cloud-native” in different ways. To help clarify this relatively new concept for you, we’ve answered the 10 questions that clients ask us most often about it. Read on to increase your understanding. It could help unlock the power of cloud computing for your organization.

No. 1: What Is Cloud-Native, and Why Is Everyone So Excited About It?

Cloud-native excitement is directly a result of excitement around cloud computing itself. While hype has somewhat subsided, cloud adoption is?growing and?is now mainstream. Organizations simply want to take advantage?of cloud.

Gartner defines cloud-native as something created to enable or leverage cloud characteristics. Those cloud characteristics are part of the original definition of cloud computing?(see Note?1) and include capabilities delivered as a service that are scalable and elastic, metered by use, service-based, ubiquitous by means of internet technologies, and shared.

The term “cloud-native” is often used as an adjective. There can be cloud-native thinking, architecture, infrastructure, applications or operations, for example.

No. 2: Why Is There So Much Confusion Around Cloud-Native?

Quite simply, the confusion around cloud-native is a result of multiple meanings of the term?becoming widely used?(see Figure 1). Some of these meanings are contradictory.

Figure 1: Cloud-Native Terminology

We identify four different uses of the term.

First is Gartner’s definition — something is cloud-native if it is optimally leveraging or implementing cloud characteristics.

Second is an architecture-focused view — adhering to architectural principles, such as Gartner’s?LIFESPAR?or 12-factor applications. This approach is popular with those who are very deep into architectural approaches, but is in no way the most common use of the term. It does, however, reinforce Gartner’s overall definition, applying an architectural perspective to leveraging and implementing cloud characteristics.

Third is CSP-native. This is actually the most common interpretation (see Figure 21). It basically means the use of the native features of the cloud platform. Examples include platform as a service, availability zones or serverless. If you’re using Amazon, then you’re using the native features of Amazon Web Services (AWS), such as Amazon Relational Database Service (Amazon RDS), AWS Lambda and AWS Elastic Beanstalk. A better term to use to describe this is “CSP-native” or a vendor-specific term such as “AWS-native.”

Fourth is container-native. This is a focus on specific technologies such as containers and Kubernetes. It is largely driven by an organization called the Cloud Native Computing Foundation (CNCF), which promotes these technologies. A better term to describe this would be container-native or Kubernetes-native.

In particular, the third and fourth definitions are contradictory; use of containers is not required to be cloud-native.

Figure 2: What Best Describes Cloud-Native?

No. 3:?How Does Cloud-Native Compare With Multicloud and Hybrid Cloud?

It is best to think of hybrid cloud and multicloud as being along two separate dimensions (see Figure 3). Multicloud spans across public clouds, as multiple public cloud providers are involved. Hybrid cloud spans between public and private cloud. Private cloud doesn’t have to be on-premises, but it often is. There is also hybrid IT, which removes the actual cloud requirement. The terms?“private?cloud” and “hybrid cloud” require that there be actual cloud computing. True private clouds are rare, and most on-premises implementations are better described as cloud-inspired virtualization and automation.

Figure 3: Multicloud and Hybrid Cloud Concepts

Cloud-native represents a layer above the multi- and hybrid cloud concepts. Cloud-native applies in both hybrid and multicloud scenarios, and it applies using both of the popular, yet contradictory, CSP-native and container-native interpretations (see Figure 4).

Figure 4: Cloud-Native and Multicloud

No. 4: Are Cloud-Native and Distributed Cloud?Synergistic?

Distributed cloud is the distribution of public cloud services to different physical locations while operation, governance and evolution of the services remain the responsibility of the public cloud provider. Distributed cloud brings together edge, hybrid and new use cases for cloud computing. It represents the future?of cloud?and specifically addresses the issue of location. Whereas cloud does not restrict location, it is perceived as tied to its most common configuration — centralized. Enterprises are advancing use cases of cloud computing in ways that deliver it at the point of need using distributed cloud. Cloud-native benefits should be achievable whether consuming cloud services from a central, public cloud or distributed cloud.

There is synergy between cloud-native and distributed cloud. It lies primarily in the path to distributed cloud utopia.?There are multiple paths to the ideal future in which public cloud services can be seamlessly delivered to any location and be consistent and managed, as well as have the flexibility of multicloud (see Figure 5).

One path is to extend the cloud providers ecosystem to deliver services in a distributed fashion. This path corresponds to the CSP-native interpretation of cloud-native. The advantage of this model is that the cloud provider has a great deal of control and can deliver a rich environment across a number of distributed models. The disadvantage is that it is a closed environment driven by a single provider.

A second path focuses on supporting a multicloud environment emphasizing portability of applications and delivery of public cloud services across a variety of cloud IaaS and enterprise data center models. This path makes use of containers and corresponds to the container-native interpretation of cloud-native. The advantage of this model is that it allows for delivery of cloud applications and services across the widest variety of infrastructure models. The disadvantage is that it is often a minimalistic, least-common-denominator approach that does not deliver as complete a set of services as a closed ecosystem, and requires the enterprise to take on more management responsibilities.

Figure 5: Paths to Distributed Cloud Utopia

In either case, or following either path, cloud-native outcomes should be achievable assuming that the architecture, implementation and operations strictly adhere to cloud principles.

No. 5: How Does Cloud-Native Impact Your Overall Cloud Strategy?

Concepts such as cloud-native (and others such as multicloud) are increasingly showing up in organizations’ cloud strategies. They primarily show up as principles that drive cloud decision making. These principles are instrumental in bringing a cloud strategy to life, and in unlocking the power of cloud by using the concepts described in the cloud strategy cookbook.

In particular, cloud-native and multicloud can potentially be either in conflict or reinforce each other. This is dependent on which meaning is desired as the principle. (There are similar varying and confusing uses of the term “multicloud” as well.) Container-native, leveraging containers for some degree of portability, reinforces a multicloud architecture goal. CSP-native has the opposite effect, encouraging use of features specific to a CSP.

No. 6: How Do We Assess Vendor Claims About Cloud-Native?

Assess vendor claims about their cloud-native capabilities with skepticism. Vendors use the latest popular buzzwords to sell their offerings — cloud-native is just the latest example. Expect vendors to describe their offerings as “cloud-native” to promote them, regardless of how cloud-native their offerings actually may be.

Vendors have amplified confusion on the topic by their use of multiple meanings. For example, some have made containers and Kubernetes synonymous with cloud-native (in other words, container-native), while some promote use of their native platform capabilities (in other words, CSP-native). This type of claim can be taken to an extreme — a claim that cloud-native doesn’t even require cloud. It is possible to have containers and container-native approaches without cloud computing, but in order to be cloud-native, the basic cloud characteristics must be leveraged or enabled — something very difficult to do without cloud computing. The best that can be achieved is a type of cloud-inspired capability.

Cloud-native is a concept that is not binary. Rather, it can be expressed in degrees or on a continuum. The more something aligns with core cloud characteristics, the more we consider it to be cloud-native and the more cloud-native outcomes can be enabled.

Focus on the outcomes you want from using cloud rather than focusing purely on the definition of cloud-native. The more your use cases align with the core cloud attributes, the more likely you are to recognize the full benefits of using cloud.

No. 7: Is Moving to Cloud-Native the Same as Digital Transformation?

Cloud initiatives and digital transformation efforts often occur simultaneously. Sometimes the terms are used somewhat interchangeably, which can be confusing.

If digital transformation efforts are to be truly transformative, then real change is necessary. Cloud (and cloud-native, meaning optimally leveraging cloud) is necessary, but not sufficient, for that change. Change at the digital transformation level requires change at the business model level and requires effective leverage of digital capabilities, including cloud. However, use of cloud technologies and cloud-native approaches does not guarantee transformation at the digital business level.

No. 8: What Are the Common Use Cases for Cloud-Native?

The primary driver for cloud-native is a desire to “get the most out?of cloud.” As the cloud itself means different things to different constituencies, it is not surprising that this can mean different things. What drives people to one or another of these approaches varies — once again, differentiated by the interpretation of the term (for example, container-native and CSP-native):

• Container-native use cases obviously involve use cases for containers, of which there are several common ones. These include agility, portability and resiliency. There are others as well, such as management and development ease.?While all are potentially cloud-native in nature (taking a broad view), in practice, it is the one most commonly associated with cloud-native.
• CSP-specific leverage is common in myriad use cases. There are too many to list as leverage of the CSP-specific capabilities are often needed to obtain performance and functionality goals, and are often a large part of a best-of-breed principle driven strategy.

It is essential to be realistic about what portability can actually be achieved, and at what cost. Not all workloads need to be portable. Use of CSP-specific features may be needed, but these capabilities should be used “with your eyes open,” and you must be keenly aware that you are doing so and must see the benefit. Many analogies and lessons can be derived from experiences with earlier portability technologies and claims — most notably Java. The end result in that case was use of Java application servers that delivered on approximately 80% portability, not 100%. This is a useful accomplishment and can be viewed as desirable in cloud-native portability scenarios as well.

Organizations should make informed decisions regarding the extent to which they invest in cloud-native for traditional workloads and processes. The investment required to move existing applications to become “cloud-native” may not be worth the expense in some cases.

No. 9: How Does Cloud-Native Affect Architecture?

Cloud-native (in its multiple meanings) can affect architecture in multiple ways. CSP-native and container-native approaches have an impact on overall architecture. However, unsurprisingly, it is when the cloud-native architecture is meant that the most impact is seen.

Cloud-native architecture is the set of application architecture principles and design patterns that enables applications to fully utilize the capabilities provided by cloud computing. Cloud-native applications are architected to be latency-aware, instrumented, failure-aware, event-driven, secure, parallelizable, automated and resource-consumption-aware (LIFESPAR).

Many organizations are employing cloud-native architectural approaches as they move their application workloads to cloud. Cloud-native principles and patterns enable applications to operate efficiently in a dynamic environment and make the most of cloud benefits. Organizations that simply “lift and shift” legacy applications often find that the applications perform poorly, consume excessive resources and aren’t able to fail and recover gracefully. Cloud-native applications are typically written (or rewritten) with these approaches in mind, or are modified to adhere to them as much as possible. Adapting operational processes such as PlatformOps/site reliability engineering are also important when adopting cloud-native approaches.

Cloud-native architecture adds a level of complexity to applications, and development teams require new skills, new frameworks and new technology to be successful. Without proper education, architects and developers can apply the principles poorly and deliver applications that fail to deliver the expected benefits. This can lead to developer frustration in adopting the new patterns and practices.

No. 10: Is Lift and Shift the Opposite of Cloud-Native?

Cloud-native is a popular and hyped concept because many organizations using cloud have not fully realized the benefits they expected from cloud. For example, if a traditional application is migrated to cloud using a lift-and-shift approach, the application is unlikely to leverage cloud characteristics and deliver the full benefits of cloud. If an application is rewritten to take advantage of cloud capabilities, then it is more likely to deliver the expected cloud outcomes.

So, at a very high level, yes, it is a type of opposite. By definition, rehosting (aka lift and shift) means that you are making no changes to your virtualized application and simply moving it elsewhere. So, while you may get some cloud benefits, the possibility to optimally leverage cloud characteristics is very small. Lift and shift is a migration model. Cloud-native is much more. They are apples and oranges.

Cloud-native efforts do not guarantee the benefits of leveraging cloud, as it is certainly very possible to execute poorly, but lift and shift does virtually guarantee no optimum leverage of cloud.

Lift and shift may very well be a good option for some situations. Complete cloud migrations as part of data center closures are an example of when it may make sense.

Evidence

1??Infographic: Cloud-Native and Multicloud — Buzzwords or Key Principles in Your Cloud Strategy

Note 1: Cloud Computing Definition and Characteristics

Cloud computing?is a style of computing where IT-enabled capabilities are delivered as a service. Characteristics of cloud computing are scalable and elastic, metered by use, service-based, ubiquitous by means of internet technologies, and shared.