Is proxy an anti pattern to microservices?

If I am building an API with something like SpringBoot then I want the APIs to scale easily and be agile. Adding a layer like Apigee proxy will make me scale up/down Apigee layer when we scale backend, develop at two different layers using two different languages (By language I mean the DSL of Apigee policies).

Is it an anti pattern to use a proxy in front of microservices?

4 1 4,945
1 REPLY 1

Not applicable

This is a very good question. Service gateways (i.e. proxies) are not yet a generally acknowledged pattern within microservices, although there are plenty of good examples of people using them. In general, if you have requirements to manage versions, maintain consistent security, and have visibility into usage and performance, then a gateway is a good approach. Microservices in production do have these requirements and so we do suggest that microservice gateways are not a bad idea.