How ymidortega/clinica works
Project type and purpose
• This is a full-stack, microservices-based clinic management system (“Sistema de Gestión de Clínica Médica”).
• Backend: Nine Spring Boot microservices (Eureka service discovery, API gateway, authentication, patient, billing, admissions, AI assistant, suppliers, clients).
• Frontend: Astro (modern web UI).
• Datastores: multiple MySQL and PostgreSQL databases plus Redis for cache/sessions.
File structure
• Top‐level “BackEnd-Clinica” folder holds one directory per microservice. Each follows a standard Maven/Spring Boot layout (src/main/java, resources, Dockerfile, HELP.md, pom.xml).
• eureka-service
• api-gateway
• auth-service
• patient-service
• billing-service
• admissions-service
• ai-assistant-service
• suppliers-service
• clients-service
• Root “docker-compose.yml” orchestrates all services plus databases (MySQL, PostgreSQL) and Redis.
• “FrontEnd-Clinica” holds Astro config, pages, components, public assets.
README for additional insights
• Confirms microservice roles, ports, DB connection details, environment variables, Swagger/OpenAPI per service, Actuator endpoints, and Docker Compose usage.
• Highlights technology stack: Java 21, Spring Boot 3.5, Spring Cloud 2025.0, Maven, Lombok, MapStruct, Docker, Astro, pnpm.
Detail
• Nine microservices plus Eureka and API Gateway
• Database instance explicitly
• Docker Compose as the deployment orchestration layer
• Environment variables or config store block if needed
• Swagger/OpenAPI aggregation via the API Gateway