From IaaS to PaaS: How Cloud‑Native Tech Supercharges Delivery

From IaaS to PaaS: Evolution of Application Architecture

Alibaba has moved from the IaaS cloud era to a PaaS‑focused cloud‑native stage. During Double 11 the e‑commerce core systems were fully migrated to IaaS, and now the company is leveraging PaaS services such as middleware, storage, cache and application‑hosting platforms.

Key Differences Between IaaS and PaaS

In the IaaS stage developers mainly care about virtual machines or containers, which have little impact on application architecture. In the PaaS stage the use of cloud products (cloud Redis, cloud RDS, cloud OSS, cloud RabbitMQ, etc.) introduces strong architectural intrusion that must be considered.

What Is Cloud‑Native Technology?

Cloud‑native can be classified along four vertical dimensions—application architecture, lifecycle management, traffic management, and infrastructure/dependencies—and several horizontal dimensions such as micro‑services, 12‑Factor Apps, containers, BaaS, GitOps/IaC, and Service Mesh.

Improving Delivery Speed with Cloud‑Native

Business teams care most about delivery velocity. Cloud‑native helps by (1) standardizing the protocol between platform/services and applications, (2) decoupling business‑agnostic capabilities to the platform, and (3) evolving the application architecture to adopt these capabilities.

Transition from IaaS to Cloud‑Native

In the IaaS era developers had to build and configure middleware themselves, consuming a lot of time. In the PaaS/cloud‑native era the goal is to consume platform‑provided capabilities and focus on core business logic.

Practical Examples

Service Mesh moves service discovery and traffic routing from the application SDK to a sidecar, allowing the platform to manage them.

Lightweight containers shift log collection from business processes to a sidecar agent, enabling resource isolation and independent upgrades.

Probes expose health information via HTTP or shell scripts so the platform can perform automatic scaling, migration, and self‑healing.

Contract = API + Configuration

Modern cloud contracts combine APIs (e.g., Docker/OCI for software delivery, gRPC/DUBBO for RPC) with declarative configuration languages (Terraform, Pulumi, GitOps) that describe infrastructure and deployment policies.

Shift in R&D Focus

Developers increasingly rely on code‑defined contracts to describe infrastructure, operations, and runtime requirements, enabling applications to run consistently across private, public, or Alibaba Cloud environments.

Conclusion

As cloud resources become richer, PaaS capabilities will continue to grow, but current usage remains inefficient and non‑standard. Cloud‑native redefines the contract between applications and the cloud, paving the way for higher‑level programming models and tools.