How jack20410/test-soa works
Components
• Frontend Application – Displays menus, dashboards, and order forms for different user roles (e.g., waiter, manager, kitchen staff).
• API Gateway – Acts as the central routing point to the internal services.
• Microservices:
– User Service – Manages user registration, authentication, and profiles; uses MySQL (user_db).
– Order Service – Processes and manages orders; integrates with User Service; uses MySQL (order_db).
– Kitchen Service – Handles kitchen orders and real-time order queue; uses MongoDB (kitchen_db).
• Databases:
– MySQL databases for the User and Order services.
– MongoDB for the Kitchen service.
• External Interfaces:
– Docker Compose – Orchestrates deployment.
– Service Development Environments and direct service-to-service communication (using HTTP requests).
Relationships and Interactions
• The Frontend connects to the API Gateway, which in turn routes requests to the appropriate microservices.
• Each microservice interacts with its own dedicated database.
• Services communicate with one another as needed (for instance, the Order Service may obtain user data from the User Service).
Architectural Patterns and Technologies
• Microservices architecture with clearly separated domain responsibilities.
• Use of an API Gateway to decouple the client-facing interface from the backend services.
• Containerization through Docker and composition via docker-compose.
• FastAPI (implied by how services are started with uvicorn) for backend services.
• Frontend built using modern JavaScript frameworks (React or similar, as seen from .jsx files and vite.config).