The 2 a.m. operator test moved every slow call out of this billing app's request path

Start with what happens on a send. The handler writes the business row and a row in `outbox_messages` in one database transaction ^[17]. The commit is the moment the user's action is durable. Delivery happens afterwards, on a worker loop that picks up unsent messages, retries, and either marks them Sent or records the error ^[17]. The chapter names the bug this design deletes: "user clicked submit, page said OK, email never arrived" ^[18]. Send inside the request instead and you choose between two bad outcomes: fail the request, so the user thinks the invoice was not saved, or swallow the error, so the email vanishes ^[18].

The cost is a container that has to be up whenever anyone expects mail, and a table that now holds the failures. Every email in the product goes through it, including feedback notifications with `Reply-To` set to the reporter ^[19]. The rule deciding what belongs there is a latency number: anything slower than about 100ms, or anything that must retry, leaves the request path ^[10]. Same codebase, different entrypoint, its own container, so a hung email send cannot block an invoice save ^[11].

The chapter describes the result as five moving parts and a proxy ^[5]. Instances count differently. foxyinvoice.com and invoices.seolith.com serve the same Angular bundle with branding resolved at runtime ^[7], and each deployment gets its own API container, worker and Postgres ^[2]. That is six processes behind one Caddy ^[22].

"Architecture includes your dependency graph," the author wrote ^[16]. The evidence is the single production failure the chapter reports. The in-process dispatcher was MediatR 12, the platform packages needed 14, and the version diamond crash-looped production until a dependency bumped it into a wall ^[15]. That outage came out of the package graph. Controllers now parse a request and hand a command or query object to Mediator, a single-file MIT library, with every business operation written as a record plus one handler class ^[12][13]. The migration took an afternoon ^[16].

For this shape to transfer, three things have to hold: one operator, no on-call rotation, and a product where downtime means someone cannot get paid ^[23]. Those conditions justify the outbox and the second container. The frontend choice came from somewhere else. Angular won on batteries-included opinions and because it is what the one operator already knew, and the chapter states the principle directly: "Framework choice is a burn-rate decision, not an identity" ^[8]. The same chapter asserts the stack can carry a million users, "further than you'd think", and includes no load figures ^[24].