FitNest Fitness Platform

A scalable microservices-based fitness tracking and AI recommendation platform built with Java (Spring Boot), React, RabbitMQ, Docker, and more.

---

Table of Contents

• System Overview
• Architecture Diagram
• Microservices & Responsibilities
• API Endpoints
• Data Flow & Working
• Setup & Running Locally
• Docker & Deployment
• Environment Variables
• Development & Testing
• Troubleshooting
• Contributing
• License

---

System Overview

This platform allows users to:

• Track fitness activities (CRUD)
• Get AI-powered recommendations for activities
• Manage authentication and user profiles
• View dashboards and insights

Tech Stack:

• Java (Spring Boot) for backend microservices
• React for frontend
• RabbitMQ for messaging
• Eureka for service discovery
• Spring Cloud Config for centralized configuration
• Docker for containerization

---

Architecture Diagram

---

Sequence Diagram

---

Microservices & Responsibilities

• activity_service/: Manages user activities (CRUD operations, metrics, etc.).
• ai_service/: Provides AI-powered recommendations and analysis for activities.
• auth_service/: Handles user authentication, registration, and JWT token management.
• user_service/: Manages user profiles and related data.
• gateway/: API Gateway for routing, load balancing, and authentication filtering.
• common-security/: Shared security logic (JWT, filters).
• config_server/: Centralized configuration management for all services.
• eureka/: Service discovery using Netflix Eureka.
• frontend/: React-based user interface.
• docker-compose.yml: Container orchestration for local development.

---

API Endpoints

Activity Service

• POST /api/v1/activities/create - Create activity
• GET /api/v1/activities - List activities (paginated)
• GET /api/v1/activities/{id} - Get activity by ID
• PUT /api/v1/activities/update/{id} - Update activity
• DELETE /api/v1/activities/delete/{id} - Delete activity
• GET /api/v1/activities/my-activities - List user’s activities
• GET /api/v1/activities/recent - Recent activities
• GET /api/v1/activities/top-calories - Top calorie activities

AI Service

• GET /api/v1/recommendations - List recommendations (paginated)
• GET /api/v1/recommendations/{id} - Get recommendation by ID
• POST /api/v1/recommendations - Create recommendation
• PUT /api/v1/recommendations/{id} - Update recommendation
• DELETE /api/v1/recommendations/{id} - Delete recommendation

Auth Service

• POST /api/v1/auth/register - Register user
• POST /api/v1/auth/login - Login

User Service

• GET /api/v1/users/{id} - Get user profile
• PUT /api/v1/users/{id} - Update user profile

Gateway

• Routes all requests to appropriate microservices

---

Data Flow & Working

1. User creates/updates/deletes an activity via frontend.
2. Activity Service processes the request and sends an event to RabbitMQ.
3. AI Service listens to RabbitMQ, processes the activity, and generates recommendations using AI (Gemini API or similar).
4. Recommendations are stored and can be fetched by the frontend.
5. All services register with Eureka for service discovery.
6. Gateway routes requests and applies security via common-security.

---

Setup & Running Locally

Prerequisites

• Java 17+
• Node.js 18+
• Docker & Docker Compose

1. Clone the repository

git clone <repo-url>
cd java_proect

2. Start RabbitMQ, Eureka, Config Server, and all services

Using Docker Compose

docker-compose up --build

Or manually

./start-all.sh

3. Start the frontend

cd frontend
npm install
npm run dev

4. Access the app

• Frontend: http://localhost:3000
• Eureka dashboard: http://localhost:8761
• RabbitMQ dashboard: http://localhost:15672 (default user/pass: guest/guest)

---

Docker & Deployment

• All services are containerized.
• Use docker-compose.yml to orchestrate services.
• For production, configure environment variables/secrets in Docker or your cloud provider.

---

Environment Variables

Each service uses its own application.yml for configuration. Key variables:

• rabbitmq.exchange.name
• rabbitmq.queue.name
• rabbitmq.routing.key
• rabbitmq.update.queue.name
• rabbitmq.update.routing.key
• rabbitmq.delete.queue.name
• rabbitmq.delete.routing.key
• spring.datasource.* (for DB config)
• jwt.secret (for auth) Set these in your application.yml or as environment variables.

---

Development & Testing

• Backend: Use ./mvnw spring-boot:run in each service folder.
• Frontend: Use npm run dev.
• Testing: Use JUnit for backend, React Testing Library/Jest for frontend.
• Linting: Use ESLint for frontend, Checkstyle for backend.

---

Troubleshooting

• RabbitMQ exchange type error: Ensure exchange type matches in config and RabbitMQ.
• Missing environment variables: Check application.yml in each service.
• Service not registering: Check Eureka and service logs.
• Frontend API errors: Check gateway and backend logs.

---

Contributing

1. Fork the repo
2. Create a feature branch
3. Commit your changes
4. Open a pull request

---