A company needs an AWS design solution for a distributed system. The system's components need to be set up so that one system component cannot negatively impact another component.
Which AWS architectural best practice will meet this requirement?
D. Implement loose coupling
Implementing loose coupling is an architectural best practice that helps to prevent one system component from negatively impacting another component. Loose coupling is achieved by designing the system so that each component is independent of the others and only communicates with them through a well-defined interface. This allows changes to be made to one component without affecting the others, and also allows the system to be more resilient to failures. When components are loosely coupled, it's easier to scale, maintain, and update the system, as well as to troubleshoot issues.
Use request throttling is a technique to control the rate of incoming requests to a service, avoiding overloading it, but it does not prevent one component from impacting another.
A stateful service is one that maintains state information across requests, which could cause issues if not properly managed.
Implementing automatic data backups is a security best practice, but it doesn't prevent one component from impacting another.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Pranava_GCP
1 year, 10 months agoAxek
2 years, 2 months agoWsummerspring
1 year, 9 months agoSaif93
2 years, 4 months agoNotMeAnyWay
2 years, 4 months agoacts268
2 years, 4 months ago