Multi-tenant booking platform backend

The backbone of my Understory work: backend services for a multi-tenant booking platform running on AWS, split into named services across bookings, events, experiences, locations, payments, profiles, and receipts, each independently deployed and wired together through serverless infrastructure. Roughly a quarter of my time here was front-end work; the other three quarters was backend, data, and AI, and this project is where most of that backend three-quarters lived.

Correctness in the booking flow was the standard everything else got measured against, since a wrong booking or a silently failed cancellation costs the company a real customer, not just an engineering apology.

I worked in Node.js and TypeScript across NestJS and Next.js services, used C4 and PlantUML diagrams to keep the service boundaries legible as the ecosystem grew past what any one person could hold in their head, and the correctness discipline this demanded shaped how I approached every other Understory project that touched the same data.