How chd000125/msa-studylog works
Project type and purpose
• This is a full-stack, microservice-based web application (“StudyLog”) offering study group recruitment, management, real-time chat, and a community board.
• The README confirms a five-service MSA: API Gateway, Eureka (discovery), Auth, User, Group, Board services, plus a React/Vite front end.
File structure
• Top-level folders:
• server – Eureka discovery server
• gateway – Spring Boot API gateway with custom filters (CORS, JWT)
• auth – authentication service (signup/login/email verification/JWT)
• client – user‐service (user CRUD, admin, scheduled account deletion)
• – study‐group service (scheduling, WebSocket chat, curriculum, TODOs)
• board – free board service (posts, comments, tags, Elasticsearch indexing)
• front – React/Vite SPA (Redux, React Router, API clients)
• Each service is a standalone Spring Boot app with its own build.gradle, src/main/java, application.properties, and JPA repositories.
• Board uses Elasticsearch; Redis is in the tech stack (likely caching or session store); each service uses MySQL via JPA.
README for additional insights
• Confirms ports and roles: gateway-9090, user-8921, auth-8922, group-8787, board-8123.
• Highlights Dockerized Elasticsearch, Redis, MySQL.
• Mentions Swagger for API docs, WebSocket for real-time chat.