Delivery for Backend Developers
Delivery is how backend code reaches production. Docker packages an app and its dependencies into a container image, CI/CD pipelines build, test and deploy on every change, and Kubernetes runs and scales containers across machines with deployments, services and health probes.
Stage: Testing, Delivery and Cloud · Part of the Backend Developer roadmap · Last reviewed 19 November 2026
What to learn in Delivery
- Write a Dockerfile and keep the image small
- Run several containers together with Docker Compose
- Build a CI pipeline that tests and builds on every push
- Describe pods, deployments and services in Kubernetes
- Roll out a new version with a rolling update and roll it back
Delivery interview questions
What is the difference between an image and a container?
An image is a read-only template with the application, runtime and filesystem layers. A container is a running instance of an image with its own process space and writable layer. You can start many containers from one image.
What does a Kubernetes Deployment manage?
A Deployment declares the desired number of identical pod replicas and the container image. Kubernetes keeps that state, replacing failed pods and performing rolling updates when you change the image, with the ability to roll back to a previous revision.
Where Delivery fits in the Backend Developer roadmap
Delivery belongs to the Testing, Delivery and Cloud stage (intermediate level), which takes about 6 hours. Ship and operate with confidence.
Other units in this stage
Back to the full Backend Developer roadmap