The 5 pillars of the AWS Architecture Framework

Recently I published an article about the Twelve Factor App Methodology for SAAS, which can be applied for any programming language.

In case you decide to go with you can complement the methodology with AWS Architecture Framework, which provides you with a solid architectural foundation for building these new kind of applications. The white paper got recently updated (November 2016) an addresses general design principles, as well as specific best practices and guidance in five conceptual areas that AWS defines as the pillars of the Well-Architected Framework.

  1. Security: The ability to protect information, systems, and assets while delivering business value through risk assessments and mitigation strategies.
  2. Reliability: The ability of a system to recover from infrastructure or service failures, dynamically acquire computing resources to meet demand, and mitigate disruptions such as misconfigurations or transient network issues.
  3. Performance Efficiency: The ability to use computing resources efficiently to meet system requirements, and to maintain that efficiency as demand changes and technologies evolve.
  4. Cost Optimization: The ability to avoid or eliminate unneeded cost or suboptimal resources.
  5. Operational Excellence: The ability to run and monitor systems to deliver business value and to continually improve supporting processes and procedures.

When architecting solutions you make trade-offs between pillars based upon your business context, these business decisions can drive your engineering priorities.

The paper will help you to make the right decisions in context of application requirements and is a guiding light in the sometimes complex AWS ecosystems

You can find the full white paper: Here.

Update 2.12.2016: Werner Vogels CTO of Amazon AWS is providing an introduction to the topic, you can find his page here.

My articles to the usage of the Amazon cloud you will find under the tag aws.

This blog entry was fully produced within Evernote and published using the Cloudburo Publishing Bot.

comments powered by Disqus