Which best practice of the AWS Well-Architected Framework is the company following with this plan?
Integrate functional testing as part of AWS deployment.
Use automation to deploy changes.
Deploy the application to multiple locations.
Implement loosely coupled dependencies.
Explanations:
Integrating functional testing as part of AWS deployment focuses on ensuring the functionality of the application after deployment. While important, this practice does not specifically address the migration to microservices or the benefits gained from that architecture.
Using automation to deploy changes is a good practice for CI/CD pipelines, but it does not directly relate to breaking down a monolithic application into microservices. It mainly enhances deployment efficiency rather than addressing application architecture.
Deploying the application to multiple locations refers to high availability and fault tolerance. While beneficial for scalability, it does not directly relate to the process of breaking a monolithic application into microservices.
Implementing loosely coupled dependencies is a key characteristic of microservices architecture. This approach allows individual services to be developed, deployed, and scaled independently, facilitating easier maintenance and scalability compared to a monolithic application.
I guess:
Implement loosely coupled dependencies.
I chart that the answer is:
Implement loosely coupled dependencies.