Cloud and Observability for Backend Developers
Cloud and observability means running backends on a major cloud such as AWS, Google Cloud or Azure and being able to see how they behave. Core cloud pieces are compute, storage, networking and managed databases, and observability combines logs, metrics and traces so you can diagnose problems quickly.
Stage: Testing, Delivery and Cloud · Part of the Backend Developer roadmap · Last reviewed 19 November 2026
What to learn in Cloud and Observability
- Deploy a service on one major cloud using managed compute
- Store files in object storage and data in a managed database
- Write structured logs with request ids
- Expose application metrics and alert on error rate
- Follow a request across services using distributed tracing
Cloud and Observability interview questions
What are the three pillars of observability?
Logs are timestamped records of events, metrics are numeric measurements over time such as request rate and latency, and traces follow a single request across services. Together they let you detect a problem, find where it happens and learn why.
Why use structured logging?
Structured logs are written as key-value data, usually JSON, instead of free text. Log systems can then filter and aggregate by fields such as user id, status or request id, which makes searching and alerting far easier than parsing text lines.
Where Cloud and Observability fits in the Backend Developer roadmap
Cloud and Observability 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