Kubernetes
Container orchestration at scale: pods, deployments, services, ingress — likely future-facing, not current-state.
Why we need this / what value this brings
Automates scheduling, scaling, and self-healing across a fleet of containers — valuable once managing instances by hand becomes the bottleneck.
When to use this
Once there are enough services/instances that manual container management is genuinely painful — not before.
How to use or implement this
Consider a managed offering (EKS, GKE) over self-hosting the control plane, and only adopt once a simpler option (ECS/Fargate) has been ruled out.
Research questions
- Realistically: does Localz need K8s before it needs more than one region/multiple backend instances?
Empty folder — drop notes, links, and findings here as you research.