How esgi-doctodoc/doctodoc-api works
Project type and purpose
• This is a Java-based, monolithic, backend API built with Spring Boot 3 (Java 21).
• It follows a hexagonal (ports & adapters) architecture to orchestrate healthcare workflows between patients, doctors, and administrators.
File structure
• Top-level: Dockerfile, GitHub Actions CI/CD workflows, pom.xml.
• src/main/java/fr/esgi/doctodocapi: divided into
• configuration – Spring beans, filters, clocks, OpenAPI
• infrastructure – adapter implementations for JPA, external APIs (address, SMS, email, Firebase), S3, Stripe, cron jobs, JWT, WebSockets
• model – domain entities, value objects, exceptions, repositories interfaces
• use_cases – application services (ports in/out, DTOs, business logic)
• presentation – REST controllers, error handlers, response wrappers
• src/main/resources: application properties sample
• src/test: unit and integration tests
README for additional insights
• Describes features for Patients, Doctors, Admins.
• Mentions core business logic lives in DoctoDoc API.
• Confirms hexagonal design (configuration → infrastructure → model → use_cases → presentation).