Hi, everyone, and welcome back.
Now, in today's video, we are going to compare the rest APIs versus the HTTP APIs in API Gateway.
Now, before we understand more in detail about this, let's quickly look into where do we find these
now in the API Gateway service, Whenever you create an API, there are multiple different types of
APIs.
The primary ones that are extensively used is the HTTP API and the rest API.
You also have the rest API for private, which is primarily used for accessing it from the VPC.
So in today's video we are going to discuss about the differences between the rest API and the HTTP
API.
Now, at a high level overview, both the rest and the HTTP APIs are the RESTful API products.
However, the major difference between both of them is that the rest API support more features than
the HTTP APIs, while the HTTP APIs are designed with minimal features so that they can be offered at
a lower price.
So if you want to create a very simple API which is also cheaper, you can use the HTTP API.
However, generally for production environments raised, APIs are generally recommended.
Now when we discuss about which one you should choose your, you should note that you need to choose
the rest APIs.
If you need wide set of features for production environments such as API keys, the client throttling
the valve integration request validation, the private API endpoints and so on.
And you can choose the HTTP APIs if you do not need these features that are included with the rest API.
So if you want to keep it simple, use HTTP APIs.
If you want more flexibility, which is generally the requirement in production environments, then
choose rest APIs.
Now let's also quickly look into the differences.
Now, again, you don't really need to remember each and every difference, but at the overview it is
important that we understand things.
For example, one of the core differences related to security, if you look into the Rest API, you
have the mutual TLS authentication, the certificate for backend authentication as well as the valve
integration.
However, HTTP API is limited to TLS discussing about the overall API management.
The rest API supports a lot of features as we're discussing related to throttling rate limiting API
keys, which the HTTP API does not provide.
Similarly, monitoring as well.
Rest API has a lot of features related to x ray tracing, execution logs and so on.
Apart from that, when we discuss about the endpoint type, again, HTTP API only works at a regional
level for Rest API, you have much more better endpoints related to edge optimized as well as private.
And when we discuss about development, the Rest API provides a lot of other features related to caching,
the canary release deployments, request validation, and others.
Now, in fact, let me also quickly show you this.
So I have two APIs that are available.
One is based on the HTTP and second one is based on rest.
So let's quickly open up both of them to understand.
Now, if you look into the HTTP API endpoint, there are very limited features that you see.
In fact, it hardly has any features that are available.
However, when we discuss about the Rest API, you have a lot of features, so you have resources,
stages, authorizers, you have resource policies, you have usage plans, client certificates, API
keys and so on.
So in fact, if you look into the overall dashboard, you can also quickly test, you can add certain
set of authentication at the API level.
So a lot of configurations you will be doing at the rest API level.
Great.
So I hope with this at a very high level overview, you understood the differences between the rest
API and the HTTP API, and with this will conclude today's video.