REST APIs

We also have experience creating what is known as Async API Gateway APIs which leverage AWS API Gateway REST APIs, but instead of an AWS Lambda function processing the request and following a request/response architecture where the client or frontend application is waiting for the request to process and return.

We will put SQS (Simple Queue Service) or leverage aWe help clients build serverless REST APIs by leveraging AWS API Gateway which is a fully managed service by AWS. We have an entire deep dive course on the topic which has over 800 students. The combination of our IAC (Infrastructure as Code) experience coupled with our deep application development knowledge means we can stand up REST APIs quickly.Behind our AWS API Gateway REST APIs we will configure either service proxies to skip over some application code, reducing development time and overhead or we will setup AWS Lambda functions written in NodeJS or Python which will accept the request coming in and process accordingly.n AWS DynamoDB stream behind our API and immediately respond to the client or frontend application, then our queue or database stream will invoke an AWS Lambda function to process the request and store the result in our database.

The client or frontend application will listen for changes in our AWS DynamoDB table and when that change takes place it will immediately update the users view. By in large, this is a much better experience for the user because they don't have to wait for the request to finish and respond. While the request is processing they can continue using the client or frontend application and see the result of the processed request propagate in real-time without refreshing the browser.

This kind of architecture can be setup with both AWS API Gateway REST APIs and AWS AppSync for GraphQL APIs.

Recently AWS came out with a new slimmed down version of AWS API Gateway which aimed to decrease complexity thus increasing developer productivity.

Our team has worked with clients to help build AWS API Gateway HTTP APIs or AWS API Gateway V2 APIs as well as migrate from AWS API Gateway V1 (AWS API Gateway REST APIs) to AWS API Gateway V2. Here is a link to an article we wrote about the migration process.

There are a lot of caveats that you need to be aware of when building AWS API Gateway HTTP APIs. Some are with the vocabulary differences and feature support, but a lot of them are hidden.

These hidden caveats are when it comes to automating the deployment of HTTP APIs where IAC (Infrastructure as Code) support can often be lacking from using AWS API Gateway REST APIs or v1 which is often considered the backbone of serverless applications on AWS because of how long it’s been released and the support from IAC (Infrastructure as Code) frameworks like the Serverless Framework.