What is an API Gateway? | WHAT IS API? | Complete Guide | VISUAL EXPLANATIONS

In this session, you will get to learn about AWS API Gateways from a very basic level, from scratch. If you are a beginner and you are not aware of APIs, Watch this to learn more.
⭐ Kite is a free AI-powered coding assistant that will help you code faster and smarter. The Kite plugin integrates with all the top editors and IDEs to give you smart completions and documentation while you’re typing. I've been using Kite for 6 months and I love it!
www.kite.com/get-kite/?...
Application Program Interface
API or the short form of what we call the Application Programming Interface is a software mediator that allows two applications to talk to each other.
So the application is basically your software program which is designed for the specific use case and when 2 programs want to communicate, they want an interface through which they can talk to each other.
When we talk about Application integration, So the next time you think of using a service provided by another application and you wish to integrate it into your program or software. THINK OF APIS
APIs are everywhere now,
Talk about Instagram,
Talk about Github
Talk about youtube
or even Twitter
When you need the information on how to use the features of these apps in your application, make sure you check the APIS.
Amazon API Gateway is a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale.
It may not be your conventional gateway but, sometimes you might think why is it called as API Gateway
So as I mentioned before it also sits in between your users and your services and acts as a doorway for all the API requests, like HTTP API or REST API or TCP API as well.
OK, now let's get some more details about API Gateways.
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
AWS Solutions Architect Associate Certification 2020 Playlist:
tinyurl.com/y4lr8zu4
Please follow we in the links below to stay updated: 🙌
🍀Click on the link below to subscribe: tinyurl.com/qqebnwz
🍀Instagram: / tougherapollo
🍀Twitter: / tougherapollo1
🍀Discord: / discord
🍀Care to share: / pythoholic
Disclaimer: The content provided in the channel are not affiliated in any way to the organization. We provide information here on the channel based on the knowledge we have on the topic. We advise our viewers to please do their own research and read more about them from the source provided by the organization to get a better outlook on the topic that has been covered.
These videos are just to provide you a platform to learn, and there can be mistakes and we are always trying to improve based on your feedback. we recommend viewers to have an open mind. Please support the channel to get more content like these in the future.
#ApiGateway #AWSSolutionsArchitectAssociate2020 #AWSAPIGATEWAY

[@Pythoholic]

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

[@gsuman0210]

This is brilliant. Never seen a KZbinr response so quick and correcting it. Kudos to you bro.

[@Pythoholic]

No worries . Happy to help. And thanks for the feedback. It's what makes the channel be better.

[@crsingh1565]

yes i was left wondering

[@Pythoholic]

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

[@ravinamohite9031]

Best tutorial ever 😊 Thanks u so much for provide us from scratching 🙏🏻😊

[@vamskrishnakadiyala2730]

You have great knowledge on AWS and processes. appreciated for sharing with all of us!

[@abhishekgowlikar]

Crystal clear explanation. Awesome !!!

[@OCDBeats]

"Ignore my parrot in the background" LOL

[@chantellethompson5237]

Fantastic video, I knew nothing it seems before this video! 😃

[@nilfarmohamed4778]

Superb explanation. very useful and thank you very much for your effort. we hope more videos related to AWS.

[@thenoobplay1312]

Presentation of content is impressive... great work. 👌

[@shreyas-rao]

Your explain the concept really well. I have been trying to understand this from a long time. thank you so much!

[@Pythoholic]

Thanks 👍

[@jdop2605]

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

[@RaoBhethanabotla]

Very nicely explained. Great job!

[@utoobbott8817]

You are an awesome teacher!!

[@yadav-r]

Wow, that was very insightful. Thank you for sharing.

[@crsingh1565]

I am two days away from my exam and this series of lectures is great to use 48 hours - Keep it up

[@techrohhit]

Thanks for explanation ❤

[@chytrak4060]

Very knowledgeable....nice explanation

[@muhammadatharkhan8695]

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.

[@Pythoholic]

Thanks a lot for the support.

[@SamruddhaShah]

so informative thanks

[@hitmusicworldwide]

The audio on this one is great please keep the audio quality St this same standard. It's much easier to understand and retain.

[@LEGSUDESIRE]

Thank You so much

[@user-ur7fe3js5h]

Thank you very much. Your videos are guiding me through my first job.

