How josephmn/api-services-all works
Project type and purpose
• From the file tree and minimal README, this is a Spring-based monolithic API service (“api-services-all”) built with Maven.
• It exposes REST endpoints (in the controller layer) for different external providers (e.g., EmapaCanete, LuzDelSur), orchestrates calls via WebClient, maps/parses responses, and returns DTOs.
File structure
• Top-level:
• pom.xml / Maven wrapper → Java, Spring Boot project
• src/main/java/com/services/api/all → code under one spring-boot module
• Under api/all:
• config → JacksonConfig, WebClientConfig (app-wide beans)
• controller → REST controllers
• dto → request/response payload objects
• service → service interfaces
• service/impl → business logic, calling external APIs
• util → mappers, HTMLParser
• src/main/resources/application.yml → runtime properties
Diagramming conventions
• Controllers (blue)
• Services (green)
• Utils (yellow)
• Config (gray)
• External (red)
• Rectangles for components