What should the solutions architect recommend to improve the customer experience?
Implement retry logic with exponential backoff and irregular variation in the client application. Ensure that the errors are caught and handled with descriptive error messages.
Implement API throttling through a usage plan at the API Gateway level. Ensure that the client application handles code 429 replies without error.
Turn on API caching to enhance responsiveness for the production stage. Run 10-minute load tests. Verify that the cache capacity is appropriate for the workload.
Implement reserved concurrency at the Lambda function level to provide the resources that are needed during sudden increases in traffic.
Explanations:
While retry logic with exponential backoff can help reduce the number of errors, it does not address the root cause of the excessive PUT requests from the client. Descriptive error messages do not improve the experience significantly in this scenario.
Implementing API throttling is an effective way to control the number of requests from a specific client, preventing them from overwhelming the API and reducing errors. Handling code 429 replies appropriately will enhance the customer experience by avoiding confusion.
API caching is not a suitable solution for reducing errors from PUT requests. Caching is more relevant for GET requests to improve performance. Load testing does not address the issue of excessive errors from a specific client.
Reserved concurrency can help manage sudden increases in traffic but does not specifically address the issue of a single client making too many PUT requests. This may not effectively reduce the errors being encountered.
If I’m not mistaken, the answer is:
Implement API throttling through a usage plan at the API Gateway level. Ensure that the client application handles code 429 replies without error.