How f-lab-edu/daangn-market-used-trading works
Project type and purpose
• This is a backend‐only monolithic API server modeled on “당근마켓” (Carrot Market).
• Built with Spring Boot (Java), it exposes REST endpoints for posts, members, and image uploads.
• It is designed to handle high traffic, session consistency in a distributed environment, caching, and file storage.
File structure
• Top-level artifacts:
– Dockerfile, Jenkinsfile/Jenkinsfile-ci → CI/CD and containerization
– pom.xml, mvnw → Maven Spring Boot build
• src/main/java/com/ssibongee/daangnmarket: package structure shows a layered architecture:
– commons: cross-cutting concerns (AOP, annotation, configuration, caching, security, data source routing)
– image: controllers → services → repositories → AWS S3 integration
– member: controllers → services → repositories (session/login, validation, exceptions)
– post: controllers → services → repositories (CRUD, search, trade status)
• src/main/resources/application.properties → externalized configuration
• tests under src/test/java → unit and integration tests
• config classes for DataSourceConfig (master/replica routing), RedisCacheConfig, RedisSessionConfig
README for additional insights
• Architecture goals: high availability, distributed sessions, cache no downtime, CI/CD with Jenkins & Docker
• Tech stack: Spring Boot, MySQL (or RDBMS), Redis (cache & session store), AWS S3, Jenkins, Docker, nGrinder for load testing