This week our superhero is Danielle Heberling
a software engineer at Tango and AWS Community Builder. She is active in the serverless community and a tech blogger
as well. She gave a talk at CDK day last week on her journey from SAM to CDK
. Thank you Danielle for all your contributions to the community!
Serverless log management can be just as difficult as it is important. David Krohn
hooks us up with a way to normalize logs from several services
. Normalizing the logs helps to query using Athena, and offers quick turnaround when digging into an issue.
Whether you’re building a new app from the ground up or have an app that’s been in production a while, it’s never too late to optimize (it might be too early, sometimes). I talk about quick optimizations for serverless applications
that involve much more than changing the memory on your Lambda functions.
Serverless calls for many opportunities for you to decide if you want to use orchestration or choreography
. Sometimes that’s an easy choice, sometimes it can be more difficult. This video from the serverless expeditions
team at Google Cloud talks about the difference between the two and when you should use one or the other.
If you’ve been deciding whether or not it was time to pull the trigger on moving to a multiple-AWS account structure, Tomasz Łakomy
helps us out with his post. He talks about a plethora of organizational benefits to this strategy
including cost optimization, promoting innovation, and minimizing blast radius when things go wrong.
This week we focus more on what to do after you’re started with serverless. Iteration is your key to success. I always say when it comes to software to do it, do it right, do it better. With each iteration you understand the problem domain better and better and will make more educated design decisions to optimize your app.
If you’d like to make a recommendation for the serverless superhero or for an article you found especially useful, send me a message on Twitter
, or email