[@Pythoholic]

awesome many congratulations!!!

[@user-ur7fe3js5h]

@@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?

[@priyatiwari6331]

Please make a series for api gateway and upload more viedo for api gateway service

[@robertsmith9994]

You are the Priest of AWS

[@abhiramdikkala]

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]

Thanks 👍

[@nikhilbharadwaj8972]

just brilliant!! ill probably be spamming all your vids with comments lol

[@pankajkpathania2664]

Great work :-)

[@mariusmihai8020]

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!

[@Pythoholic]

Thanks a lot for the support. Its the support like this that keeps me going

[@priyaranjan1733]

Thanks, #Subscribed😅 Very good explanation😎

[@nainabhartia9260]

Wonderful explanation.

[@Pythoholic]

Thank u naina

[@fellifel147]

Superb video, please which animatio/graphic tool have u used for presentation? I need this to do a small presentation at work 🙏🏾

[@Pythoholic]

hi i use powerpoint thats it

[@sasig268]

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.

[@Pythoholic]

Thanks for the suggestion. I will surely make one.

[@aravindviswanathan6884]

Thanks much sir, yes sir it would be great to have a real chat app developed thorugh websocket API

[@user-zl1wm9pf5r]

thank you!

[@Pythoholic]

You're welcome!

[@ommiesalma240]

Hello...how u create these visualization ? from where u source different icons used here ?

[@Pythoholic]

Hi... I purchase the premium icons and design them using illustrator and ppt

[@TKVenu]

super

[@rameshm78]

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?

[@Pythoholic]

Thanks remeshm.. I will surely try and put it out

[@rameshm78]

Dear @@Pythoholic - Does AWS have anything like Azure Application Gateway Ingress controller? Regards Ramesh

[@Pythoholic]

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)​

[@rameshm78]

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

[@Pythoholic]

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.

[@onlythala4865]

Hi ...is this topic for AWS solution architect or for both aws ssa and aws developers??

[@Pythoholic]

It's for Aws SAA C02

[@sainikithd8210]

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?

[@Pythoholic]

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.

[@sainikithd8210]

@@Pythoholic thank you sir got it :)

[@Pythoholic]

@@sainikithd8210 I have changed the order to avoid confusion, :)

[@sainikithd8210]

@@Pythoholic thank you very much sir

[@iamshahleo]

Cool

[@SamruddhaShah]

WebSocket API is bidirectional but we also use bidirectional in rest API like put, delete?

[@Pythoholic]

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

[@SamruddhaShah]

@@Pythoholic got it! Thank you so much

[@shainazmaulavi3883]

Greatttttt

[@rajiv7]

What is that noise in the background? Rest all is just excellent, thanks :)

[@Pythoholic]

Thanks for the feedback.. I have tried to improve in new videos

[@AparnaBL]

Would u be making the chatbot with websocket api please

[@Pythoholic]

I could actually. Do we need it with aws or python is fine?

[@sskabade]

Your content is really helpful. One request can you make some videos on AWS best architecture design patterns

[@Pythoholic]

Thanks for the suggestion. Yes for sure we can do that.

[@sskabade]

@@Pythoholic thank you.

[@arpantiwary]

What sort of questions are expected out of API gateway in terms of associate exam? Pls comment

[@Pythoholic]

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.

[@arpantiwary]

@@Pythoholic thanks a lot for such awesome content and replying to queries instantly. This is really appreciated 😀 please keep making more videos 👍🏻🙏🏻🙏🏻🙏🏻

[@gsuman0210]

Websocket API is stateful. In one of your slides it said Websocket API is stateless

[@Pythoholic]

Is it let me check it. Thanks for the feedback

[@gsuman0210]

@@Pythoholic At 14.40 if I remember

[@Pythoholic]

@@gsuman0210 Thanks I have added a comment and pinned it.

[@kumarsaurabh6256]

So, can we say it's like nginx?

[@Pythoholic]

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.

[@ndmoorthy]

when we expect VPC

[@Pythoholic]

Today we will have the introduction to VPC. Fingers Crossed!

[@ndmoorthy]

may be i mistake route 53 and vpc is same

[@Pythoholic]

Sorry couldnt catch you !

[@ndmoorthy]

@@Pythoholic Thanks for your reply.