Choose a backend project: tracing, deadlines, fetching, contracts or jobsCHAPTER 04
PART B / APIs and background work
Your guided curriculum
CHAPTER 04GUIDED READING

Choose a backend project: tracing, deadlines, fetching, contracts or jobs

Read the section first. Work in this order; each project isolates one skill. Each link opens one complete build brief with a concrete contract, a baseline, two changed requirements, and the original staged AI prompts.

These are five project briefs, not five supplied applications. All prompts are constructed practice.

1. Trace requests through a bookmark API

Trace requests through a bookmark API — Trace one request while preserving trust and redaction boundaries.

2. Enforce a single deadline across API dependencies

Enforce a single deadline across API dependencies — Spend a deadline once and distinguish attempts from retries.

Build an SSRF-resistant link preview fetcher — Bind URL validation to the actual connection and every redirect.

4. Evolve tag responses without breaking old clients

Evolve tag responses without breaking old clients — Evolve a wire contract while proving old-client compatibility.

5. Move title lookup into restartable background jobs

Move title lookup into restartable background jobs — Protect result commits from stale lease owners and repeated execution.