You have been asked to leverage Amazon VPC BC2 and SOS to implement an application that submits and
receives millions of messages per second to a message queue. You want to ensure your application has
sufficient bandwidth between your EC2 instances and SQS
Which option will provide the most scalable solution for communicating between the application and SQS?
A.
Ensure the application instances are properly configured with an Elastic Load Balancer
B.
Ensure the application instances are launched in private subnets with the EBS-optimized option enabled
C.
Ensure the application instances are launched in public subnets with the associate-public-IP-address=true
option enabled
D.
Launch application instances in private subnets with an Auto Scaling group and Auto Scaling triggers
configured to watch the SQS queue size
Explanation:
http://www.cardinalpath.com/autoscaling-your-website-with-amazon-web-services-part-2/
Hi, I would go for D.
The question is about most “scalable solution for communicating” for SQS that is parallel processing of SQS messages.
See also:
– https://aws.amazon.com/articles/1464
– http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/throughput.html
Thanks,
Frank
1
0
I agree with Frank. Doesn’t seem like Answer B is really an option in terms of scalability.
1
0
Yeap, D makes more sense … will someone update this question?
1
0
I go with D.
We can set the Auto-scaling based on the message queue size.
1
0
I think both answer B(sufficient bandwidth) and D(scalable solution) are correct.
I will go with D if I do not think out-of-box. Because the question is to leverage with Amazon VPC EC2 and SQS and no ELB or autoscaling, even SQS is scalable by default.
0
0
Sorry, I will go with B.
0
0
B (keyword Bandwidth)
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSOptimized.html
1
0
b
0
0
d
0
0
B
0
0
D.. Makes more sense.. Bandwidth literally means network not IO Bandwidth.. Having alerts to scale the Autoscaling is most sophisticated option.
0
0
D
0
0
WHen I read https://aws.amazon.com/blogs/aws/scaling-with-amazon-sqs/ then I go for D because as I may quote: “The throughput scales horizontally, so the more threads and hosts you add, the higher the throughput “
2
0
D, of course
0
0