All geek questions in one place

Api Gateway or No Api Gateway

I am developing an application based microservice architecture. Here, each serviceis an independently deployable play-scala applicationexposure rest apis. I want to implement Api gatewayon top of these services to display incoming requests. I follow the architecture described here: Building Microservices

There are very few projects with significant maturity based on microservice architecture. One of them is Reactive Microservices . But this project does not use api gateway patternand seems to be following the Anti Pattern issue open for this project regarding the missing Api Gateway here. The authors here argue that they did not follow api gateway patternbecause he has a risk single-point of failure.

This different opinion really confuses me. So, I am looking for suggestions on whether I should use Api Gateway or not.What is the right practice here ?

+4
source share
1 answer

The API gateway does not introduce a single point of failure, as does the load balancer. Any serious API gateway should operate in high availability mode, removing a single point of failure.

The API gateway encourages good documentation and planning within teams. Some API gateways allow you to import Swagger specifications https://swagger.io/ to create an API.

, . , , , .

API , . healthcheck LB, .

auth . JWT, Oauth, Simple, Open .. . . .

+1

Source: https://habr.com/ru/post/1621517/

More articles:


All Articles