How fpaolant/realestateads works
Project type and purpose
• This is a full-stack, microservices/SOA system (“RealEstateAds”) composed of multiple Spring Boot modules (account, ads, wallet, geolocation, search, publish), a Spring Cloud Gateway, a Eureka Discovery server, and an Angular SPA client.
• Purpose: allow users to sign up, manage accounts and wallets, publish real-estate ads (with payment), and search ads by title, city or geographic radius.
File structure
• Top-level Maven modules:
• account-service, ads-service, wallet-service, geolocation-service (SOAP or REST providers)
• search-service, publish-service (prosumer services calling providers)
• gateway (Spring Cloud Gateway)
• discovery-service (Eureka Server)
• client (Angular SPA + Nginx)
• Supporting artifacts: wsdl/ and openapi/ definitions, docker-compose.yml, Dockerfiles in each module.
• Patterns: Microservices registered to Eureka, API Gateway as single entrypoint, prosumers orchestrate multiple provider calls asynchronously.
Key insights from the README
• Services categorized as Providers (REST or SOAP) and Prosumers (aggregators).
• Gateway routes ALL client requests to underlying services.
• Discovery service handles service registration and lookup.
• Sequence flows: Login, Signup, Search Ads, Publish Ad describe interactions through Gateway → Services.
• Blue for frontend/client
• Green for Gateway & Discovery
• Orange for REST Provider services
• Purple for SOAP Provider services
• Yellow for Prosumer services
• Grey for shared infrastructure (DB, WSDL/OpenAPI)