Skip to content

Project

EventTickets - Microservices Ticketing Platform

Polyglot microservices platform for event discovery, reservations, payments, and notifications routed through a hardened API gateway.

2024
Tech Lead & Full-stack Developer
Microservices · Event Ticketing · Distributed Systems
MicroservicesEvent TicketingDistributed SystemsNode.jsSpring BootLaravelVue.jsPrismaDocker
EventTickets - Microservices Ticketing Platform

EventTickets - Microservices Ticketing Platform

A production-inspired ticketing platform built with a polyglot microservices stack. The system exposes a unified API gateway while delegating catalog, inventory, payments, and user management to focused services that can scale independently.

Architecture

  • API Gateway (Node.js + Express): Central entry point handling JWT auth, routing, and cross-service observability hooks.
  • Catalog & Inventory (Spring Boot): Dedicated services for event metadata, seat availability, and reservation windows, each with Swagger documentation.
  • Payments & Notifications (Laravel): Handles payment flows, receipts, and email/SMS notifications to keep buyers informed.
  • User Service (Node.js + Prisma): Manages identity, profiles, and tokens so session concerns stay isolated from business logic.
  • Frontend (Vue + Vite): A SPA that consumes gateway endpoints for browsing events and purchasing tickets with real-time availability feedback.
  • Docker Compose: One-command local orchestration to boot every service with consistent networking and env configuration.

Reliability & Delivery

  • Employed contract-first APIs with Swagger to align service interfaces and speed front-end integration.
  • Added health checks, logging, and request tracing to surface cross-service failures early.
  • Included JMeter load scenarios plus Maven/PHP/Node test suites to guard performance and correctness across the fleet.

Lessons Learned

  • Balanced autonomy and cohesion across heterogeneous stacks without sacrificing developer ergonomics.
  • Validated that routing, auth, and observability belong in a gateway to simplify downstream services.
  • Reinforced the value of environment-parity setups (Docker Compose) for reproducible demos and onboarding.