Loading project…
C#Professionalabout 9 hours19 lessons
Recommended first: Footlight
Run the booking platform for a chain of climbing gyms by writing its HTTP stack yourself, in the .NET style. You start with a recorded day of raw requests and finish with a routed, validated, authenticated, rate-limited, cached, observable API with a transactional outbox and a request-day report. The operations console beside your editor shows requests flowing through your middleware lanes, your route table, your container, your health lights and your logs.
Each lesson adds one working part to your build.
Chapter 1
Model an HTTP exchange, route it by template, and wrap it in a middleware pipeline built from delegates.
Chapter 2
Bind requests to code, reject bad input with problem details, and keep bookings in a unit of work with row versions.
Chapter 3
Sign tokens, authorize the caller and the resource, throttle bursts, make retries safe and let clients cache.
Chapter 4
See what the API is doing, report its health, survive a flaky upstream and deliver side effects reliably.
Structured logs, correlation ids and metrics
55 min280 XPAdds Log stream, Latency histogram
Health checks: live, ready, startup
40 min220 XPAdds Health board
Timeouts, retries with jitter and a circuit breaker
55 min290 XPAdds Upstream calls
The outbox and a worker that shuts down gracefully
60 min310 XPAdds Outbox
Chapter 5
Roll out features gradually, test through the front door, evolve the API and read a whole day back.