SOFTWARE ENGINEERING
Bun Service-Oriented Systems: From Modular Monolith to Production
Build one order-to-delivery system, extract services only when evidence earns the boundary
CURRICULUM
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 SystemBuild: ParcelFlow accepts one tenant-scoped order and returns a delivery promise from one Bun process.Published 09 Aug 202612 sections
- 02Choose Bun and an HTTP FrameworkDecision: keep Bun, adopt Hono as ParcelFlow’s HTTP layer, and preserve a framework-neutral application core.Published 09 Aug 202614 sections
- 03DRY, SRP, IoC, DI, and the Composition RootRefactor: make ParcelFlow’s policy independent from Hono, Bun.SQL, and the fake payment adapter without adding a DI container.Published 09 Aug 202614 sections
- 04Durable State, Transactions, and IdempotencyPersist: move ParcelFlow to PostgreSQL through Bun.SQL and prove retries, concurrency, rollback, and restart behaviour.Published 09 Aug 202614 sections
- 05Earn the First Service BoundaryPublished 09 Aug 202611 sections
- 06Synchronous Contracts and API EvolutionPublished 09 Aug 202612 sections
- 07Events, Outbox, and Idempotent ConsumersPublished 09 Aug 202612 sections
- 08Resilience Under Partial FailurePublished 09 Aug 202612 sections
- 09Identity, Tenant Isolation, and Service AuthorityBind every human and workload request to one tenant and one explicit permission before it reaches ParcelFlow data.Published 09 Aug 202615 sections
- 10Observability as an Operating LoopTurn ParcelFlow behavior into correlated evidence, an accountable decision, and a measured recovery.Published 09 Aug 202616 sections
- 11Containerize and Deploy with PulumiTurn tested ParcelFlow services into immutable Bun containers and a reviewable AWS release with canary rollback.Published 09 Aug 202614 sections
- 12Full-System E2E Proof and RetirementProve ParcelFlow as one customer system: release, attack, fail, recover, roll back, export, revoke, disable, and retire.Published 09 Aug 202618 sections