How alessandrocavaglia/taas-2021-backend works
Project type and purpose
• This is a Java-based microservices backend for an online second-hand trading app (TAAS course).
• It consists of two domain services (User and Product), a service registry (Discovery/Eureka), an API gateway (Zuul), and a RabbitMQ broker.
• It’s deployable via Docker and Kubernetes.
File structure
• Top-level microservice folders:
– discovery-service: Eureka server to register and discover all services
– api-gateway: Netflix Zuul proxy routing client calls to microservices
– user-microservice: Spring Boot service managing users and Facebook integration
– product-microservice: Spring Boot service managing products, matches, tokens
• Messaging config: rabbitMQ.yaml at root for broker setup
• Deployment artifacts per service: Dockerfile, docker-compose.yml, deployment.yaml
• Parent pom.xml orchestrates multi-module build
README for additional insights
• Confirms use of Eureka for service discovery and Zuul for API gateway
• RabbitMQ as message broker between the two domain services
• Emphasis on containerization (Docker/ Kubernetes)
Detail
• Microservice’s registration with Eureka
• How API Gateway dynamically routes based on Eureka metadata
• Both synchronous HTTP calls and asynchronous message exchanges