At 11:17 , There is a mistake -- Where I have mentioned, HTTP to be STATEFUL, and WebSocket API to be STATELESS, CORRECTION : Its the opposite, HTTP is STATELESS and WebSocket is STATEFUL
Timelines for your convenience: 00:00 // Intro 01:40 // What are APPLICATION PROGRAMMING INTERFACE? How does API work? Visual Explanations 15:44 // API - HTTP CLIENT SERVER MODEL 16:23 // API - REST BASED API MODEL 17:30 // API - WebSocket PROTOCOL 18:25 // What is a GATEWAY? 24:02 // What is AWS API GATEWAY and HOW DOES IT WORK? 29:03 // BENEFITS OF USING API GATEWAY 31:30 // Use API Gateway to create HTTP APIs 33:02 // Use API Gateway to create REST APIs 36:15 // Use API Gateway to create WebSocket APIs 40:57 // Who uses API Gateway? 42:24 // FEATURES OF API GATEWAY 45:03 // PRICING FOR API GATEWAY 46:18 // SECURITY FOR API GATEWAY 48:44 // Outro
ooh man , nice content i was searching to fetch data from s3 throw api and here i am with so much knowledge about aws, microservices, gateway with so much info
Thanks a lot for sharing your knowledge with us! your content is really helping me understand these AWS Solutions. I'm confident that I have a better understanding than before and can identify when to use API Gateway while designing my solution's architecture.
Hi .The videos are very helpful and easy to understand. Request you to make exam cram videos if possible, so that they can be viewed as a revision before exam covering all the important points for all topics.
I do not know how to say, but your way to teach and present informations is amazing, hope to see in the future more videos related to aws services. Nice work!
I faced the same question for websocket API in the exam today which you have discussed in the example 🙌🤩 Thanks for your efforts for bringing this content for free 🤝
@@Pythoholic I am facing a problem since am new to AWS can you help me? I want to create a lambda function to integrate two different APIs from an API gateway. 1. I am creating a form on my application to invoke an API on AWS (AWS endpoint) 2. Use the response of the API from step 1 and return the information back to the client. 3. Then based on the response, the client calls another API(different from the first one) passing some values of the response (from the first API). 4. Return the response from step 3 back to the client. I hope my intentions are clear to you. Can you suggest a way for me to do this?
Hi Pythoholic, Thanks for this awesome video. I was wondering if you could show something regarding how EKS can be integrated with API Gateway. If applications are hosted on pods in clusters, then how can we design the cloud infra so that API gateway can route traffic from intenet to EKS pods?
Yes, AWS offers the Amazon Elastic Load Balancing Application Load Balancer (ALB), which can be used with the AWS ALB Ingress Controller to manage external or internal HTTP(S) traffic for services running in a Kubernetes cluster. This solution is similar to the Azure Application Gateway Ingress Controller and works with any Kubernetes cluster, including Amazon Elastic Kubernetes Service (Amazon EKS)
Hey @@Pythoholic , thanks. However won't using an ALB require using one ALB per application. Suppose we have 10, then the cost would be much higher. Apparently use of Nginx Ingress controller was a more cost effective solution that was given by someone. I'm new to EKS and API Gateway, so please excuse if I'm saying illogical things. Just trying to learn. Thank you so much for your kind replies
An alternative solution like the Nginx Ingress controller can be more cost-effective because it allows you to handle traffic for multiple applications using a single load balancer instance, distributing traffic to various services within your cluster based on the rules defined in your ingress resources. As per concerns with using multiple ALBs for different applications in AWS, there is a method to implement a central ingress Application Load Balancer (ALB) that supports private Amazon Elastic Kubernetes Service (EKS) VPCs.
Sir IAM not able to understand the order of the videos.please can u help me out of this problem,and is there any prerequisite for doing this certification?
Hi Sai, the order is based on what is mentioned in the playlist. That is the order. No prerequisite but, if you have some knowledge of cloud that helps, But I am trying to share it as a perspective of a beginner.
Bidirectional in the sense . The server doesn’t send you request isn’t it. Web-sockets can send u notifications without u making a request in the socket connection. Let suppose in rest api once u send a request you either wait for the response or you do a polling. In websocket u dont have to poll, it will respond back when it’s ready
Mostly it will be simple. Like making external calls to execute functions and API Calls, which service would you make use of? In SAACo2, mostly it's about theory. What we have on the channel is beyond what's needed, aiming that it helps you not just for the exam but also in your real life.
@@Pythoholic thanks a lot for such awesome content and replying to queries instantly. This is really appreciated 😀 please keep making more videos 👍🏻🙏🏻🙏🏻🙏🏻
Both NGINX and API Gateway are tools that can be used in the context of managing and routing web traffic, but they serve different primary purposes and offer different features. Here's a comparison between the two: ### 1. Primary Purpose: **NGINX:** - NGINX is primarily a web server, similar to Apache or IIS. It can serve static content, act as a reverse proxy, and handle load balancing. - While it can be configured to handle some API management tasks, it's not its primary purpose. **API Gateway:** - An API Gateway is specifically designed to manage, secure, and route API traffic. - It provides features like rate limiting, authentication, logging, caching, and more, tailored for APIs. ### 2. Features: **NGINX:** - **Load Balancing:** Distributes incoming traffic across multiple servers. - **Static Content Serving:** Can serve static web content efficiently. - **Reverse Proxy:** Can forward requests to another server and return the response to the client. - **SSL Termination:** Handles the SSL handshake process, offloading the task from backend servers. - **HTTP/2 and WebSocket Support:** Modern protocol support for better performance and real-time communication. **API Gateway:** - **Rate Limiting:** Limits the number of API calls from a client in a given time frame. - **Authentication & Authorization:** Ensures only authorized clients can access the API. - **Request & Response Transformation:** Modifies API requests and responses on-the-fly. - **Logging & Monitoring:** Tracks API usage and performance. - **Caching:** Stores API responses to improve speed and reduce backend load. - **API Composition:** Aggregates multiple API calls into a single call. ### 3. Use Cases: **NGINX:** - Hosting websites and web applications. - Load balancing traffic across multiple servers. - Serving as a reverse proxy to forward requests to application servers. **API Gateway:** - Managing traffic for microservices architectures. - Securing APIs with authentication and authorization. - Monitoring and analyzing API usage and performance. ### 4. Flexibility: **NGINX:** - Highly configurable and can be extended with modules. However, for advanced API management features, you might need to integrate with third-party tools or use the commercial version, NGINX Plus. **API Gateway:** - Designed for API management, so it offers out-of-the-box features tailored for this purpose. Different API Gateway solutions (like AWS API Gateway, Kong, Apigee) might offer different sets of features. ### Conclusion: While there's some overlap in functionality, especially when using NGINX as a reverse proxy, the primary difference lies in the use case. If you're looking to manage, monitor, and secure your APIs, an API Gateway is the more appropriate tool. If you need a web server or load balancer, NGINX is a better fit. In many modern architectures, you might find both being used in tandem: NGINX serving web content and handling general traffic routing, with an API Gateway managing API-specific traffic.
At 11:17 , There is a mistake -- Where I have mentioned, HTTP to be STATEFUL, and WebSocket API to be STATELESS, CORRECTION : Its the opposite, HTTP is STATELESS and WebSocket is STATEFUL
This is brilliant. Never seen a RUclipsr response so quick and correcting it. Kudos to you bro.
No worries . Happy to help. And thanks for the feedback. It's what makes the channel be better.
yes i was left wondering
Timelines for your convenience:
00:00 // Intro
01:40 // What are APPLICATION PROGRAMMING INTERFACE? How does API work? Visual Explanations
15:44 // API - HTTP CLIENT SERVER MODEL
16:23 // API - REST BASED API MODEL
17:30 // API - WebSocket PROTOCOL
18:25 // What is a GATEWAY?
24:02 // What is AWS API GATEWAY and HOW DOES IT WORK?
29:03 // BENEFITS OF USING API GATEWAY
31:30 // Use API Gateway to create HTTP APIs
33:02 // Use API Gateway to create REST APIs
36:15 // Use API Gateway to create WebSocket APIs
40:57 // Who uses API Gateway?
42:24 // FEATURES OF API GATEWAY
45:03 // PRICING FOR API GATEWAY
46:18 // SECURITY FOR API GATEWAY
48:44 // Outro
Best tutorial ever 😊 Thanks u so much for provide us from scratching 🙏🏻😊
"Ignore my parrot in the background" LOL
You have great knowledge on AWS and processes. appreciated for sharing with all of us!
I am two days away from my exam and this series of lectures is great to use 48 hours - Keep it up
@Pythoholic, you are gifted teacher. Please can you make an explicit vide on AWS S3 Accesspoint practical with full demo
ooh man , nice content i was searching to fetch data from s3 throw api and here i am with so much knowledge about aws, microservices, gateway with so much info
The audio on this one is great please keep the audio quality St this same standard. It's much easier to understand and retain.
Fantastic video, I knew nothing it seems before this video! 😃
Presentation of content is impressive... great work. 👌
Superb explanation. very useful and thank you very much for your effort. we hope more videos related to AWS.
Your explain the concept really well. I have been trying to understand this from a long time. thank you so much!
Thanks 👍
Thanks a lot for sharing your knowledge with us! your content is really helping me understand these AWS Solutions.
I'm confident that I have a better understanding than before and can identify when to use API Gateway while designing my solution's architecture.
Thanks a lot for the support.
Please make a series for api gateway and upload more viedo for api gateway service
Thanks for explanation ❤
Hi .The videos are very helpful and easy to understand. Request you to make exam cram videos if possible, so that they can be viewed as a revision before exam covering all the important points for all topics.
Thanks for the suggestion. I will surely make one.
Wow, that was very insightful. Thank you for sharing.
Very nicely explained. Great job!
I do not know how to say, but your way to teach and present informations is amazing, hope to see in the future more videos related to aws services. Nice work!
Thanks a lot for the support. Its the support like this that keeps me going
I faced the same question for websocket API in the exam today which you have discussed in the example 🙌🤩
Thanks for your efforts for bringing this content for free 🤝
Thanks 👍
just brilliant!! ill probably be spamming all your vids with comments lol
Crystal clear explanation. Awesome !!!
Very knowledgeable....nice explanation
Thanks much sir, yes sir it would be great to have a real chat app developed thorugh websocket API
You are the Priest of AWS
Thank you very much. Your videos are guiding me through my first job.
awesome many congratulations!!!
@@Pythoholic I am facing a problem since am new to AWS can you help me? I want to create a lambda function to integrate two different APIs from an API gateway.
1. I am creating a form on my application to invoke an API on AWS (AWS endpoint)
2. Use the response of the API from step 1 and return the information back to the client.
3. Then based on the response, the client calls another API(different from the first one) passing some values of the response (from the first API).
4. Return the response from step 3 back to the client.
I hope my intentions are clear to you. Can you suggest a way for me to do this?
You are an awesome teacher!!
Thank You so much
Wonderful explanation.
Thank u naina
Hi Pythoholic,
Thanks for this awesome video.
I was wondering if you could show something regarding how EKS can be integrated with API Gateway. If applications are hosted on pods in clusters, then how can we design the cloud infra so that API gateway can route traffic from intenet to EKS pods?
Thanks remeshm.. I will surely try and put it out
Dear @@Pythoholic - Does AWS have anything like Azure Application Gateway Ingress controller?
Regards
Ramesh
Yes, AWS offers the Amazon Elastic Load Balancing Application Load Balancer (ALB), which can be used with the AWS ALB Ingress Controller to manage external or internal HTTP(S) traffic for services running in a Kubernetes cluster. This solution is similar to the Azure Application Gateway Ingress Controller and works with any Kubernetes cluster, including Amazon Elastic Kubernetes Service (Amazon EKS)
Hey @@Pythoholic , thanks. However won't using an ALB require using one ALB per application. Suppose we have 10, then the cost would be much higher. Apparently use of Nginx Ingress controller was a more cost effective solution that was given by someone. I'm new to EKS and API Gateway, so please excuse if I'm saying illogical things. Just trying to learn.
Thank you so much for your kind replies
An alternative solution like the Nginx Ingress controller can be more cost-effective because it allows you to handle traffic for multiple applications using a single load balancer instance, distributing traffic to various services within your cluster based on the rules defined in your ingress resources. As per concerns with using multiple ALBs for different applications in AWS, there is a method to implement a central ingress Application Load Balancer (ALB) that supports private Amazon Elastic Kubernetes Service (EKS) VPCs.
Superb video, please which animatio/graphic tool have u used for presentation? I need this to do a small presentation at work 🙏🏾
hi i use powerpoint thats it
What is that noise in the background?
Rest all is just excellent, thanks :)
Thanks for the feedback.. I have tried to improve in new videos
Thanks, #Subscribed😅
Very good explanation😎
thank you!
You're welcome!
so informative thanks
super
Hello...how u create these visualization ? from where u source different icons used here ?
Hi... I purchase the premium icons and design them using illustrator and ppt
Sir IAM not able to understand the order of the videos.please can u help me out of this problem,and is there any prerequisite for doing this certification?
Hi Sai, the order is based on what is mentioned in the playlist. That is the order. No prerequisite but, if you have some knowledge of cloud that helps, But I am trying to share it as a perspective of a beginner.
@@Pythoholic thank you sir got it :)
@@sainikithd8210 I have changed the order to avoid confusion, :)
@@Pythoholic thank you very much sir
Great work :-)
Your content is really helpful. One request can you make some videos on AWS best architecture design patterns
Thanks for the suggestion. Yes for sure we can do that.
@@Pythoholic thank you.
Hi ...is this topic for AWS solution architect or for both aws ssa and aws developers??
It's for Aws SAA C02
Websocket API is stateful. In one of your slides it said Websocket API is stateless
Is it let me check it. Thanks for the feedback
@@Pythoholic At 14.40 if I remember
@@gsuman0210 Thanks I have added a comment and pinned it.
WebSocket API is bidirectional but we also use bidirectional in rest API like put, delete?
Bidirectional in the sense . The server doesn’t send you request isn’t it.
Web-sockets can send u notifications without u making a request in the socket connection.
Let suppose in rest api once u send a request you either wait for the response or you do a polling.
In websocket u dont have to poll, it will respond back when it’s ready
@@Pythoholic got it! Thank you so much
Greatttttt
Cool
What sort of questions are expected out of API gateway in terms of associate exam? Pls comment
Mostly it will be simple. Like making external calls to execute functions and API Calls, which service would you make use of? In SAACo2, mostly it's about theory. What we have on the channel is beyond what's needed, aiming that it helps you not just for the exam but also in your real life.
@@Pythoholic thanks a lot for such awesome content and replying to queries instantly. This is really appreciated 😀 please keep making more videos 👍🏻🙏🏻🙏🏻🙏🏻
Would u be making the chatbot with websocket api please
I could actually. Do we need it with aws or python is fine?
So, can we say it's like nginx?
Both NGINX and API Gateway are tools that can be used in the context of managing and routing web traffic, but they serve different primary purposes and offer different features. Here's a comparison between the two:
### 1. Primary Purpose:
**NGINX:**
- NGINX is primarily a web server, similar to Apache or IIS. It can serve static content, act as a reverse proxy, and handle load balancing.
- While it can be configured to handle some API management tasks, it's not its primary purpose.
**API Gateway:**
- An API Gateway is specifically designed to manage, secure, and route API traffic.
- It provides features like rate limiting, authentication, logging, caching, and more, tailored for APIs.
### 2. Features:
**NGINX:**
- **Load Balancing:** Distributes incoming traffic across multiple servers.
- **Static Content Serving:** Can serve static web content efficiently.
- **Reverse Proxy:** Can forward requests to another server and return the response to the client.
- **SSL Termination:** Handles the SSL handshake process, offloading the task from backend servers.
- **HTTP/2 and WebSocket Support:** Modern protocol support for better performance and real-time communication.
**API Gateway:**
- **Rate Limiting:** Limits the number of API calls from a client in a given time frame.
- **Authentication & Authorization:** Ensures only authorized clients can access the API.
- **Request & Response Transformation:** Modifies API requests and responses on-the-fly.
- **Logging & Monitoring:** Tracks API usage and performance.
- **Caching:** Stores API responses to improve speed and reduce backend load.
- **API Composition:** Aggregates multiple API calls into a single call.
### 3. Use Cases:
**NGINX:**
- Hosting websites and web applications.
- Load balancing traffic across multiple servers.
- Serving as a reverse proxy to forward requests to application servers.
**API Gateway:**
- Managing traffic for microservices architectures.
- Securing APIs with authentication and authorization.
- Monitoring and analyzing API usage and performance.
### 4. Flexibility:
**NGINX:**
- Highly configurable and can be extended with modules. However, for advanced API management features, you might need to integrate with third-party tools or use the commercial version, NGINX Plus.
**API Gateway:**
- Designed for API management, so it offers out-of-the-box features tailored for this purpose. Different API Gateway solutions (like AWS API Gateway, Kong, Apigee) might offer different sets of features.
### Conclusion:
While there's some overlap in functionality, especially when using NGINX as a reverse proxy, the primary difference lies in the use case. If you're looking to manage, monitor, and secure your APIs, an API Gateway is the more appropriate tool. If you need a web server or load balancer, NGINX is a better fit. In many modern architectures, you might find both being used in tandem: NGINX serving web content and handling general traffic routing, with an API Gateway managing API-specific traffic.
when we expect VPC
Today we will have the introduction to VPC. Fingers Crossed!
may be i mistake route 53 and vpc is same
Sorry couldnt catch you !
@@Pythoholic Thanks for your reply.