Skip to content
Module
Module 6 of 6Lesson 2 of 3~15 min

Drawing a request's journey through your product

The final workshop has you map the full path of a request in your own product, from the user down to the data. You produce an annotated diagram that brings the whole course together and that a developer validates, a shared basis for discussing incidents, performance and technical choices with your team.

Take this lesson: your first course is freeSee the full syllabus

Lesson objective

By the end of this lesson, you will be able to produce the annotated diagram of a request's journey through your own product (eight zones, five annotations per zone) and have it validated by a developer.

Topics covered

  • architecture diagram
  • web product workshop
  • technical mapping
  • web architecture
  • deliverable

In the glossary

Full glossary

Where it fits

Diagnose and map your product

How do I use all of this to qualify an incident and describe my own product?

Lessons in this module

  1. Qualifying an incident layer by layer
  2. Drawing a request's journey through your product (this lesson)
  3. Exit kit and application plan

What you will learn in this module

This lesson is part of the course Explain how a web product works, from browser to server

  • Explain how responsibilities are split between browser, frontend, backend, API, database and third-party services, and place where a business rule must run.
  • Explain the role of a CDN and of caches (browser, CDN, server) and anticipate their effects on speed, data freshness and releases.
  • Tell apart local, preview, staging and production environments, and say what changes from one to another (configuration, data, secrets).
  • Place a symptom (slowness, blank page, error, stale data) in the right layer and ask the technical team precise questions.
  • Produce the annotated diagram of a request's journey through your own product and have it validated by a developer.

Related courses