AWS has turned running their annual re:Invent conference into a science. The 2020 virtual version will certainly be different from the Las Vegas versions, but they will still be sharing the latest and greatest new functionality for you to build better apps. However, AWS ships so much new stuff every year (and nothing seems to slow them down!) it can be hard to figure out how to consume and synthesize all the information in order scale your modern applications. Never fear! We at Stackery have perfected the art of drinking from the re:Invent firehose and are here to help you!
Everything AWS announced in the week before re:Invent that you might have missed!
Andy Jassy's re:Invent keynote today was chock full of new features and services. I'm here to help break down the most important news related to modern application architecture. If you've read [my first post](https://www.stackery.io/blog/architecting-your-reinvent-experience) about how to consume re:Invent content, you won't be surprised to see below that I'm pointing out news that tell us a larger story about how to ship applications in 2021 and beyond.
Companies across sectors are seeing amazing success adopting modern application architectures, especially with managed services like AWS Lambda, DynamoDB, S3, etc. This week Jessica Feng from AWS gave an excellent re:Invent talk: "Enabling a serverless-first Cloud Center of Excellence." She described common patterns and traits for organizations who have adopted a "serverless-first" mindset to achieve operational and cost management success.
Whether deserved or not (and I lean towards the "not deserved" side), AWS has a reputation in some corners of reaping monetary success off the free and open source contributions of others. The rationale for this argument is that AWS has paid nothing for nor involved the open source community around key projects it relies on when it provides services to customers.
Our team combed through the massive re:Invent schedule to bring you the the most important sessions related to serverless, architecture, and DevOps.
I found lots of information about dead letter queues, but no examples that demoed a redrive function to retry those failed messages. This post is meant to serve as a nice example for folks like me who want to do this on AWS and haven’t found many examples.