Echo JS 0.11.0

<~>
xat 2207 days ago. link 4 points ▲ ▼
Before switching to AWS Lambda keep a few things in mind:

* A lambda function has a maximal execution timeout of 5 minutes
* API Gateway has a timeout of 30 seconds for incoming requests
* Because of those limits you probably won't be able to use Websockets
* You are totally binding yourself to Amazon services
* If your app has periods where it doesn't get much incoming traffic then cold starts might become a problem

If all that isn't a problem for you and your app has that much traffic, then go for it ;)

Replies

user90210 2206 days ago. link 2 points ▲ ▼
WebSockets are not meant to be used with AWS Lambda. It's not one of the problems that Lambda addresses.

Can you please elaborate on "You are totally binding yourself to AWS"?
xat 2206 days ago. link 2 points ▲ ▼
I just mean that by optimizing your app for AWS Lambda and using surrounding services like DynamoDB, S3, API Gateway, etc. it can/may be hard to later on move your app to some other platform.

For example, if you would instead split your app up in multiple docker containers, using open source technologies like expressjs, postgres and ngnix, it should be quite easy (or at least easier) to move your app to another platform which supports containers.

To be clear, I'm not saying that you shouldn't use AWS Lambda at all, just don't blindly follow the hype and carefully evaluate if it solves a problem you're having.