8.4: Cloud-Native Deployment- Platforms and Container Orchestration

Introduction to Cloud Computing · LibreTexts

0%

Contents

    Text

    Size
    100%
    Theme
    Typeface
    Line length
    Spacing

    Read aloud

    How

    Speed: 1×
    Light up
    Highlight

    Symbols: Mulberry Symbols, © 2018–2026 Steve Lee, CC BY-SA 4.0 (licence, the set), the site's own copies.

    From LibreTexts, under CC BY 4.0, as the source states it; its equations are written in TeX, which the PDF shows typeset. This page at LibreTexts.

    8.4: Cloud-Native Deployment- Platforms and Container Orchestration

    Designing a cloud-native application is only half the story – you also need to deploy and run it effectively. A typical cloud-native app runs on a cluster of machines (which could be virtual machines or even bare-metal, but often cloud VMs or a managed service) rather than a single server. This cluster provides resources for many containerized microservices to run concurrently, and tools are needed to schedule, coordinate, and manage those containers. This is where container orchestration comes in, with Kubernetes as the dominant technology. Cloud providers have each built services around running containers and microservices at scale, such as AWS’s Elastic Container Service (ECS) and Elastic Kubernetes Service (EKS), or Google Cloud’s Kubernetes Engine (GKE).

    In this section, we’ll introduce the main options for deploying cloud-native applications in clustered environments, focusing on Kubernetes and managed cloud services. We will also provide a comparative look at AWS vs. GCP container tooling (see Table 8-2).


    This page titled 8.4: Cloud-Native Deployment- Platforms and Container Orchestration was last modified on Tue, 22 Sep 2026 21:13:28 GMT and is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by Felix Amoruwa.