APIs and background work
Trace requests, define contracts, and coordinate bounded background work.
Follow one save from HTTP input to durable data
A research team saves links in a shared reading list. The API accepts a URL, records it, and may attempt to obtain a display title. The URL can be safely saved even when that optional lookup fails. The later lessons introduce concurrent work, deadlines, tracing, and durable jobs around this interaction.
Start with the supplied local HTTP/SQLite API. Each project tells you which behavior is already implemented and which boundary you will add. AWS diagrams describe deployment responsibilities, while local commands remain the first runnable step.
Parts group related chapters. Each lesson has a chapter.lesson address, such as 4.07. Open a title below, or use Next to follow the reading sequence. Within a lesson, On this page lists its sections.
- 4.01
Follow an HTTP request from validation to durable state
Concepts and examples
- 4.02
Validate provider responses before returning an API result
Concepts and examples
- 4.03
Distinguish I/O overlap from parallel CPU execution
Concepts and examples
- 4.04
Fetch a bounded batch while preserving order and partial results
Concepts and examples
- 4.05
Bounded blocking queue with shutdown
Concepts and examples
- 4.06
Bound accepted work and make executor shutdown predictable
Concepts and examples
- 4.07
- 4.08
- 4.09
- 4.10
- 4.11
- 4.12
- 4.13