Masstransit

Breaking "background work" into three separate accounts — trigger semantics, process ownership, and module boundaries — to explain why Quartz and MassTransit are not an either/or but a division of labor, and how boundary erosion drags a modular monolith toward a big ball of mud.

Unpacking the core tradeoffs of Web-Queue-Worker: why the Web tier must "publish, never wait," why the Outbox is a precondition for correctness rather than an optimization, and why scheduled jobs can't use a bare Timer — each argued from mechanism, "why this and not the other."