How shvetgharework/ticketizer works
Ticketizer is a ticket discovery and booking product backed by Spring Cloud services. A user browses events, selects a show and seats, holds them, pays, then views bookings and ticket notifications. The README documents atomic Redis holds and Kafka-backed persistence plus authentication, inventory, payment, and email capabilities. Edges below are limited to relationships shown in the README or excerpts; several service internals and integrations are represented at their documented directory level.
Main entry points: ApiGatewayApplication.java API gateway · booking Booking service · auth Authentication · inventory Event inventory
Components 20
Web experience
- Ticketizer web app
frontend/src/app/layout.tsx - Event discovery
frontend/src/app/events/page.tsx - Event details
frontend/src/app/events/[id]/page.tsx - Seat selection
frontend/src/app/events/[id]/shows/[showId]/seats/page.tsx - Checkout
frontend/src/app/checkout/[bookingId]/page.tsx - My bookings
frontend/src/app/my-bookings/page.tsx
Ingress and identity
- API gateway
src/api-gateway/src/main/java/com/example/Ticketizer/gateway/ApiGatewayApplication.java - Authentication
src/auth-service/src/main/java/com/example/Ticketizer/features/auth
Booking lifecycle
- Booking service
src/booking-service/src/main/java/com/example/Ticketizer/features/booking - Redis seat holds
- Kafka events
Discovery and shared core
- Eureka registry
src/eureka-server/src/main/java/com/example/Ticketizer/EurekaServerApplication.java - Shared security and DTOs
src/ticketflow-common/src/main/java/com/example/Ticketizer
Domain services
- Event inventory
src/inventory-service/src/main/java/com/example/Ticketizer/features/inventory - PostgreSQL
- Payment service
src/payment-service/src/main/java/com/example/Ticketizer/features/payment - Notification service
src/notification-service/src/main/java/com/example/Ticketizer/features/notification
Other components
- Ticket buyer
- Razorpay
- Mail service
Connections 31
- Ticket buyer → Ticketizer web app: uses
README.md - Ticketizer web app → Event discovery: renders
frontend/src/app/layout.tsx - Ticket buyer → Event discovery: browses
README.md - Event discovery → API gateway: fetches events
- Event discovery → Event details: opens event
frontend/src/app/events/page.tsx - Event details → Seat selection: selects seats
frontend/src/app/events/[id]/page.tsx - Ticket buyer → Seat selection: chooses seats
README.md - Seat selection → API gateway: requests reservation
- API gateway → Event inventory: routes events
README.md - API gateway → Booking service: routes bookings
README.md - API gateway → Authentication: routes auth
README.md - Booking service → Redis seat holds: locks seats
README.md - Booking service → Kafka events: publishes booking
README.md - Kafka events → Booking service: delivers events
README.md - Booking service → PostgreSQL: persists bookings
README.md - Checkout → API gateway: creates payment order
frontend/src/app/checkout/[bookingId]/page.tsx - API gateway → Payment service: routes payments
README.md - Payment service → Razorpay: integrates payment
README.md - Payment service → Booking service: settles booking
README.md - My bookings → API gateway: cancels bookings
frontend/src/app/my-bookings/page.tsx - API gateway → Notification service: routes notifications
README.md - Kafka events → Notification service: streams events
README.md - Notification service → Mail service: sends email
README.md - Authentication → PostgreSQL: stores users
README.md - Event inventory → PostgreSQL: stores inventory
README.md - Event inventory → Redis seat holds: warms seat cache
README.md - Authentication → Eureka registry: registers
README.md - Booking service → Eureka registry: registers
README.md - Event inventory → Eureka registry: registers
README.md - Authentication → Shared security and DTOs: uses shared core
- Booking service → Shared security and DTOs: uses shared core