How keerthikumarn/food-ordering-portal works
Project type and purpose
• This is a Spring-Boot and Maven-based microservices project implementing a “Food Ordering Portal.”
• It consists of four modules:
• eureka-service (service registry)
• usermanagement-service (user CRUD)
• restaurant-listing (restaurant info)
• food-menu (menu items)
File structure
• Each module is a standalone Spring Boot application (has its own pom.xml, src/main/java, src/main/resources/application.properties).
• Common package layering in each service: controller → dto/entity → mapper → service → repo.
• No single frontend or gateway module present; services likely expose REST APIs directly.
README
• Very brief: “Food ordering portal.”
• No built-in frontend or API Gateway.
Main components
a. eureka-service
• Acts as the Netflix Eureka server (service registry)
b. usermanagement-service
• Exposes endpoints for User operations
• Persists data to its own database
c. restaurant-listing-service
• Manages restaurant metadata
• Own database
d. food-menu-service
• Manages menu items, links to restaurants
• Own database
e. Client (e.g., Browser or Mobile App)
• Consumes REST APIs
Relationships and interactions
• On startup, each microservice registers itself with Eureka.
• The client discovers service instances via Eureka (or a future API Gateway).
• Client → (via load-balancer) → service’s REST controller → service layer → repository → database.
• Services may call one another for composite operations (e.g., an ordering service could call usermanagement & food-menu), but that’s out of scope.
Architectural patterns and principles
• Microservices pattern: small, independently deployable Spring Boot apps
• Layered (onion) architecture within each service (Controller → Service → Repository)
• Service Discovery (Eureka) for dynamic resolution and load balancing
• Each service encloses its own datastore (database-per-service) for data autonomy
Relevant technologies and frameworks
• Spring Boot (starter-web, spring-data-jpa)
• Netflix Eureka (spring-cloud-netflix-eureka-server / client)
• Maven for build and dependency management
• JPA/Hibernate for persistence
• RESTful APIs using Spring MVC controllers
Details to capture
• Service names and ports (if known, e.g., 8761 for Eureka)
• The fact that each .properties file configures its database datasource
• Future extension points: API Gateway, messaging bus, external payment service