API Gateway
Also written as Kong, Apigee, Azure API Management, APIM
A single entry point that sits in front of multiple backend services, routing requests to the right one and often handling shared concerns like authentication, rate limiting, and logging in one place.
Think of it like
Like a building's front desk that checks every visitor's ID and directs them to the right department, instead of every department checking IDs at their own door.
Junior or senior?
Junior sounds like
Has only had requests pass through an API Gateway someone else set up.
Senior sounds like
Has configured one themselves and can describe what it handled centrally that each service would've otherwise duplicated.
Ask them
“What did your API Gateway handle centrally that each service would've otherwise had to implement separately?”