PRs? MRs? What?
For those of you who are new to software development, Pull Requests (PRs) or Merge Requests (MRs) are…well requests that you make in order to get your newly added/modified code into a parent branch. If you’re at the beginning you might not have done this if you worked alone on your personal projects, and just commited everything on the master branch, but in “real life” projects, where teams have more than 1 member, this is the AS IS way of doing things, to keep the already chaotic process of development under some kind of control.
But WHY..
Let’s get a bit more…
In your typical microservice architecture the main access point (and desirably the only one) to the inside of it should be the apigateway. So its job is to route the requests, as the first line of interaction between outside world and the inside, to the appropriate microservice based on different values that the request has. Some endpoints are private therefore they might require, let’s say, a specific token to be passed with the request (eg. JWT auhorization).
In this case, instead of computing (here I’m referring to decrypt the JWT signature) whether or not the caller is who they say…
ALex Antonica
Software engineer in my 5th year now, passionate and curious about new technologies, practices and ways of thinking. Never stop growing.
