🚀
Serverless Adapter
Install | Usage | Support | Architecture | Credits
Run REST APIs and other web applications using your existing Node.js application framework (Express, Koa, Hapi and Fastify), on top of AWS Lambda, Amazon API Gateway and many other event sources.
This library was a refactored version of @vendia/serverless-express, I created a new way to interact and extend event sources by creating contracts to abstract the integrations between each library layer.
Why you would use this libray instead of @vendia/serverless-express?
- Better APIs to extend library functionality.
- You don't need me to release a new version to integrate with the new event source, you can create an adapter and just call the
addAdaptermethod when building your handler.
- You don't need me to release a new version to integrate with the new event source, you can create an adapter and just call the
- All code can be extended, if you want to modify the current behavior you can.
- This is important because if you find a bug, you can quickly resolve it by extending the class, and then you can submit a PR to fix the bug.
- All code was written in Typescript.
- We have >99% coverage.
Install
Using NPM:
npm install --save @h4ad/serverless-adapter
Using Yarn:
yarn add @h4ad/serverless-adapter
Usage
You can quickly use this library as follows:
import { ServerlessAdapter } from '@h4ad/serverless-adapter';
import { ApiGatewayV2Adapter } from '@h4ad/serverless-adapter/lib/adapters/aws';
import { ExpressFramework } from '@h4ad/serverless-adapter/lib/frameworks/express';
import { DefaultHandler } from '@h4ad/serverless-adapter/lib/handlers/default';
import { PromiseResolver } from '@h4ad/serverless-adapter/lib/resolvers/promise';
import app from './app';
export const handler = ServerlessAdapter.new(app)
.setFramework(new ExpressFramework())
.setHandler(new DefaultHandler())
.setResolver(new PromiseResolver())
.addAdapter(new AlbAdapter())
.addAdapter(new SQSAdapter())
.addAdapter(new SNSAdapter())
.build();
export { handler };
Too fast? Ok, I can explain.
First, you need to create an instance of the builder with ServerlessAdapter.new(app). The variable app is the instance of your framework (Express, Fastify, Koa, etc).
So you need to specify for this library which framework you will use to handle the request with setFramework, you can only use one. If you use express in our backend, use ExpressFramework , see more in support.
Then you specify which handler you will use to interact with the serverless cloud with setHandler, currently we only have one, the DefaultHandler. In the next releases, maybe we will add support for Azure, Huawei and others, for now, you can use this default.
Then you specify with setResolver which resolver you will use to wait for the library to forward the request to your framework, and then get the response back to your cloud. I recommend you use PromiseResolver, it's the most cloud-agnostic resolver.
By now, you've already added the basic abstractions of this library, now, you can add the adapters that will add support for receiving and processing different sources of addAdapter events. In the example I added AlbAdapter, SQSAdapter and SNSAdapter. With these adapters you can connect your lambda to three different event sources and you can add more if you wish.
Finally, we call build which will assemble your handler that you can expose directly to your cloud.
Final thoughts:
- You can set the
frameworkonly once. - You can set the
handleronly once. - You can set the
resolveronly once. - You can have as many
adaptersas you like, use and extend as you wish.
Support
We are in beta, so some adapters may not work as expected, feel free to create an issue or provide feedback on current behavior.
By design we have these contracts that define the layers of the library: Frameworks, Adapters, Resolvers and Handlers.
If you don't know what each thing means, see Architecture.
Currently, we support these frameworks:
- Express by using (ExpressFramework)
- Fastify by using (FastifyFramework)
- Hapi by using (HapiFramework)
- Koa by using (KoaFramework)
We support these event sources:
- AWS
- AWS Load Balancer by using (AlbAdapter)
- AWS Api Gateway V1 by using (ApiGatewayV1Adapter)
- AWS Api Gateway V2 by using (ApiGatewayV2Adapter)
- AWS DynamoDB by using (DynamoDBAdapter)
- AWS Event Bridge / CloudWatch Events by using (EventBridgeAdapter)
- AWS Lambda Edge by using (LambdaEdgeAdapter)
- AWS SNS by using (SNSAdapter)
- AWS SQS by using (SQSAdapter)
- Azure
- The support is coming soon.
- Huawei
- The support is coming soon.
We support these resolvers:
- Promise by using (PromiseResolver)
- Callback by using (CallbackResolver)
- AWS Context by using (AwsContextResolver)
We support these handlers:
- Default by using (DefaultHandler)
Architecture
The main purpose of this library is to allow the developer to add support for any cloud and as many event sources as he wants, without having to create an issue to request the feature or copy the library code because the library doesn't expose good APIs for you to extend its functionality
So I refactored @vendia/serverless-express with 4 layers of abstraction: Framework, Handler, Resolver and Adapter.
The FrameworkContract is responsible for forwarding to IncomingMessage and ServerResponse for your application instance. With this abstraction you can implement any framework you want, they just need to accept both parameters and call end in ServerResponse, so the library knows when to continue and return the response.
The HandlerContract is responsible to get the input from the serverless and then manage to call each layer of abstraction to return a response. With this abstraction, you can implement different ways to receive input from your serverless environment. They usually have the same structure, but if you need to deal with a very different cloud, you can use this abstraction to add support for that cloud.
Handler is a good choice for implementing (
monsters) ways to receive input. For example, we can create an http server as its handler to test our serverless code without having to launch the framework. Because? I don't know, but you can.
The ResolverContract is responsible for waiting for the framework to handle the request and then returning the response to the cloud. Using AWS for example, you have three ways to wait for the response: returning a promise, calling the callback, and using in-context methods, each option has its own benefits, but generally the promise option will be the better because any good cloud provider will support promises.
Finally, the masterpiece of this library, the AdapterContract is responsible for handling the received event, transforming the request in a way that your application can understand and then transforming the response in a way your cloud can understand.
Well, with these four contracts, you'll be able to add support to any cloud that exists (no more excuses not to use cloud X with NodeJS).
Why you create this library?
The real reason I created this library was because I wanted to add API Gateway and SQS support at the same time to save some money. But, @vendia/serverless-express was not supported, so I created a PR, but until I finished this library, that PR was never accepted.
So I build my own library based on that library with better APIs so I never have to wait for the maintainer to accept my PR just to extend the library's functionality :)
Credits
Honestly, I just refactored all the code that the @vendia team and many other contributors wrote, thanks so much to them for existing and giving us a brilliant library that is the core of my current company.
"TrpcContext"">
6 Apr 8, 2022
120 Dec 23, 2022
1 Jan 3, 2022
3 Jun 28, 2022
116 Dec 15, 2022
7 Jul 19, 2022
20 Nov 7, 2022
89 Jan 3, 2023
5 Aug 23, 2022
7 Jun 27, 2022
17 Nov 23, 2022
35 Dec 17, 2022
4 Dec 18, 2022
16 Nov 18, 2022
12 Oct 28, 2022
301 Jan 1, 2023
5 Nov 25, 2022
19 Dec 28, 2022