How team-tlog/tlog-was works
Project type and purpose
• Tlog-was is a Java Spring Boot backend monolith employing Domain-Driven Design (DDD). It exposes REST and WebSocket endpoints, integrates with multiple persistence stores, message broker, cache, and external services (SSO, FCM). There is no separate frontend in this repo.
File structure
• Top-level “tlog-was” directory is a single Spring Boot application.
• Inside “src/main/java/com/se/Tlog” you see:
• config (async, CORS, datasource, RabbitMQ, Redis, WebSocket, security, OpenAPI)
• domain (split into sub-packages: Admin, User, Travel, Course, Review, Notification, Search, Social, Team, Tbti, Reward, Wishlist)
• global (exception handling, response wrappers, security filters, JWT/Redis utilities)
• Persistence layers: JPA (relational DB) and Mongo (for travel, course, review, search, post, wishlist).
• Messaging: RabbitMQ for chat.
• Caching: Redis.
• External APIs: Google/Kakao SSO, FCM.
README
• Focuses on branch/commit conventions.
Detail and essential elements
• Persistence choices and external integrations.
• Inter-module service calls only where cross-module interactions exist (e.g., Wishlist → Travel, Review → Course).