How johnbenjaminmccarthy/mathsgenealogyapi works
Data Flow Representation
• Client Request → Controllers → Services → [Repositories ↔ Database]
• → [Scraper ↔ External Website]
Key Components Detail
• Domain Models (Node, Edge, Advisor, Dissertation)
• DTOs (NodeDto, EdgeDto, etc.)
• Data conversion flow (Entity ↔ DTO)
Architectural Patterns to Highlight
a. Layer separation:
• Presentation (Controllers)
• Business Logic (Services)
• Data Access (Repositories)
• External Integration (Scraper)
b. Caching Strategy:
• Database caching mechanism
• 30-day refresh policy
Technical Stack Callouts
Technology badges or notes for:
• Spring Boot
• Hibernate
• PostgreSQL
• Docker
• Jsoup (for scraping)
• Log4j2
Component Interactions
• User-facing components (e.g., controllers)
• Business logic (services)
• Data persistence (repositories and database)
• External integration (scraper)
A small example of the graph structure (similar to the one in the README) to illustrate the actual data representation.