Dev Byte’s Post

What does API gateway do? The diagram below shows the detail. Step 1 - The client sends an HTTP request to the API gateway. Step 2 - The API gateway parses and validates the attributes in the HTTP request. Step 3 - The API gateway performs allow-list/deny-list checks. Step 4 - The API gateway talks to an identity provider for authentication and authorization. Step 5 - The rate limiting rules are applied to the request. If it is over the limit, the request is rejected. Steps 6 and 7 - Now that the request has passed basic checks, the API gateway finds the relevant service to route to by path matching. Step 8 - The API gateway transforms the request into the appropriate protocol and sends it to backend microservices. Steps 9-12: The API gateway can handle errors properly, and deals with faults if the error takes a longer time to recover (circuit break). It can also leverage ELK (Elastic-Logstash-Kibana) stack for logging and monitoring. We sometimes cache data in the API gateway. Over to you: 1. What’s the difference between a load balancer and an API gateway? 2. Do we need to use different API gateways for PC, mobile and browser separately? {Let me know in the comments....} #bytebytego #sde #application #model #api Author -ByteByteGo Follow for more #Dev tips PRANAV VIKRAMAN ..

What does API gateway do? . . The diagram below shows the detail. Step 1 - The client sends an HTTP request to the API gateway. Step 2 - The API gateway parses and validates the attributes in the HTTP request. Step 3 - The API gateway performs allow-list/deny-list checks. Step 4 - The API gateway talks to an identity provider for authentication and authorization. Step 5 - The rate limiting rules are applied to the request. If it is over the limit, the request is rejected. Steps 6 and 7 - Now that the request has passed basic checks, the API gateway finds the relevant service to route to by path matching. Step 8 - The API gateway transforms the request into the appropriate protocol and sends it to backend microservices. Steps 9-12: The API gateway can handle errors properly, and deals with faults if the error takes a longer time to recover (circuit break). It can also leverage ELK (Elastic-Logstash-Kibana) stack for logging and monitoring. We sometimes cache data in the API gateway. Over to you: 1) What’s the difference between a load balancer and an API gateway? 2) Do we need to use different API gateways for PC, mobile and browser separately? – hashtag #systemdesign hashtag #coding hashtag #interviewtips Credit :ByteByteGo

What does API gateway do? . . The diagram below shows the details. Step 1 - The client sends an HTTP request to the API gateway. Step 2 - The API gateway parses and validates the attributes in the HTTP request. Step 3 - The API gateway performs allow-list/deny-list checks. Step 4 - The API gateway talks to an identity provider for authentication and authorization. Step 5 - The rate limiting rules are applied to the request. If it is over the limit, the request is rejected. Steps 6 and 7 - Now that the request has passed basic checks, the API gateway finds the relevant service to route to by path matching. Step 8 - The API gateway transforms the request into the appropriate protocol and sends it to backend microservices. Steps 9-12: The API gateway can handle errors properly, and deals with faults if the error takes a longer time to recover (circuit break). It can also leverage ELK (Elastic-Logstash-Kibana) stack for logging and monitoring. We sometimes cache data in the API gateway. Over to you: 1) What’s the difference between a load balancer and an API gateway? 2) Do we need to use different API gateways for PC, mobile and browser separately? *************** #𝐒𝐨𝐟𝐭𝐰𝐚𝐫𝐞 #𝐓𝐞𝐬𝐭𝐢𝐧𝐠 *************** 𝐍𝐞𝐰 𝐉𝐚𝐯𝐚 𝐒𝐞𝐥𝐞𝐧𝐢𝐮𝐦 𝐁𝐚𝐭𝐜𝐡 𝐢𝐬 𝐒𝐭𝐚𝐫𝐭𝐢𝐧𝐠 𝐟𝐫𝐨𝐦 𝟓𝐭𝐡 𝐀𝐮𝐠𝐮𝐬𝐭 𝐑𝐞𝐠𝐢𝐬𝐭𝐞𝐫 𝐡𝐞𝐫𝐞 𝐭𝐨 𝐀𝐭𝐭𝐞𝐧𝐝 𝐅𝐫𝐞𝐞 𝐃𝐞𝐦𝐨:- https://lnkd.in/g5HQ_Z-X 𝐅𝐨𝐫 𝐦𝐨𝐫𝐞 𝐢𝐧𝐬𝐢𝐠𝐡𝐭𝐟𝐮𝐥 𝐮𝐩𝐝𝐚𝐭𝐞𝐬 𝐚𝐧𝐝 𝐭𝐢𝐩𝐬 𝐫𝐞𝐥𝐚𝐭𝐞𝐝 𝐭𝐨 𝐓𝐞𝐬𝐭𝐢𝐧𝐠. 𝐉𝐨𝐢𝐧 𝐦𝐲 𝐓𝐞𝐥𝐞𝐠𝐫𝐚𝐦 𝐂𝐡𝐚𝐧𝐧𝐞𝐥:- https://lnkd.in/dmT_T-mY Credit: ByteByteGo

𝗪𝗵𝗮𝘁 𝗱𝗼𝗲𝘀 𝗔𝗣𝗜 𝗴𝗮𝘁𝗲𝘄𝗮𝘆 𝗱𝗼? 𝗦𝘁𝗲𝗽 𝟭 - The client sends an HTTP request to the API gateway. 𝗦𝘁𝗲𝗽 2 - The API gateway parses and validates the attributes in the HTTP request. 𝗦𝘁𝗲𝗽 𝟯 - The API gateway performs allow-list/deny-list checks. 𝗦𝘁𝗲𝗽 𝟰 - The API gateway talks to an identity provider for authentication and authorization. 𝗦𝘁𝗲𝗽 𝟱 - The rate limiting rules are applied to the request. If it is over the limit, the request is rejected. 𝗦𝘁𝗲𝗽𝘀 𝟲 𝗮𝗻𝗱 𝟳 - Now that the request has passed basic checks, the API gateway finds the relevant service to route to by path matching. 𝗦𝘁𝗲𝗽 𝟴 - The API gateway transforms the request into the appropriate protocol and sends it to backend microservices. 𝗦𝘁𝗲𝗽𝘀 𝟵-𝟭𝟮: The API gateway can handle errors properly, and deals with faults if the error takes a longer time to recover (circuit break). It can also leverage ELK (Elastic-Logstash-Kibana) stack for logging and monitoring. We sometimes cache data in the API gateway.

