APIs, or Application Programming Interfaces, are a set of rules and protocols that allows two software applications or services to communicate with each other.
This article is a fantastic guide to understanding API Gateways! The clear explanations of features like authentication, rate limiting, and request handling, along with practical examples, make it super easy to follow.
Your posts are consistently informative! The way you break down complex API design concepts has helped me a lot. In fact, I’ve begun using EchoAPI, and it’s been a game changer in simplifying my design process.
This article is really insightful and I have picked a lot of lessons, but I am curious to ask. Is API gateway really worth it? I am sorry for sounding foolish. But, I am looking at it from the perspective of scaling. While i understand the immerse benefits it brings especially from the pov of central access control, rather than having each micro-service defining define authentication/authorization, you can just do the definition on the api gateway.
Let me put this into more context, say I have an api gateway that connects to 3 micro-services (payment, onboarding and inventory). But i get more hits to the payments and onboarding, and which sometimes lead to slowness.
1. How do I scale? Should I scale the api gateway or the payment/onboarding service.
2. What if the api gateway goes down, and the 3 other micro-services are still up and running. How do I manage/mitigate against that happening?
This article is a fantastic guide to understanding API Gateways! The clear explanations of features like authentication, rate limiting, and request handling, along with practical examples, make it super easy to follow.
looking forward to more such insightful content!
love to hear this, thank you!
Your posts are consistently informative! The way you break down complex API design concepts has helped me a lot. In fact, I’ve begun using EchoAPI, and it’s been a game changer in simplifying my design process.
Very insightful. Thank you Ashish, such a wonderful explanation
This article is really insightful and I have picked a lot of lessons, but I am curious to ask. Is API gateway really worth it? I am sorry for sounding foolish. But, I am looking at it from the perspective of scaling. While i understand the immerse benefits it brings especially from the pov of central access control, rather than having each micro-service defining define authentication/authorization, you can just do the definition on the api gateway.
Let me put this into more context, say I have an api gateway that connects to 3 micro-services (payment, onboarding and inventory). But i get more hits to the payments and onboarding, and which sometimes lead to slowness.
1. How do I scale? Should I scale the api gateway or the payment/onboarding service.
2. What if the api gateway goes down, and the 3 other micro-services are still up and running. How do I manage/mitigate against that happening?