End the Monolith! Lessons learned adopting Serverless
Stop worrying about serverless costs. Your real problem is the random 500 error you can't diagnose.
#1about 4 minutes
Break down monolithic problems into microservices
Adopt a microservices mindset by breaking down large problems into the smallest possible units, like the minimum marketable feature.
#2about 7 minutes
Prioritizing observability and debugging in serverless
Focus on solving observability and debugging first, as these are often bigger challenges than cost or complexity in a serverless environment.
#3about 5 minutes
Using infrastructure as code and structured logging
Adopt tools for infrastructure as code and structured logging to gain visibility and control over your serverless architecture.
#4about 4 minutes
Why you should grow serverless talent, not hire it
Build a successful serverless team by investing in internal talent through funding, resources, and supportive feedback rather than trying to hire rare experts.
Related jobs
Jobs that call for the skills explored in this talk.
Why Attend a Developer Event?Modern software engineering moves too fast for documentation alone. Attending a world-class event is about shifting from tactical execution to strategic leadership.
Skill Diversification: Break out of your specific tech stack to see how the industry...