Self-managed vs. Managed CaaS

Learn when to use self-managed and managed CaaS.

We'll cover the following

Overview
Kubernetes cluster overhead
Ease of deployment
Conclusion

We’ve explored both managed and self-managed Containers as a Service (CaaS). Examples of the former were Azure Container Instances, AWS ECS with Fargate, and Google Cloud Run. The results were mixed, ranging from useless to amazing. Now, on the other hand, we’ve explored Knative as a potential candidate for running self-managed serverless CaaS workloads. Potentially the most important question left unanswered is whether we should use managed or self-managed CaaS?

For the sake of comparison, let’s assume that all managed CaaS are equally as good, even though that’s not the case, and generalize the discussion into a simple managed vs. self-managed choice.

Get hands-on with 1200+ tech skills courses.

Before We Get Started

Infrastructure as Code (IaC)

Google Kubernetes Engine (GKE) Clusters with Terraform

AWS Elastic Kubernetes Service (EKS) Clusters with Terraform

Azure Kubernetes Service (AKS) Clusters with Terraform

Packaging, Deploying, and Managing Applications

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

Self-managed vs. Managed CaaS