aws-lambda-web-adapter VS serverless-graphql

In the next part of the series I'll make the introduction to the AWS Lambda Web Adapter and explain how our Serverless Spring Boot application on AWS can make use of it.

Lambda Web Adapter (LWA) is an open-source project that enables running Web apps on Lambda functions without the need to change or adapt the code.

Thanks to the AWS Lambda Web Adapter, the application built as a (good old) REST/HTTP API using a familiar library (in this case, Gin.

Using the excellent Lambda web adapter extension with a container, you can very easily move a function from Lambda to Fargate or Apprunner if cost becomes an issue. This optionality is of high value, and shouldn't be overlooked.

We will use AWS Lambda Web Adapter to run our Node.js Application on AWS Lambda.

For such frameworks, I would look at Lambda Web Adapter (https://github.com/awslabs/aws-lambda-web-adapter/tree/main/examples). Both frameworks have specific examples for them that allow for the execution of those within a Lambda context with few, if any, code changes. For spring, specifically, using Lambda Snapstart can significantly improve cold-start performance. You can read more about Java and Spring framework in this blog post that contains also a code example https://aws.amazon.com/blogs/compute/reducing-java-cold-starts-on-aws-lambda-functions-with-snapstart/ With regards to Flask, you can also use a project like: https://pypi.org/project/flask-lambda/

With the lambda web adapter[1], you shouldn't need to make any code changes for web projects, just some dockerfile changes which are only used if it is running as a lambda, so the same container image should still work on ecs or another cloud. [1]https://github.com/awslabs/aws-lambda-web-adapter

Additionally, there is this tool you can use to use the same image in a lambda and any other container runtime. https://github.com/awslabs/aws-lambda-web-adapter

You can point your platform team to this: https://github.com/awslabs/aws-lambda-web-adapter , which they can use to get your service running in Lambda.

Since then, the ecosystem has changed. Using the Serverless Framework makes deployment simpler. We released the managed Tracetest App making any serverless-based systems simpler to instrument and test. You can now test public-facing apps with no infra overhead!

We see some great results from using these in conjunction with frameworks such as SST or Serverless, and also some real spaghetti from people who organically proliferate 100’s of functions over time and lose track of how they relate to each other or how to update them safely across time and service. Buyer beware!

When we think about AWS serverless service, the first thing that comes to our mind is Lambda function. Yes, the quickest way to deploy this backend Express JS app to AWS is to deploy it as a Lambda function. The easiest way is using Serverless Framework.

Serverless Framework: https://www.serverless.com/

Github | Website

In this example, we're using the serverless framework to quickly set up the Lambda function along with an API gateway for the entry point. The lambda function is a simple Koa REST API with a few functional endpoints.

Naturally, there are several options available to declare your cloud resources. The options with the most popularity are the CDK, AWS CloudFormation, SST, Serverless framework, Terraform, and AWS SAM. There are others, but when talking about Infrastructure as Code (IaC), these are the ones you hear about most often.

1 - Serverless + AWS CDK + Lift: An integration that amps up the traditional Serverless Framework with Lift's static frontend construct and CDK's robust infra definition.

It's a bit easier in Python if you use tools like https://www.serverless.com/. I'm not sure if Rust has something similar yet.

Serverless