How afks-fundamentos/backend works
Project type and purpose
• This is a standalone backend service (Spring Boot) implementing an “Advisory Management” domain.
• It follows Domain-Driven Design (DDD) and a layered/CQRS pattern: REST interfaces → Application services → Domain model → Persistence.
File structure
• Top-level files: pom.xml, maven wrapper, Application.java (Spring Boot entry).
• src/main/java/com/pcmaster/AFK/… splits into:
– advisorymanagement (the core bounded context)
· interfaces/rest (Spring MVC controllers, resource DTOs, assemblers)
· application/internal (command and query service implementations)
· domain/model (aggregates, commands, queries, value objects)
· domain/services (ports for business logic)
· infrastructure/persistence/jpa (Spring Data JPA repositories)
– config (SecurityConfig, ValidationConfig)
– shared (common domain abstractions, JPA naming strategy, OpenAPI config)
• Resources: application.properties, OpenAPI docs.
README
• Minimal—only “# Backend.” No additional architectural notes.