This project is a Fitness Management System consisting of three microservices. The User Service handles user authentication and authorization, providing users with tokens for interactions with the system. The Reservation Service allows clients to browse and search for available trainings, while gym managers can input data about their gym. The Notification Service sends emails for account activations, successfully scheduled training sessions and reminders before each session.
- User Types: The system supports different user types: admin, client, and gym manager.
- Registration: Clients and managers have separate registration routes.
- Login: Users log in with email and password, receiving a JWT upon successful authentication.
- Application Access Restriction: Admin can ban/unban user access to the application.
- Profile Editing: Users can edit their profile parameters, excluding membership card number and scheduled training count.
- Gym Management: Gym managers can input and update data about their gyms, including name, description, number of trainers etc...
- Listing Available Trainings: Users can view available training slots based on type, individual/group, day, and start time.
- Training Session Booking: Clients can book available training slots, triggering an email confirmation. Retry pattern implemented for network issues.
- Canceling Booked Training: Clients and gym managers can cancel booked training sessions, updating availability and notifying the User Service.
- Loyalty Program: Gym managers can define loyalty rewards, e.g., a free session after every 10th booked sessions.
- Notification Types: Admin defines notification types with associated text and parameters.
- Activation Email Sending: Handles activation email requests from the User Service.
- Password Change Email Sending.
- Successful Training Booking Notification: Sent to the client and gym manager.
- Training Cancellation Notification: Sent to the client(s) and gym manager.
- Reminder Notification 24h Before Training.
- Notification Archive: All sent notifications stored in the database, with filtering options.
- Asynchronous Notification Sending: Implemented via message broker to ensure loose coupling.
- Dynamic Service Registration: Each service registers itself with Eureka, providing a dynamic and up-to-date service registry.
- Service Discovery: Eureka allows services to locate and communicate with each other without hardcoding URLs or IP addresses.
- Load Balancing: Eureka provides load balancing capabilities, distributing incoming requests among available instances of a service.
- Routing: Routing requests to the appropriate service based on predefined rules.
- Load Balancing: Distributing incoming requests across multiple instances of a service to ensure optimal resource utilization.
The frontend of the Fitness Planner System is made using React, offering an engaging and user-friendly interface for interaction with the microservices.