soluxboro/31th_1_solux_boro_back

Purpose and runtime

BORO is a Spring Boot backend for a peer rental/community service: members publish rental posts and empty spots, request and manage rentals, chat, review, maintain assets/points, and authenticate socially. The application starts at src/main/java/com/boro/BoroApplication.java; Gradle build/runtime definition is build.gradle.

API and domain layering

Each business area follows controller → command/query service → repository/entity, with DTO converters separating HTTP contracts from persistence models. Core HTTP entry points include:

• Posts and availability: src/main/java/com/boro/domain/post/controller/PostController.java, src/main/java/com/boro/domain/emptyspot/controller/EmptySpotController.java

• Rentals: src/main/java/com/boro/domain/rentalrequest/controller/RentalRequestController.java, src/main/java/com/boro/domain/rentalrequest/controller/RentalController.java

• Member profiles/assets: src/main/java/com/boro/domain/member/controller/MemberController.java, src/main/java/com/boro/domain/member/controller/AssetController.java

Identity and request security

Authentication supports local token flows plus Google OAuth user loading. JWT security is a cross-cutting boundary: requests pass through Spring Security and JwtFilter, while token storage/query operations are backed by Redis. Relevant paths: src/main/java/com/boro/global/security/SecurityConfig.java, src/main/java/com/boro/domain/auth/service/command/AuthCommandService.java, src/main/java/com/boro/domain/auth/factory/GoogleUserLoader.java.

Rental marketplace lifecycle

Posts model rentable items, images, categories, prices, status, likes, and linked empty spots. Rental requests own request status/decisions and reviews; command/query services indicate separate mutation and read paths. The main business flow is member-authenticated post discovery/creation → rental request → rental decision/status transition → review and associated member history/points. Paths: src/main/java/com/boro/domain/post/entity/Post.java, src/main/java/com/boro/domain/rentalrequest/entity/RentalRequest.java, src/main/java/com/boro/domain/rentalrequest/entity/Review.java.

Realtime chat and eventing

Chat supports REST access and WebSocket/STOMP messaging, persisted as rooms, memberships, messages, and message images. Redis Pub/Sub provides a distribution boundary for chat events, enabling delivery beyond a single application process. Paths: src/main/java/com/boro/domain/chat/controller/ChatWebSocketController.java, src/main/java/com/boro/domain/chat/service/command/RedisPublisher.java, src/main/java/com/boro/global/config/WebSocketConfig.java.

Persistence, media, and shared behavior

Relational persistence is represented by JPA-style entities/repositories across domains, sharing audit/base behavior through BaseEntity. Redis is used for token/session-like storage and chat messaging. File upload is decoupled through AWS S3 presigned URL generation, so clients can transfer media directly to S3. Paths: src/main/java/com/boro/global/common/BaseEntity.java, src/main/java/com/boro/global/s3/service/S3PresignService.java, src/main/java/com/boro/global/config/RedisConfig.java.

Deployment and operations

The service is containerized with Dockerfile and composed via docker-compose.yml; Nginx is configured as an edge proxy in deploy/nginx/boro.conf. Prometheus scrape configuration is present at monitoring/prometheus.yml. CI/CD workflows are defined in .github/workflows/ci.yml and .github/workflows/cd.yml.