Search for a command to run...
Testing serverless isn't hard. Testing serverless well is a different story. After years of building Lambda-based systems, I've seen the full spectrum: no tests at all, tests that mock everything and
If you don't know yet, I have a book published about serverless, and this weekend, I got a message from a reader. He'd been looking at From Zero to Production with AWS Lambda and had a sharp observati
Yes, this is a serverless blog and obviously the main objective here is to spread the serverless word, and make people feel more comfortable to use it. But still, we are talking about technology, and
Every Lambda test starts the same way: you need an event object — and crafting one is annoying. API Gateway v2 events have 30+ fields, SQS needs message IDs, receipt handles, and ARNs, and DynamoDB St
Serverless promises to free teams from infrastructure worries, but picking the wrong database can hurt your performance, increase your costs, and affect developer velocity. As with everything in softw
You might have created a Lambda function that "handles events." But take a moment to question yourself about what an event actually is. Let's forget the object that you can access on the lambda, and t
In recent interviews, I asked candidates a system-design question about managing failures in a serverless, event-driven architecture. I was surprised by how many didn't include retry mechanisms or a D
I've been building with serverless since 2021. Not just tinkering — using it as the primary architectural choice for production systems, advocating for it in hiring conversations, writing about it, gi
