In a microservice architecture, if an API Gateway 1 already serves as an endpoint for Client 1. After a period of time, Client 2 comes in with the need for similar yet not exact functionalities while consuming the same core services.
Is it a better solution to create a custom API Gateway 2 for it, so in the future custom changes can be added easily while dealing with duplicate code. Or keep using API Gateway 1 for both, so future changes are done once while dealing with different implementations sometimes?
I'm targeting a solution that can scale and easily support multiple clients.
Any suggestion or resource shared is appreciated.
question from:https://stackoverflow.com/questions/65943922/microservices-one-vs-multiple-api-gateways-for-multiple-clients
