How wongi-kim/playus-backend works
Project type and purpose
• This is a monolithic, feature-driven, full-stack application:
• Backend: Java + Spring Boot REST API (this file tree)
• Frontend: Next.js + TypeScript + Tailwind CSS (deployed on Vercel)
• Database: MongoDB
• External services: Google Sheets API, JWT auth, GCP + Docker on Ubuntu
• Purpose: expose REST endpoints for admin management, user login/signup, experience tracking, quests, boards, notifications, and fetch Google Sheet data.
File structure
• src/main/java/org/example/playus/domain: each subpackage is a bounded context (admin, board, employee, quest, login/logout, security, sheet, signup, user, etc.).
• In each context:
• Controller classes accept HTTP requests.
• Service classes hold business logic.
• Repository interfaces access MongoDB (via Spring Data).
• DTO packages define request/response payloads.
• model or entity classes represent domain objects.
• global: common utilities (error handling, timestamped base class, configs for Mongo & Swagger).
• SecurityConfig + JWT filters chain incoming requests.
• Dockerfile + Gradle build scripts for containerized deployment.
README for additional insights
• ERD (data model relationships) is present.
• Environmental variables for MongoDB, MySQL (unused?), JWT, Google Sheet ID.
• Swagger for API docs.