01. When should I use serverless?

In this episode Eoin and Luciano talk about what it means to adopt serverless, when you should use AWS Lambda, and when you should not use serverless.
The show is also available as a podcast:
- Spotify: open.spotify.com/show/3Lh7Pzq...
- Google: podcasts.google.com/feed/aHR0...
- Breaker: www.breaker.audio/aws-bites
- RSS: ​​anchor.fm/s/6a3312a0/podcast/rss
Do you have any AWS questions you would like us to address?
Leave a comment here or connect with us on Twitter:
- / eoins
- / loige
#aws #serverless #podcast

[@LiranTal]

"Serverless is more about business value than servers" - I like that

[@TheSimoyw]

Great! really liked it 👍👍

[@Loige]

Thank you, Simone. We look forward to knowing if you will enjoy the next episodes too. Keep us posted ☺️

[@rishabhsethi29]

Great discussion.
Just a suggestion: You should add hash tags to the video and make content available for similar searches.

[@AWSBites]

Thanks for the tip!

[@loupax]

Most of the time using DynamoDB will give you the most value for money, even if nothing else is serverless in your stack 😄

[@LiranTal]

IMO another "why not use serverless" is when the technological and organizational readiness isn't mature for that. Serverless is great, but it is a lot of moving parts and overhead which could be overwhelming for teams to take on.

[@AWSBites]

That is a really good point. Any technological decision as an impact on the organisation, so it's definitely important to make sure the organisation is ready for serverless. One good thing about serverless (and FaaS in particular) is that you can start very small, just a Lambda or two to get the feeling of how does that look like and how it fits the organisation.