clear to its core.

Just found your channel. Wanted to say your content is amazing. Keep the good work. This channel is a hidden gem 💎

@ByteMonk

8 ай бұрын

Thanks a ton!

Thanks for the informative video. I am a beginner in System Design and I have following doubts related to this- 1. API gateway is like a middleman between computer and other computer programs- do the computer programs reside on the same computer or different? 2. When do I have to worry about creating an API gateway? Is it when I am building a system that needs to make API calls or when I am building the API which needs to be called by my clients?

@ByteMonk

Жыл бұрын

1. In the context of API gateway, the computer programs typically reside on different computers or systems. The API gateway acts as an intermediary or middleman that facilitates communication and data exchange between these distinct programs. It helps manage and control the flow of data, requests, and responses between various components, such as client applications, microservices, and backend systems. By serving as a centralized entry point, the API gateway enables seamless integration and coordination among distributed computer programs, regardless of their physical location. 2. You typically need to consider creating an API gateway when you are building the API that needs to be called by your clients. The API gateway serves as a single point of entry for client applications to access your API. It provides a layer of abstraction that decouples the clients from the underlying microservices or backend systems. If you are a beginner, I suggest checking out my course on System Design here: kzread.info/head/PLJq-63ZRPdBt423WbyAD1YZO0Ljo1pzvY

Is it necessary that api gateway also serves the rate limiting?? ,for rate limiting we have dedicated resource(Oracle rate limiter),internaly they work on rate wheeler algorithm ..So is it not a extra load to the system when you are given this task to the gateway?? (technicaly though we can do that by balancing the request and then distribute it across the server ) .Thanks for the easiest explanation of the concept .Much Appreciated..

@ByteMonk

11 ай бұрын

You're welcome! I'm glad I could help. Regarding rate limiting in an API gateway, while it's a common practice for an API gateway to handle rate limiting, it's not an absolute requirement. You can certainly use dedicated resources like the Oracle rate limiter, especially if you have specific rate limiting needs or existing systems in place. Using an API gateway for rate limiting offers a centralized and unified approach, simplifying management and control across multiple APIs or microservices. However, you rightly pointed out that there can be a concern about adding extra load to the gateway, especially when dealing with a high volume of requests. In cases where you have dedicated rate limiting resources or other specialized tools, you can indeed offload rate limiting from the API gateway. This can help distribute the load more efficiently and ensure that each component is optimized for its specific role. The decision on where to handle rate limiting depends on factors like your system's architecture, performance requirements, and the capabilities of your existing tools. It's all about finding the right balance between centralization and distribution of responsibilities to ensure your system functions optimally and reliably.

@stefano_schmidt

10 ай бұрын

​@@ByteMonklooks like chatGpt answer ))