Recommending and Testing Potential Remediation Solutions

Now that you have clearly identified the potential bottlenecks in your workload, it’s time to devise recommendations to get rid of them. As a solutions architect, you have to devise a rationale for each recommendation that you make. The rationale will typically include a description of the issue, a set of options that you have considered to solve it, and finally, the recommended solution and the reason why you recommend it. Luckily, in most cases, you don’t have to reinvent the wheel, as chances are that the community of solutions architects has already faced similar issues and devised design patterns, and anti-patterns, that you can directly utilize. AWS has collated this collective intelligence, including many best practices, in its Well-Architected Framework for you to leverage as much as you can. AWS also regularly publishes and updates reference architectures and prescriptive guidance to address determined...