How well-architected enables junior engineers

Click for: original source

Well-architected describes the key concepts, design principles and architecture best practices for designing your cloud workloads. It balances best practices with business goals to determine the optimal outcome. By Gerald Stewart.

Created by AWS Solutions Architects using the lessons Amazon has learnt from running thousands of systems at a massive scale, it enables developers to compare their workloads against the rigorous standards that AWS holds itself against.

The framework covers these pillars:

  • Operational Excellence - To be able to monitor and support workloads effectively, to enable continuous improvement and to deliver business value
  • Security - Improving your security posture by taking advantage of Cloud technologies to protect your assets and systems
  • Reliability - Ensuring your workload can perform it’s intended function correctly and consistently
  • Performance Efficiency - Ensuring appropriate resource allocation to enable performant systems and a positive end user experience
  • Cost Optimisation - Ensuring you are delivering business value at the lowest possible cost

If I could recommend one topic of learning to a junior engineer or someone looking to up their game designing and building on AWS it would be to read the Well-Architected framework and understand how to apply it.

Well-Architected should be applied both continuously with reviews carried out at regular intervals. Understanding the pillars, core concepts and reasons behind the pillars of the Well-Architected framework can enable you to make better architecture decisions and avoid rewrites or large changes after a full-scale review has been carried out. For deeper insights follow the link to the full article. Good read!

[Read More]

Tags frameworks app-development programming agile aws serverless