An organization developed serverless applications by using an event driven architecture (Amazon API Gateway, AWS Lambda). When launched in production, customers complained about slow response during the morning peak hours. Developers pointed out it is related to AWS Lambda cold starts. On average, the development team estimated there will be 100 concurrent users.How do you mitigate the AWS Lambda cold starts?Prevent AWS Lambda cold starts by increasing the service limits.Prevent AWS Lambda cold start with the Amazon CloudWatch Metrics to schedule events on morning hours.Prevent AWS Lambda cold starts with Lambda provisioned concurrency.Prevent AWS Lambda cold starts with Lambda reserved concurrency.
Question
An organization developed serverless applications by using an event driven architecture (Amazon API Gateway, AWS Lambda). When launched in production, customers complained about slow response during the morning peak hours. Developers pointed out it is related to AWS Lambda cold starts. On average, the development team estimated there will be 100 concurrent users.How do you mitigate the AWS Lambda cold starts?Prevent AWS Lambda cold starts by increasing the service limits.Prevent AWS Lambda cold start with the Amazon CloudWatch Metrics to schedule events on morning hours.Prevent AWS Lambda cold starts with Lambda provisioned concurrency.Prevent AWS Lambda cold starts with Lambda reserved concurrency.
Solution
To mitigate AWS Lambda cold starts, you can use the following strategies:
-
Increase Service Limits: AWS sets default limits on resources which can sometimes limit the performance of your applications. You can request an increase in these limits to allow for more concurrent executions.
-
Use Amazon CloudWatch Metrics: You can use CloudWatch to schedule events during peak hours. This will keep your Lambda functions warm and ready to respond quickly to requests.
-
Use Lambda Provisioned Concurrency: This feature allows you to set the number of instances that are always ready to respond to invocations. By setting a provisioned concurrency, you can ensure that there are always a certain number of warm instances ready to handle requests.
-
Use Lambda Reserved Concurrency: This feature allows you to reserve a portion of your account level concurrency limit for specific functions. This ensures that these functions will always have the necessary resources to execute quickly.
Remember, each of these strategies has its own costs and benefits, so you should choose the one that best fits your specific use case.
Similar Questions
A company will be modernizing their application which is currently running on Amazon Elastic Cloud Compute (EC2) instances. They have experience with scaling this infrastructure using Amazon EC2 Autoscaling. They want to move to serverless infrastructure consisting of an Amazon API Gateway that triggers Lambda functions. They are consulting you about scaling this new infrastructure.What should the company consider in order to make sure the serverless infrastructure scales to their needs?Throttle Lambda functions by configuring reserved concurrency, sending the excess traffic to Dead Letter Queues (DLQ) that will be handled when the request volume reduces.Look at service limits for Amazon API Gateway and Lambda functions used in order to identify potential bottlenecks and balance performance requirements, costs, and business impactEnable Auto Scaling Groups for AWS Lambda to ensure that enough Lambda functions are ready to handle the incoming requestsDo nothing. API Gateway and AWS Lambda are managed services that have built-in horizontal scaling, security, and high availability to handle unlimited amount of requests
You are consulting for a company that promotes large musical events. They are going to announce a concert of a well known artist and expect a 10 fold increase in requests to their service. The service is based on API Gateway triggering a series of Lambda functions and an Amazon Relational Database Service (Amazon RDS) Database for persistent storage.What suggestions would you make for cost effective scaling?Set Lambda provisioned concurrency to a value that meets your cost targetEnable API Gateway caching to reduce backend invocationsScale the Amazon RDS instance up during the peak request periodUse API Keys to rate limit incoming user requests
Your company has a serverless application with Amazon API Gateway and AWS Lambda having both read, as well as, write APIs. The developers make frequent changes to the Lambda code and run load tests on the application after every change. The regular load testing has resulted in a spike in the cost.What are the best practices and cost savings options available on their Lambda compute usage? (Select TWO)Changing Lambda code does not necessarily require load testing. Unit and integration tests are sufficient.User reserve concurrency for the lambda functions and set the concurrency to a lower value.Use compute savings plan for lambda (discounted Savings Plans rates of up to 17% for a 1 or 3 year term, up to the commitment level.)Use Amazon EC2 instead of lambda.Use caching on Amazon API Gateway.
As a Solution Architect working for an online gaming company, you have been informed the player feedback system is slow to respond during peak periods. The feedback is reviewed weekly by the game developers. The current system submits the feedback to an Amazon API Gateway which invokes a Lambda function to first validate and then store the review in a Amazon DynamoDB table. This table has been configured with provisioned capacity.What suggestion would you offer to remove the players wait time?Enable API caching and payload compression in Amazon API GatewayIncrease the Lambda functions memory configuration so that it can process each client request faster.Change Amazon DynamoDB from provisioned capacity to on-demand allowing the table to scale up to handle any increases in demand.Insert an Amazon Simple Queue Service queue between the API Gateway and Lambda function. Use Lambda's native SQS poller to read off the queue. Refactor the Lambda function to handle the new event object.
weather-tracking application is built using Amazon DynamoDB. The performance of the application has been consistently good. But lately, the team has realized that during holidays and travel seasons, the load on the application is high and the read requests consume most of the database resources, thereby drastically increasing the overall application latency. Which feature/service will help resolve this issue?Question 63Answera.Amazon CloudFrontb.Amazon DynamoDB Acceleratorc.Amazon DynamoDB Regulatord.Amazon ElastiCache
Upgrade your grade with Knowee
Get personalized homework help. Review tough concepts in more detail, or go deeper into your topic by exploring other relevant questions.