Skip to content

Work

Introduction

A web application is a set of cooperating components. Following the flow of a request reveals where data is processed, stored, cached and passed between systems.

Why it matters

This view helps locate application bugs and support incidents across frontend, backend and infrastructure boundaries. It also makes it easier to identify where untrusted input enters and where sensitive data needs protection.

Key topics to explore

  • Browser and server responsibilities
  • APIs, databases and background jobs
  • Cookies, sessions and browser storage
  • Origins, CORS and browser isolation
  • Reverse proxies, caches and trust boundaries

Practice & notes

Possible first exercise: Draw the request and data flow for a small application. Annotate its trust boundaries and use browser developer tools to compare the diagram with actual requests.

Future notes will record the setup, observations, open questions and principles learned. This exercise is a starting idea, not a completed assessment.