Schedule

The workshop runs from 9:00 AM to 5:00 PM with a morning break, lunch, and an afternoon break. Teaching time is five hours and fifty minutes.

Time	Block	Length
9:00 – 9:20	Welcome, environment check, and the Roastery tour	20 min
9:20 – 10:30	Module 1 — Fundamentals and the endpoint pipeline	70 min
10:30 – 10:45	Morning break	15 min
10:45 – 12:00	Module 2 — Data, validation, and the shape of a good API	75 min
12:00 – 1:00	Lunch	60 min
1:00 – 2:15	Module 3 — Identity, tokens, and authorization	75 min
2:15 – 2:30	Afternoon break	15 min
2:30 – 3:45	Module 4 — Performance, resilience, and testing	75 min
3:45 – 4:40	Module 5 — Aspire, containers, and shipping	55 min
4:40 – 5:00	Wrap-up, retrospective, and where to go next	20 min

Inside a module

Each module follows the same rhythm so you always know what is coming:

• Concepts (about 25 minutes). The instructor builds the feature live, explaining the decisions as they go. Follow along or just watch; the lab repeats everything at your own pace.
• Lab (about 45 minutes). You implement the feature in your own copy of Roastery, with a numbered set of steps, a stretch goal if you finish early, and a list of the mistakes people most often make.
• Checkpoint. Every lab ends at a git tag. If you are behind, run git checkout checkpoint-N and carry on with the group.

Lunch table topic

An optional conversation for anyone who wants it: Minimal APIs versus controllers versus FastEndpoints and Carter: when would you not use Minimal APIs?

If the day runs long

The schedule carries about fifteen minutes of slack, most of it in Module 5, which is designed to compress gracefully. If we need to cut, the cuts are made in this order: the versioning step in Lab 5, then the container build in Lab 5 (it becomes a demo), then the HybridCache step in Lab 4, then the security-header middleware in Lab 3. The integration tests in Lab 4 and the authorization policies in Lab 3 are never cut.