A core tenet for #AWS has always been that, if it was possible to take care of scaling, resilience, availability, security, and cost management of our customer's infrastructure components, we should do so. Eventually, this became known as "serverless", which encompasses much more than executing code without the need for servers. Amazon SQS and S3 were the first AWS services launched, and they were "serverless" from day one. A good example of this philosophy in practice is Aurora Serverless, which provides on-demand auto-scaling for Amazon Aurora databases. It proactively scales up resources during peak periods to ensure the predictable performance when you require it. When demand subsides, it seamlessly scales back down, reducing waste. And with granular, second-by-second billing, you can truly optimize for cost. Remember, the essence of frugal architecture is robust monitoring driving the ability to optimize costs. To dive deeper into how Aurora Serverless exemplifies this principle, I recommend reading the latest paper here: https://lnkd.in/e4uPK6wv #AWS #serverless #databases
Had to think of Corey Quinn’s take on Aurora Serverless: https://www.lastweekinaws.com/blog/no-aws-aurora-serverless-v2-is-not-serverless/ Is it still serverless if you pay for the service even it is not in use?
This is very interesting and a great read, thank you. I think there was tremendous progress made on serverless to ease scaling, resilience and availability. The only aspect I see still a bit "cumbersome" today is the broader Multi-Region scaling, resilience and availability. This is often still more of a manual created architecture with many things to consider by the customers themselves. I think in the future there could be more of that "taken care of".
Great work from the AWS team! https://www.amazon.science/publications/resource-management-in-aurora-serverless
AWS’s serverless solutions, like Aurora Serverless, offer significant benefits, including: 💰 Cost Savings 📈 Scalability However, I've seen people getting scared of the following two things: 👉 Learning Curve 👉 Vendor Lock-In Trust me! When you weigh these factors carefully against the long-term benefits, you yourself will notice that you have saved a lot and in fact it is not that complex to learn the things and train the teams!
Remember, the essence of frugal architecture is robust monitoring driving the ability to optimize costs.
Your forward-thinking approach and dedication to optimizing infrastructure for scaling, resilience, and cost management is truly admirable, Werner Vogels.
Thanks for sharing Werner Vogels. I'd also add that Amazon's principles on "frugal" architecture also helps reduce the carbon impact of cloud - which is becoming a critical issue as we enter the age of AI. #wellarchitected #doublebottomline
Aurora Serverless is a great example and i really love reading this , Werner Vogels......I think that a retail company experiencing seasonal traffic can benefit from Aurora Serverless’s ability to scale resources up and down.
Monitoring CloudFront is far from frugal with CloudWatch.
Principal Consultant. Working with stakeholders to develop long term strategies while leading teams to provide solutions that align with those goals.
4moOf all the examples you chose Aurora? You must be after engagement on the post due to controversial opinions. Aurora is widely criticised as one of the not truly serverless products because it doesn't scale down to zero. The cost calculator used to cover the service, but it's since been removed due to how pointless the implementation was. I had to build this to estimate costs for clients: https://www.linkedin.com/pulse/comparing-costs-between-rds-aurora-serverless-v2-joseph-howe/ Shouldn't be difficult to make a service account that pulls Cloudwatch data for RDS to compare & provide that sort of feedback.