b2c-platform

End-to-end server-side system for a popular venue's B2C platform. A single backend serves the consumer web frontend, an admin back-office and a native mobile companion app. Beyond user accounts and entitlement handling, the system runs two-way sync of purchased entitlements and their metadata with an external ticketing provider, and ships separate domains for on-site catering pre-orders, coupon/discount logic, billing integration and the full admin workflow. The architecture is a modular monolith with ~18 bounded contexts (nwidart/laravel-modules) — deployable as one unit, but with sharp domain boundaries. Heavy work (ticket PDF/QR generation, email, push, billing callouts) runs on a Horizon-backed async pipeline, so user-facing latency never waits on background work. Payments drive a webhook-controlled order state machine (CREATED → PAYMENT_IN_PROGRESS → ORDERED), with Redis-backed distributed locks on the critical sections. The system is explicitly tuned for the on-sale moments when a sought-after act drives an explosive burst of concurrent traffic to entitlement-adjacent features.

• →Modular monolith with ~18 bounded contexts: orders, entitlements, on-site services, coupon/loyalty, billing integration, admin
• →Horizon-backed async pipeline for PDF/QR, email, push and billing callouts — payment confirmation never blocks on the heavy work
• →Webhook-driven order state machine (CREATED → PAYMENT_IN_PROGRESS → ORDERED) with atomic transitions on payment events
• →External ticketing API integration via a Saloon-based client; two-way sync of purchased entitlements and venue data
• →OpenAPI 3.0 spec split into customer and admin surfaces; Sanctum token auth, Spatie-based RBAC, OAuth2 social login