NEW: Lambda FINALLY adds multiconcurrency support with Lambda Managed Instances!

Sandboxes process multiple concurrent requests when deployed into EC2 clusters managed by AWS.

You pick the instances, and you can set the max concurrency per sandbox.

MEANING: No more cold starts! Two major points:

1. Compute costs should be massively improved as you can fully utilize the sandboxes AND instances. This won't replace Lambda on-demand for small scale, but anyone running high-volume Lambda workloads will likely switch over immediately.

Which would you expect would be faster, SNS directly invoking a Lambda function? Or SNS to SQS to a Lambda function?

Here's a fun thread documenting what I've learned!
🧵👇
#Serverless In a totally unscientific test (N=3), I’ve observed SNS messages delivered directly to Lambda functions are slower than an SNS message sent to SQS, then delivered to Lambda.

Check out the following trace:

@fitzsimons_dev @dynamodb Oh! You're one of today's lucky 10,000!

DynamoDB streams are GREAT! I use them in almost every place I use a DDB table with #Serverless. I suggest doing non-essential work via stream vs in one long function call, so the end user gets the fastest experience possible.

Here's a 🧵 @fitzsimons_dev @dynamodb 1. Sending a confirmation email after a user registers.

This is an important function, but users shouldn't have to wait for my API to call an email provider before getting a response from the backend. Stream it to another function!