Delivery for Full Stack Developers
Delivery is how code reaches production reliably. Docker packages an app and its dependencies into an image, Docker Compose runs several services together, GitHub Actions automates testing and building on each push, and cloud hosting runs the container or serverless function users reach.
Stage: Deploy and Operate · Part of the Full Stack Developer roadmap · Last reviewed 19 November 2026
What to learn in Delivery
- Write a Dockerfile that builds a small Node.js image
- Run an app and a database together with Docker Compose
- Create a GitHub Actions workflow that tests and deploys
- Inject environment variables per environment without committing secrets
- Roll back a bad release to the previous version
Delivery interview questions
What is the difference between a Docker image and a container?
An image is a read-only template holding the filesystem, dependencies and start command. A container is a running instance of an image with its own writable layer and process. You can start many containers from one image.
Why use multi-stage Docker builds?
A multi-stage build compiles or installs dev dependencies in one stage, then copies only the built output into a lean final image. The result is smaller, faster to deploy and has fewer packages that could contain vulnerabilities.
Where Delivery fits in the Full Stack Developer roadmap
Delivery belongs to the Deploy and Operate stage (intermediate level), which takes about 6 hours. Take the app live and keep it healthy.
Other units in this stage
Back to the full Full Stack Developer roadmap