graph LR
API_Gateway["API Gateway"]
Client_Applications["Client Applications"]
Core_Microservices["Core Microservices"]
Unclassified["Unclassified"]
Client_Applications -- "sends Synchronous HTTP/S requests to" --> API_Gateway
API_Gateway -- "forwards Synchronous HTTP/S requests (internal) to" --> Core_Microservices
click API_Gateway href "https://github.com/CodeBoarding/GeneratedOnBoardings/blob/main/EShopMicroservices/API_Gateway.md" "Details"
The EShopMicroservices architecture is designed around a central API Gateway that acts as the primary entry point for all Client Applications. This gateway intelligently routes incoming synchronous HTTP/S requests to the appropriate Core Microservices, such as the Basket API and Catalog API. Beyond routing, the API Gateway centralizes cross-cutting concerns like authentication, authorization, and rate limiting, thereby simplifying client interactions and enhancing the overall security and manageability of the microservices landscape. The Core Microservices are responsible for encapsulating specific business capabilities and exposing their functionalities through well-defined HTTP/S endpoints, which the API Gateway then orchestrates.
API Gateway [Expand]
The API Gateway serves as the single, unified entry point for all client requests into the EShopMicroservices system. It is responsible for intelligently routing incoming requests to the appropriate backend microservices. Beyond simple routing, it centralizes critical cross-cutting concerns such as authentication, authorization, rate limiting, and potentially request aggregation or transformation, thereby offloading these responsibilities from individual microservices. This approach simplifies client-side interactions and enhances the overall security and manageability of the microservices landscape.
Related Classes/Methods:
These represent external applications (e.g., web, mobile, desktop) that consume the services exposed by the EShopMicroservices system. They interact with the system exclusively through the API Gateway.
Related Classes/Methods:
This component encompasses the individual, independently deployable microservices that implement the core business logic of the EShopMicroservices system. Examples include the Basket API, Catalog API, etc. These services expose their functionalities via HTTP/S endpoints, which are then consumed by the API Gateway.
Related Classes/Methods:
Component for all unclassified files and utility functions (Utility functions/External Libraries/Dependencies)
Related Classes/Methods: None