Module 07: DevOps, Cloud, And Operations

Learn how code becomes running software and how to keep it alive.

Deployment is not copying code. Deployment is producing a runnable artifact, configuring it, exposing it safely, observing it, and being able to roll back.

source -> build -> artifact -> config -> deploy -> health -> traffic -> observe

Shipping software is like opening a shop. Writing code is designing the shop. Operations is making sure electricity works, doors open, staff show up, payment works, customers can find it, and there is a plan when something breaks.

• Missing environment variable.
• Secret not mounted.
• Database migration not applied.
• Health check points to the wrong path.
• Container listens on wrong port.
• Image tag points to old code.
• Logs are not collected.
• Rollback breaks because schema changed.

Ask an agent:

Review this deployment/runbook. Find missing config, secret handling, health
checks, rollback risk, and verification gaps. Do not assume successful deploy
means successful operation.

• What is the deployable artifact?
• What is different between local, staging, and production?
• What should /health check?
• What is the difference between logs and metrics?
• What is a safe rollback?
• Why can a deploy succeed while the product is broken?

1. Create portfolio/07-devops-cloud-operations/runbook.md.
2. Add a health endpoint.
3. Add environment-based config.
4. Run the app from a clean terminal or container.
5. Capture startup logs.
6. Hit the health endpoint.
7. Break one config value.
8. Observe the failure.
9. Roll back.
10. Document the process.

• Someone else can start and stop the app.
• Health and logs prove runtime behavior.
• A known failure is documented.
• Rollback is tested.