So far the most useful comparison I've found between Rest and HTTP. Makes it clear to pick HTTP API unless there is a missing feature but if you can survive without the feature be aware HTTP is the future direction for API Gateway.
I wish you had touched on what makes the REST option inherently heavier/slower. I can imagine that it would be slower if I was using a lot of the bells & whistles, but why would it be slower even without those?
I had a doubt can you help me to solve it.Correct me if I am wrong.only 2 questions 1.I had a assumption that creating endpoints can be done with rest API ,graphql,etc and to communicate with any these api client-server I need to use a transfer protocol which is http. But how we can create endpoints with such transfer protocol http. Http api and http transfer protocol are different or same. 2.Http transfer protocol has the verb commands like Get,post, update, delete.If I don't use these transfer protocol it is possible to create these verb in rest api itself without using http
I had same doubt then I researched and got to know this: yes http is a transfer protocol but here he is talking about http api vs rest api “in API Gateway” which means in api gateway, there are may be two options to create api 1. Using rest and 2. Using http. meaning when we use http api we don’t have to adhere to the principles that REST has specified but we can create simple api without the adherence of any rules or principles unlike rest api approach in API gateway and it is helpful if we have simpler needs but rest api in api gateway offers a comprehensive set of features designed to support RESTful principles. So we can choose any of these two as per our requirements.
Part 2 is here: ua-cam.com/video/M91vXdjve7A/v-deo.html
So far the most useful comparison I've found between Rest and HTTP. Makes it clear to pick HTTP API unless there is a missing feature but if you can survive without the feature be aware HTTP is the future direction for API Gateway.
Sorry, what do you mean by "be aware HTTP is the future address for API Gateway"? thx
Learn how to build a REST API on AWS with API Gateway: ua-cam.com/video/uFsaiEhr1zs/v-deo.html
Very useful. Thanks
I wish you had touched on what makes the REST option inherently heavier/slower. I can imagine that it would be slower if I was using a lot of the bells & whistles, but why would it be slower even without those?
Very good. Can't wait for Part 2
Great content. Thank you for sharing!
You're very welcome Hamed!
Thanks! Would be great a video about appsync vs api gateway, more about subscriptions vs websockets
This is so good!
Excellent! Love it! Thx
I had a doubt can you help me to solve it.Correct me if I am wrong.only 2 questions
1.I had a assumption that creating endpoints can be done with rest API ,graphql,etc and to communicate with any these api client-server I need to use a transfer protocol which is http. But how we can create endpoints with such transfer protocol http. Http api and http transfer protocol are different or same.
2.Http transfer protocol has the verb commands like Get,post, update, delete.If I don't use these transfer protocol it is possible to create these verb in rest api itself without using http
I had same doubt then I researched and got to know this: yes http is a transfer protocol but here he is talking about http api vs rest api “in API Gateway” which means in api gateway, there are may be two options to create api 1. Using rest and 2. Using http. meaning when we use http api we don’t have to adhere to the principles that REST has specified but we can create simple api without the adherence of any rules or principles unlike rest api approach in API gateway and it is helpful if we have simpler needs but rest api in api gateway offers a comprehensive set of features designed to support RESTful principles. So we can choose any of these two as per our requirements.
Ill use it just as soon as it has better support for Lambda
Since HTTP does not support usage plans, how do you prevent someone from DDOS'ing you into bankruptcy?
Hi there, AWS WAF helps with DDoS attacks and is generally the preferred option.
A nice video. Is there any way to allow new binary media types on HTTP API? I'm getting corrupted font files (with woff extension) from AWS HTTP API.
Eventbridge doesn't support aws http api gateway
Also with Grapghql
Please fix your microphone. Way too much bass, can barely hear anything you say.