How aryansrivastava1709/event-management-system works
Project Type and Purpose
• This is a full-stack, microservices-based Event Management System.
• Frontend: Angular SPA.
• Backend: A set of Spring Boot microservices managing registration, login, events, bookings, payments, notifications, images, user lookups, plus an API Gateway and Eureka Service Registry.
• Each microservice exposes REST endpoints, uses JWT for security, communicates via Feign, and persists data to its own MySQL schema.
File Structure Analysis
• Top-level “backend” directory contains:
• eureka‐server – service registry
• gateway-api – Spring Cloud Gateway for routing + JWT filtering
• registration-service, login-service, user-service, event-service, booking-service, payment-service, notification-service, image-service – each a standalone Spring Boot app (controller, service, repository, config, dto, exception, tests)
• “frontend” directory contains an Angular project (app module, components, services, guards).
• Build and config files: pom.xml, application.properties, .mvn, Maven wrappers in each service; angular.json, package.json for frontend.
Key Architecture Insights from README
• A classical microservices architecture with:
• Service Registry (Eureka)
• API Gateway for routing and cross-cutting concerns (JWT, CORS, logging)
• Dedicated microservices for domain functions (users, auth, events, bookings, payments, notifications, images)
• Each service registers with Eureka, discovers peers via Feign, and secures endpoints using JWT.
• Frontend (Angular SPA)
• API Gateway
• Eureka Service Registry
• Microservices:
• Registration Service
• Login Service
• User Service
• Event Service
• Booking Service
• Payment Service
• Notification Service
• Image Service
• Datastores (MySQL) – one per service
• External Services: Mail SMTP (Notification), Cloudinary (Image), Razorpay (Payment)
• User’s browser → HTTP(S) → API Gateway
• Gateway → Eureka lookup → Route to appropriate microservice
• Booking Service ↔ Payment Service (via Feign)
• Booking Service ↔ Event Service, User Service (via Feign)
• Payment Service ↔ Razorpay API
• Notification Service → Mail server
• Image Service → Cloudinary API
c. Architectural Patterns & Principles:
• Microservices with single responsibility
• Service Discovery (Eureka) + Client-side load balancing
• API Gateway Pattern for authentication, routing, logging, CORS
• JWT-based stateless security
• Inter-service comm via Feign (REST)
d. Key Technologies & Frameworks:
• Spring Boot, Spring Cloud Netflix (Eureka, Feign), Spring Security (JWT)
• MySQL (persistent store)
• Angular, TypeScript (frontend)
• External APIs: Razorpay, Cloudinary, SMTP Mail