The distributed cloud era has arrived

The term “cloud” has been evolving ever since the term was first used in the early 1990s. One could argue that Cloud 1.0 was really nothing more than a euphemism for hosted services. Hosted services gave companies the ability to run critical apps off their premises in a highly secure, predictable environment. This value proposition continued with the future rise of services like AWS and Microsoft Azure, where businesses would “lift and shift” legacy apps and drop them into a cloud. 

Cloud 2.0 gave rise to web-optimized apps. In Cloud 2.0 the apps were truly built for the cloud and spawned companies that made the cloud their primary compute platform. However, this cloud strategy revolved around a single cloud provider and traditional monolithic app architectures. Even companies that used multiple clouds built app A on one cloud, app B on another, etc. In this case, multicloud was actually multiple clouds being used as discrete, independent infrastructure entities.

We have now entered the Cloud 3.0 era, which can be thought of as multicloud on steroids. The rise of microservices and containers has allowed app developers to build apps by accessing services from multiple cloud providers. Most modern, cloud-native apps are being built this way. Edge computing is on the horizon, which will create more locations for app developers to extend access to data and app services. This is the concept of the distributed cloud, where the cloud is no longer a single location, but a set of distributed resources.

Distributed cloud changes app delivery

The evolution of the cloud – and cloud-native apps as a result – has had a profound impact on the networking and security services required to connect app components to other app components and to connect apps to users. With Cloud 1.0, IT professionals used physical appliances such as load balancers or application delivery controllers and web app firewalls. These were installed in the same data centers that hosted the app infrastructure. With Cloud 2.0, these functions were virtualized and installed as a cloud resource. The network and app architectures were largely the same, but the infrastructure shifted to cloud-resident virtual appliances.

>>With distributed cloud (Cloud 3.0), app components (e.g. microservices) are modular and reside in containers across multiple clusters. This creates significant deployment and operational challenges for DevOps teams and IT professionals. The dynamic and distributed nature of containerized workloads and microservices can’t be supported by the physical or even virtual infrastructure traditionally used for monolithic apps, which rely on centralized control and visibility, as opposed to the dynamic operational model needed for highly distributed clusters and workloads. A containerized workload can be spun up and deprecated in a matter of minutes, even seconds. This means the supporting network and security infrastructure like load balancers, web app firewalls, and API gateways need to be spun up and down just as quickly. 

Meeting the operational challenges of distributed cloud

This week cloud-native app infrastructure provider, Volterra, announced the latest release of its VoltMesh service, which addresses many of the operational challenges associated with deploying and operating modern apps in a distributed cloud model. The company offers a wide range of what would typically be known as “application delivery services” from the cloud, made available as a single SaaS-based offering.

Copyright © 2020 IDG Communications, Inc.

Source link