Serverless soultions is can be incredibly cheap due to their event-based nature - if your system isn't working, you pay barely anything for it. But if you're not careful, serverless can still result in some nasty surprises when it comes to costs.
Get started with golang and the AWS SAM CLI for local Lambda development.
Understanding the differences between the various event types and their retries is important, because it will change how you design and code your application. If you're developing a serverless application in Lambda, you will have to deal with retries. They
Last week I presented to the Sydney AWS Lambda User Group about serverless operations aka. LessOps. Here are the slides I used to talk about the good - and less good - things about operating a serverless application: Serverless Operations
Now that the Lambda Proxy Integration is a thing for API GW, performing redirects is a much simpler - and more sane - thing to do in your Serverless service. In my own case I was wanting to do a
I've just finished my first Serverless screencast. Check it out and let me know what you think: It's my first screencast, so there's lots of things that I'd like to fix in it. Even so, it was a great learning
I hang out a lot in the Serverless forum and Gitter - I just like talking about this new-fangled FaaS (Functions-as-a-Service) thing. A common misconception that keeps coming up is that it's not an appropriate choice for things that use
I've been really enjoying playing with the Serverless framework recently. The FaaS (Function-as-a-Service) model really appeals to me, and I think it's going to be A Big Deal in the future. The Serverless framework makes interacting with AWS Lambda, API