How ddog-org/daengle-server works
Project type and purpose
• This is a large-scale, back-end focused, multi-module microservices platform (“댕글”) for dog grooming and health-care mediation.
• It follows Domain-Driven Design (DDD) and Hexagonal Architecture: a central domain module (daengle-domain) and multiple Spring-Boot API microservices (auth, chat, user, groomer, vet, payment, notification), plus dedicated persistence adapters (RDB, NoSQL, queue).
File structure
• Top-level Gradle modules:
• daengle-auth: JWT-based authentication/authorization
• daengle-chat-api: WebSocket chat, DynamoDB persistence
• daengle-user-api, daengle-groomer-api, daengle-vet-api: role-specific REST APIs
• daengle-payment-api: integrates with Iamport, AWS SNS/SQS, handles orders and callbacks
• daengle-notification-api: listens on SQS, pushes notifications (Kakao, WebSocket)
• daengle-domain: pure domain model with ports/interfaces
• daengle-persistence-rdb, -nosql, -queue: adapters implementing ports
• CI/CD workflows: under .github/workflows for dev/prod deploy and integration testing.
README for additional insights
• The README includes architecture event-flow, multi-module layout, sequence flows for payments, ban-word filtering trie flow, DynamoDB chat flow, ERD for relational data.
• Tech stack: Spring Boot, Gradle, AWS (DynamoDB, RDS, SQS, SNS), WebSocket, Kakao social login, Iamport.
Elements
• Clear labels: service names, database names, queue/topic names
• Client → API Gateway → Services
• Service → Persistence → Database
• Service → SNS → SQS → Notification Service
• Microservices (blue rectangles)
• Domain module (green)
• Persistence adapters (orange)
• External systems (grey ovals)