#89 — February 22, 2019
— Yes, thanks to serverless, of course :-) This post goes into fantastic detail about a specific use case where thousands of pages need to be tested quickly, why a serverless approach was chosen, and just how quick the end result is.
— Compares the performance of three different architectures running the same HTTP endpoint: using an API Gateway service proxy, containers on AWS Fargate, and serverless with AWS Lambda.
— A brief tour of open source serverless platforms (starting with OpenWhisk) that shows how they quickly began to gravitate around Kubernetes.
— This isn’t just about Cloudflare getting early access to a snazzy new
— A look at what’s involved in using Stripe’s Charge API from PubNub’s Functions platform to process payments in a realtime chat app.
Chandler Mayo (PubNub)
— “This post is a complete guide. That means we are going to create an AWS Lambda in the console first and then move onto using AWS SAM on our local machine to package and deploy the Lambda to AWS.”
— We’ve joined forces with Sanity.io to make it easy to upload and preview videos within their CMS and deliver great video experiences at scale.
— You can configure the latest version of Next.js (a universal framework for React commonly used to introduce server-side rendering to React apps) to generate lambdas for each page and work serverlessly.
— “Forget Lambda and serverless: if you are doing anything at all in AWS besides using it as a fantastically overpriced datacenter, I pretty much guarantee you are deeply locked into IAM.”
— v1.38 might not sound like a particularly interesting version number but the Serverless Framework now includes full WebSockets support now that CloudFormation supports it too.
Yan Cui joins Trek10’s Forrest Brazeal to share best practices for running serverless apps at production scale.