How miguelcocohdez/proyecto-microservicios-riverspain works
Project type and purpose
• RiverSpain is a distributed system built as an academic project using a microservices architecture.
• Its core purpose is to manage data about rivers, fish species, protected zones, volunteers and to send notifications (e-mail) using Spring Boot, Spring Cloud (Eureka, Config Server), Docker and MySQL.
File structure
• At the root you have:
• docker-compose.yml – orchestrates all containers into a riverspain_network
• pom.xml – parent aggregator (optional)
• carpeta datospruebabdd – SQL scripts for initial data
• carpetas de microservicios independientes:
– microservicio-eureka (Service Discovery)
– microservicio-config (Central Config)
– microservicio-gateway (API Gateway)
– microservicio-peces, ‑rios, ‑zonas, ‑voluntarios, ‑batidas (domain services)
• Each microservice follows the standard Spring Boot layout:
src/main/java/com/riverspain/<servicename>/{application, config, dto, entity, repository, service, rest, client…}
• Each has its own application.yml, Dockerfile, and test suite.
README for additional insights
• It lists technologies (Spring Cloud Config, Eureka, Feign, JPA, Docker Compose).
• It describes deployment steps: create network, docker compose up, endpoint checks.
• It enumerates each microservice and notes “batidas” is maintained in a separate repo.
Capturing essential architectural elements
• Be extremely detailed: represent every microservice, infra service, database, network boundary and external dependency.
• Service registration, discovery, configuration fetch, request routing, inter-service calls, and persistence.