Commonly I see people creating a 'microservice' that serves *all frontend requests, authenticate them and *orchestrates among all the real business microservices. It aims to facilitate the service consumption for the frontend.To my humble opinion, this violates core principles of microservices: 1. Multiple deployments will be required now to deploy a single feature - a change in the real service + a change to the gateway which approaches it 2. The gateway is a single point of failureThe gateway is actually a smart pipe which knows a lot of things about many servicesNote: I'm not referring to networking API gateway, a reverse proxy, which just performs 'dumb' HTTP related tasks
Submitted February 18, 2018 at 05:14PM by yonatannn
No comments:
Post a Comment