In this course, we provide insight into how to utilize the AWS global infrastructure to your advantage, allowing you to design for failure.
By the end of this course, you will have a greater understanding of how to design for failure to help with high availability using the AWS global infrastructure, including availability zones and regions.
This course has been primarily created for solution architects, operational engineers, and anyone looking to sit an Associate certification with AWS.
This is an intermediate-level course. To get the most from this course, you should have a general understanding of networking services in AWS in addition to availability zones and regions.
In this course, we looked at the key factors of the AWS global infrastructure when architecting for failure, specifically at the availability zone and Region level. To ensure that our solutions continue to run and operate when a failure occurs, and a failure WILL occur at some point, then you need to ensure you design for this from the outset. Designing for failure will ensure that you and your customers continue to receive great service, and you as a business continue to thrive as a reliable and stable platform delivering solid services.
The level at which you implement your design for failure is largely dependent on your RTO and RPO, the longer these values are the less critical it might be to implement increasing amounts of failure protection. The shorter these values are, the more complexity and resiliency you will need to architect and build into your solutions. Failure doesn’t just occur at the global infrastructure level, we need to be building with failure in mind at every level, from the application running on the host all the way through to the geographical location hosting the resources. Always ask the question in your design, ‘If this component fails, will my application still work?’ If not, then re-architect it if the business deems it critical enough.
That now brings me to the end of this lecture and to the end of this course. You should now have a better understanding of why you should incorporate a ‘design for failure’ approach when it comes to your architectural design patterns. If you have any feedback, positive or negative, please send an e-mail to email@example.com, your feedback is greatly appreciated.
Thank you for your time and good luck with your continued learning of cloud computing. Thank you.
Stuart has been working within the IT industry for two decades covering a huge range of topic areas and technologies, from data center and network infrastructure design, to cloud architecture and implementation.
To date, Stuart has created 150+ courses relating to Cloud reaching over 180,000 students, mostly within the AWS category and with a heavy focus on security and compliance.
Stuart is a member of the AWS Community Builders Program for his contributions towards AWS.
He is AWS certified and accredited in addition to being a published author covering topics across the AWS landscape.
In January 2016 Stuart was awarded ‘Expert of the Year Award 2015’ from Experts Exchange for his knowledge share within cloud services to the community.
Stuart enjoys writing about cloud technologies and you will find many of his articles within our blog pages.