- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
In a cloud native architecture with an API Gateway, you typically do not need to create equivalent APIs in the API Gateway for each of your microservices. Instead, you can use the API Gateway to create a single, unified API that provides a single entry point for your client applications to access the functionality exposed by your microservices.
To do this, you can create a single API in the API Gateway and define multiple resources within that API to represent the different functionality exposed by your microservices. For example, you could create a resource for the "order" microservice, a resource for the "customer" microservice, and a resource for the "payment" microservice.
Within each of these resources, you can then define methods (such as "GET" and "POST") that map to the corresponding endpoints in your microservices. So, in the case of your three microservices, you would likely define three resources with two methods each, for a total of six methods.
You do not need to create a separate microservice for each method in the API Gateway. Instead, you can use the API Gateway to route requests from your client applications to the appropriate microservice and endpoint based on the resource and method specified in the request. This allows you to keep your microservices simple and focused on a specific set of functionality, while using the API Gateway to handle the cross-cutting concerns such as authentication, authorization, and rate limiting.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Thanks for the detailed response, it helps. I have added a few more questions (#4 to 6) based on your answer. Appreciate if you can clarify.