liveBook · Manning

Response boundary

As explained in Crack Any Codebase with AI

A response boundary is the point separating work completed before a server response from work performed after the response is sent.

A response boundary separates work completed before a server response from work performed after the response is sent. It defines what the user waits for and which failures may occur after a success message. section 7.5

Booking cancellation

Before the 200 OK, the booking status change and audit-row creation run synchronously; failures produce a visible error. Afterward, workflow cancellation, webhook delivery, and calendar deletion run asynchronously. Their failure can remain invisible while the user sees a green success screen. section 7.5

Use the boundary to ask:

  • Which writes block the response? section 7.5
  • Which operations fan out afterward and fail silently? section 7.5
  • Which external calls need idempotency keys when retries cross the boundary? section 7.5

How Crack Any Codebase with AI covers it

How deep it goes
Traces response timing through database writes, queued tasks, failure visibility, and retry safety.
Examples
Uses booking cancellation with an audit row, workflow cancellation, webhook scheduling, calendar deletion, and a Stripe refund.
What it assumes
Assumes familiarity with server responses, database writes, queued work, retries, and external API calls.
What you can do after
Diagnose which failures users see, which failures require background monitoring, and which retries require idempotency keys.
How it connects
Connects database writes, asynchronous processing, webhooks, retries, idempotency, and external API calls.

This explainer was generated by Manning's knowledge graph from the text of Crack Any Codebase with AI. The section links point to the parts of the book it draws on.