How sungwookkk/ftt_backend works
Project type and purpose
• This is a monolithic, full-stack (serving a SPA frontend from Spring Boot) backend service built with Java Spring Boot.
• It provides REST APIs for user, task, team, chat, community post, badge, statistics, file uploads; real-time presence via WebSocket; batch jobs for SMS reminders; integrations with Kafka, Twilio, OpenAI, and social login (Google, Naver).
File structure
• Top-level: Gradle build, Spring Boot entry point (FttBackendApplication.java).
• config: security (JWT filters, WebConfig), batch (schedulers, controllers), kafka, openai, twilio, data loader.
• controller → REST endpoints; model → JPA entities; repository → Spring Data; service → business logic; social → OAuth controllers; socket → WebSocket setup; statistics → analytics endpoints and DTOs.
• resources/static + SpaForwardController serve the frontend.
README for additional insights
• Notes on CI/CD, DataLoader, REST API design, batch job setup (Twilio, Kafka).
Be detailed but focused
• Break the backend monolith into at least these sub-components: API Layer, Service Layer, Data Layer, Batch Module, WebSocket Module, Security Module, Integration Modules.
• External dependencies and asynchronous flows (Kafka).
• Avoid over-splitting trivial classes; aggregate by module.