Track 01

System design

Map who does what, where data moves, and what each part promises.

Start here

Map the system before choosing components

  1. Identify the actors. Name who requests the work, who does it, and who uses the result.

  2. Draw the boundaries. Follow one request. Mark where data and permissions change hands.

  3. Define a useful result. Decide what to guarantee and how to show an incomplete or failed result.

Read API design principles

Worked examples

References

Explore all five tracks