Overview

We’ve already explored a few Containers as a Service solutions. We saw the pros and cons of using AWS ECS with Fargate, Azure Container Instances, and Google Cloud Run. All those solutions were managed CaaS. They’re provided and managed by other vendors. When using them, we don’t need to think about the underlying infrastructure, services, plumbing, scaling, and other things not directly related to developing applications. By using managed CaaS, we’re externalizing most of the work required for the successful deployment and management of our applications.

However, managed solutions aren’t always the best path forward. There are cases when using a service is not enough. Sometimes we ...

Before We Get Started

Infrastructure as Code (IaC)

Google Kubernetes Engine (GKE) Clusters with Terraform

Manage Infrastructure using Terraform on Google Cloud Platform

AWS Elastic Kubernetes Service (EKS) Clusters with Terraform

Azure Kubernetes Service (AKS) Clusters with Terraform

Packaging, Deploying, and Managing Applications

Deploying a Web Application over Kubernetes

Using Helm as a Package Manager for Kubernetes

Hands-On: Using Helm as a Package Manager for Kubernetes on AWS

Exploring Serverless Computing

Using Managed Functions as a Service(FaaS)

Hands On: Using Managed Functions as a Service(FaaS) on AWS

Serverless as the Future

Using Managed Containers as a Service(CaaS)

Hands On: Using Managed Containers as a Service(CaaS) on AWS

Using Self-Managed Containers as a Service (CaaS)

Hands-On: Using Self-Managed Containers As A Service on AWS

Using Centralized Logging

Hands-On: Using Centralised Logging

Deploying Applications Using GitOps Principles

Hands-On: Deploying Applications Using GitOps Principles

Applying Progressive Delivery

Hands-On: Applying Progressive Delivery

Conclusion

Appendix

Introduction: Self-managed CaaS

Overview