How team-promesa/promesa-backend works
Project type and purpose
• From the file tree and README we see this is “Promesa-Backend,” a monolithic Spring Boot application that powers Promesa, an art exhibition and sales platform for ceramic artists.
• It exposes a REST API (controllers under src/main/java/com/promesa/promesa/domain/*/api) backed by business logic (service classes) and persisting data to a relational database. It integrates with AWS S3 for image storage and uses OAuth2/JWT for authentication/authorization.
File structure
• Top-level artifacts
• build.gradle / gradle wrapper: Java build system
• Dockerfile, scripts/, appspec.yml: packaging and deployment (Docker, CodeDeploy)
• .github/workflows: CI pipelines (build & deploy)
• src/main/java/com/promesa/promesa/common: cross-cutting concerns (exception handlers, advice, configuration for Jackson, CORS, security, Swagger, QueryDSL, S3, OAuth2Service, etc.)
• src/main/java/com/promesa/promesa/domain: 11 subdomains (artist, category, exhibition, home, inquiry, item, itemCategory, member, review, wish) each following the pattern
– api: REST controllers
– application: service layer
– dao: Spring Data repositories
– domain: JPA entities & value types
– dto: request/response objects
– exception: domain-specific errors
– query (in some modules): custom QueryDSL-based repositories
• src/main/java/com/promesa/promesa/security: JWT filters, token provider, refresh tokens, logout, OAuth2 user service
• src/main/resources: multiple profiles (local, test, prod), SQL initialization, static assets
• data/: H2 database files for local testing
README for additional insights
• The README is succinct, confirming the purpose: “Promesa – platform for exhibiting & selling ceramic artwork.”
Key points
• Cross-cutting and domain-specific components
• Security chain (JWT filter, OAuth2 service, refresh token flow)
• Don’t just show “Backend” – decompose into layers and external dependencies