Bun Service-Oriented Systems: From Modular Monolith to Production
Build one order-to-delivery system, extract services only when evidence earns the boundary
Build ParcelFlow as a tenant-aware order-to-delivery system on Bun: begin with a modular monolith, make state and contracts durable, then extract, observe, deploy, and retire services only when measured coupling and failure evidence justify each boundary.
- 01One Request, One Complete System
- 02Choose Bun and an HTTP Framework
- 03DRY, SRP, IoC, DI, and the Composition Root
- 04Durable State, Transactions, and Idempotency
- 05Earn the First Service Boundary
- 06Synchronous Contracts and API Evolution
- 07Events, Outbox, and Idempotent Consumers
- 08Resilience Under Partial Failure
- 09Identity, Tenant Isolation, and Service Authority
- 10Observability as an Operating Loop
- 11Containerize and Deploy with Pulumi
- 12Full-System E2E Proof and Retirement