What does API gateway do? . . The diagram below shows the detail. Step 1 - The client sends an HTTP request to the API gateway. Step 2 - The API gateway parses and validates the attributes in the HTTP request. Step 3 - The API gateway performs allow-list/deny-list checks. Step 4 - The API gateway talks to an identity provider for authentication and authorization. Step 5 - The rate limiting rules are applied to the request. If it is over the limit, the request is rejected. Steps 6 and 7 - Now that the request has passed basic checks, the API gateway finds the relevant service to route to by path matching. Step 8 - The API gateway transforms the request into the appropriate protocol and sends it to backend microservices. Steps 9-12: The API gateway can handle errors properly, and deals with faults if the error takes a longer time to recover (circuit break). It can also leverage ELK (Elastic-Logstash-Kibana) stack for logging and monitoring. We sometimes cache data in the API gateway. Over to you: 1) What’s the difference between a load balancer and an API gateway? 2) Do we need to use different API gateways for PC, mobile and browser separately #interviewtips #coding #systemdesign

What does API gateway do? Step 1 - The client sends an HTTP request to the API gateway. Step 2 - The API gateway parses and validates the attributes in the HTTP request. Step 3 - The API gateway performs allow-list/deny-list checks. Step 4 - The API gateway talks to an identity provider for authentication and authorization. Step 5 - The rate limiting rules are applied to the request. If it is over the limit, the request is rejected. Steps 6 and 7 - Now that the request has passed basic checks, the API gateway finds the relevant service to route to by path matching. Step 8 - The API gateway transforms the request into the appropriate protocol and sends it to backend microservices. Steps 9-12: The API gateway can handle errors properly, and deals with faults if the error takes a longer time to recover (circuit break). It can also leverage ELK (Elastic-Logstash-Kibana) stack for logging and monitoring. We sometimes cache data in the API gateway. Over to you: 1. What’s the difference between a load balancer and an API gateway? 2. Do we need to use different API gateways for PC, mobile and browser separately?

What does API gateway do? Step 1 - The client sends an HTTP request to the API gateway. Step 2 - The API gateway parses and validates the attributes in the HTTP request. Step 3 - The API gateway performs allow-list/deny-list checks. Step 4 - The API gateway talks to an identity provider for authentication and authorization. Step 5 - The rate limiting rules are applied to the request. If it is over the limit, the request is rejected. Steps 6 and 7 - Now that the request has passed basic checks, the API gateway finds the relevant service to route to by path matching. Step 8 - The API gateway transforms the request into the appropriate protocol and sends it to backend microservices. Steps 9-12: The API gateway can handle errors properly, and deals with faults if the error takes a longer time to recover (circuit break). It can also leverage ELK (Elastic-Logstash-Kibana) stack for logging and monitoring. We sometimes cache data in the API gateway. Over to you: 1) What’s the difference between a load balancer and an API gateway? 2) Do we need to use different API gateways for PC, mobile and browser separately?

𝐖𝐡𝐚𝐭 𝐝𝐨𝐞𝐬 𝐀𝐏𝐈 𝐠𝐚𝐭𝐞𝐰𝐚𝐲 𝐝𝐨? . . The diagram below shows the details. Step 1 - The client sends an HTTP request to the API gateway. Step 2 - The API gateway parses and validates the attributes in the HTTP request. Step 3 - The API gateway performs allow-list/deny-list checks. Step 4 - The API gateway talks to an identity provider for authentication and authorization. Step 5 - The rate limiting rules are applied to the request. If it is over the limit, the request is rejected. Steps 6 and 7 - Now that the request has passed basic checks, the API gateway finds the relevant service to route to by path matching. Step 8 - The API gateway transforms the request into the appropriate protocol and sends it to backend microservices. Steps 9-12: The API gateway can handle errors properly, and deals with faults if the error takes a longer time to recover (circuit break). It can also leverage ELK (Elastic-Logstash-Kibana) stack for logging and monitoring. We sometimes cache data in the API gateway. Over to you: 1) What’s the difference between a load balancer and an API gateway? 2) Do we need to use different API gateways for PC, mobile, and browser separately? Follow me Jafar Muzeyin Credit ByteByteGo #systemdesign #coding #interviewtips 

What does an API gateway do in 12 SIMPLIFIED steps? 1 - The client sends an HTTP request to the API gateway. 2 - The API gateway parses and validates the attributes in the HTTP request. 3 - The API gateway performs allow-list/deny-list checks. 4 - The API gateway talks to an identity provider for authentication and authorization. 5 - The rate limiting rules are applied to the request. If it is over the limit, the request is rejected. 6 and 7 - Now that the request has passed basic checks, the API gateway finds the relevant service to route to by path matching. 8 - The API gateway transforms the request into the appropriate protocol and sends it to backend microservices. 9-12: The API gateway can handle errors properly, and deals with faults if the error takes a longer time to recover (circuit break). It can also leverage ELK (Elastic-Logstash-Kibana) stack for logging and monitoring. We sometimes cache data in the API gateway.