Tweet This is part 2 of a multipart series that explores ideas on how we could apply the principles of chaos engineering to serverless architectures built around Lambda functions. part 1: how can we apply principles of chaos engineering to Lambda? part 2: latency injection for APIs part 3: fault injection for Lambda functions The

Tweet This is the first of a multipart series that explores ideas on how we could apply the principles of chaos engineering to serverless architectures built around Lambda functions. part 1: how can we apply principles of chaos engineering to Lambda? part 2: latency injection for APIs part 3: fault injection for Lambda functions There’s

Tweet Gotta clean up those old Lambda deployment packages! With AWS Lambda and the Serverless framework, deploying your code has become so simple and frictionless. As you move more and more of your architecture to run on Lambda, you might find that, in addition to getting things done faster you are also deploying your code more frequently. That’s awesome!

. . . it's interesting to see the number of efforts to build new languages on old vm's . . .

Tweet AWS Lambda announced native support for environment variables at the end of 2016. But even before that, the Serverless framework had supported environment variables and I was using them happily as me and my team at the time migrated our monolithic Node.js backend to serverless. However, as our architecture expanded we found several drawbacks with managing configurations with environment