You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Want to get up and running quickly? [Check out our basic starter example](examples/basic-starter) which includes:
29
30
30
-
- Lambda function
31
-
- Express server
32
-
[Swagger file](http://swagger.io/specification/)
33
-
-[Serverless Application Model (SAM)](https://github.com/awslabs/serverless-application-model)/[CloudFormation](https://aws.amazon.com/cloudformation/aws-cloudformation-templates/) template
34
-
- Helper scripts to configure, deploy, and manage your application
31
+
- Lambda function
32
+
- Express server [Swagger file](http://swagger.io/specification/)
33
+
-[Serverless Application Model (SAM)](https://github.com/awslabs/serverless-application-model)/[CloudFormation](https://aws.amazon.com/cloudformation/aws-cloudformation-templates/) template
34
+
- Helper scripts to configure, deploy, and manage your application
35
35
36
36
### Getting the API Gateway event object
37
+
37
38
This package includes middleware to easily get the event object Lambda receives from API Gateway
38
39
39
40
```js
@@ -44,25 +45,36 @@ app.get('/', (req, res) => {
44
45
})
45
46
```
46
47
48
+
## 4.0.0 Goals
49
+
50
+
1. Improved API - Simpler for end user to use and configure; extensible without breaking backwards compatibility or hurting API
51
+
1. Node.js 8+ only - can upgrade dependencies to latest (Jest); can use latest syntax in source and tests; can use server.listening; future-proof for Node.js 10
52
+
1. Promise resolution mode by default? Requires benchmarking. Otherwise try callback with callbackWaitsForEventLoop=false (configurable by user); requires benchmarking. If context.succeed is still most performant, leave as default.
53
+
1. Additional event sources - currently only supports API Gateway Proxy; should also support Lambda@Edge (https://github.com/awslabs/aws-serverless-express/issues/152) and ALB; have had a customer request for DynamoDB; should make it easy to provide your own IO mapping function.
54
+
1. Multiple header values - can get rid of set-cookie hack
55
+
1. Configure logging - NONE, ERROR, INFO, DEBUG; also include option to respond to 500s with the stack trace instead of empty string currently
56
+
1. Improved documentation
57
+
1. Option to strip base path for custom domains (https://github.com/awslabs/aws-serverless-express/issues/86)
- For apps that may not see traffic for several minutes at a time, you could see [cold starts](https://aws.amazon.com/blogs/compute/container-reuse-in-lambda/)
66
-
- Cannot use native libraries (aka [Addons](https://nodejs.org/api/addons.html)) unless you package your app on an EC2 machine running Amazon Linux
67
-
- Stateless only
68
-
- API Gateway has a timeout of 30 seconds, and Lambda has a maximum execution time of 15 minutes.
77
+
- For apps that may not see traffic for several minutes at a time, you could see [cold starts](https://aws.amazon.com/blogs/compute/container-reuse-in-lambda/)
78
+
- Cannot use native libraries (aka [Addons](https://nodejs.org/api/addons.html)) unless you package your app on an EC2 machine running Amazon Linux
79
+
- Stateless only
80
+
- API Gateway has a timeout of 30 seconds, and Lambda has a maximum execution time of 15 minutes.
0 commit comments