How naughtycomputer/naughty-be-spring works
Project type and purpose
• This is a Spring Boot–based monolithic backend service for a “2025 졸업 프로젝트” (graduation project) named “Naughty-BE-Spring.”
• It exposes RESTful endpoints for user, post, comment, profile, like/scrap functionality and handles authentication (including OAuth2 via Kakao) and JWT-based security.
File structure
• Top level: standard Gradle/Spring Boot layout.
• build.gradle, gradlew scripts, settings.gradle, gradle wrapper -> build and dependency management
• src/main/java/naughty/tuzamate -> application code
• src/test -> unit/integration tests
• Packages under src/main/java:
• auth – controllers, services, JWT filters/providers, OAuth2 integration (Kakao)
• domain – modular subpackages for comment, post, postLike, postScrap, profile, user; each with controller, dto, entity, repository, converter, service/command, service/query
• global – cross-cutting concerns: BaseTimeEntity, API payload wrappers, config (SecurityConfig, SwaggerConfig, WebConfig), global errors and exception handlers, success codes
• No separate “frontend” or microservices—this is a single monolith with layered architecture (Controller → Service → Repository → Database).
README for additional insights
• Only confirms backend Spring part of graduation project.
Elements
– Green for external systems (Kakao, DB)
– Orange for cross-cutting components (SecurityConfig, GlobalExceptionHandler)
• Annotations for major classes/interfaces (e.g., JwtFilter, SecurityConfig, CustomResponse)