DevOps
Deploying multi-audience NestJS with Docker & K8s, horizontally
0views0comments
A guide to splitting API_AUDIENCE=web/cms into two independent services, scaling safely behind a load balancer.
Overview
This post shares real experience splitting a single NestJS codebase into two independent services for production.
Why split the service
Separating web/cms lets each scale to its actual load — public traffic is usually far higher than admin traffic.
Deploying on K8s
Each service gets its own Deployment and HorizontalPodAutoscaler, both pointing at one database through a connection pool.
Tags
devopskubernetes
Blog
← BackCategory
DevOps · Blog