An organization has a serverless API hosted on Amazon API Gateway that routes requests to an AWS Lambda function. The function queries an Amazon DynamoDB table to retrieve static configuration metadata that changes only once a day. Due to a sudden surge in traffic, the application is experiencing high latency and increased DynamoDB costs. The developer wants to implement a caching strategy to reduce latency and database reads with the least operational overhead and no code changes. Which of the following is the most suitable solution?
- Enable caching on the Amazon API Gateway stage for the GET method.Answer
- BIncrease the provisioned Read Capacity Units (RCUs) on the DynamoDB table and use strongly consistent reads for all configuration queries.
- CModify the AWS Lambda function code to perform a DynamoDB Scan operation to fetch the configuration metadata on every invocation.
- DMigrate the configuration metadata to AWS Secrets Manager and configure the Lambda function to fetch the secret on each execution.
Answer
Enable caching on the Amazon API Gateway stage for the GET method.
Enabling caching on the API Gateway stage allows the API Gateway to return cached responses directly to the client for the specified Time-to-Live (TTL). This bypasses the Lambda function invocation and subsequent DynamoDB queries entirely, reducing both latency and costs without requiring any modification to the application code.
Step-by-Step Solution
Key Concept
API Gateway Caching