How avdyldemukajj/ticketapp works
Project type and purpose
• This is a full-stack, microservices-based ticketing/order management system.
• It consists of multiple Node.js services (auth, tickets, orders, payments, expiration), a React/Next.js client, event bus (NATS), databases, and Kubernetes deployment files.
• The system uses event-driven architecture for inter-service communication and integrates with Stripe for payment processing.
File structure
• Top-level directories
– auth, tickets, orders, payments, expiration: independent services
– client: Next.js frontend
– infra: Kubernetes manifests and ingress configuration
• Common patterns
– Each service has its own Dockerfile, tsconfig.json, src folder, tests, and package.json.
– Services publish and consume events via a shared NATS wrapper.
– Each service owns its own MongoDB collection (auth-mongo, tickets-mongo, orders-mongo, payments-mongo) and one uses Redis for delayed jobs.
• Deployment
– skaffold.yaml for development pipelines
– infra/k8s/*.yaml describes Deployments, Services, Redis, NATS, and Ingress.
Key insights from README
• The README isn’t descriptive; rely on file names and structure for system purpose.
Detail
• Flow of a typical user action end-to-end (e.g., user creates a ticket → event propagation → order creation → payment → expiration).
• Test and mock components if relevant, but keep focus on runtime architecture.