You have a periodic Image analysis application that gets some files In Input analyzes them and tor each file
writes some data in output to a ten file the number of files in input per day is high and concentrated in a few
hours of the day.
Currently you have a server on EC2 with a large EBS volume that hosts the input data and the results it takes
almost 20 hours per day to complete the process.
What services could be used to reduce the elaboration time and improve the availability of the solution?
A.
S3 to store I/O files. SQS to distribute elaboration commands to a group of hosts working in parallel. Auto
scaling to dynamically size the group of hosts depending on the length of the SQS queue
B.
EBS with Provisioned IOPS (PIOPS) to store I/O files. SNS to distribute elaboration commands to a group
of hosts working in parallel Auto Scaling to dynamically size the group of hosts depending on the number of
SNS notifications
C.
S3 to store I/O files, SNS to distribute evaporation commands to a group of hosts working in parallel. Auto
scaling to dynamically size the group of hosts depending on the number of SNS notifications
D.
EBS with Provisioned IOPS (PIOPS) to store I/O files SQS to distribute elaboration commands to a group of
hosts working in parallel Auto Scaling to dynamically size the group ot hosts depending on the length of the
SQS queue.
Explanation:
Amazon EBS allows you to create storage volumes and attach them to Amazon EC2 instances. Once attached,
you can create a file system on top of these volumes, run a database, or use them in any other way you would
use a block device. Amazon EBS volumes are placed in a specific Availability Zone, where they are
automatically replicated to protect you from the failure of a single component.
Amazon EBS provides three volume types: General Purpose (SSD), Provisioned IOPS (SSD), and Magnetic.
The three volume types differ in performance characteristics and cost, so you can choose the right storage
performance and price for the needs of your applications. All EBS volume types offer the same durable
snapshot capabilities and are designed for 99.999% availability.
Only A: make sense.
A
A and D are quite similar and the difference is where/how to store the input file, cheap S3 or expensive but quicker EBS.
Since the Q is after “reduce the elaboration time” without mentioning cost, I will go for D
With EBS attached to a single EC2 instance you are stuck with a single point of failure – i.e. the EC2 server to which the EBS is attached. Besides, in that case, the SQS worker hosts will have to get the files FROM this EC2 server to process. (D) is a bad combination of EBS hosted on EC2 and external SQS workers.
I’d go with (A) which provides distributed HA storage and on-demand processing using SQS workers.
Yes, D is the option, notice only few large files to process . EBS is ideal
Where does it say few large files? It says input is high but only during a few hours.
D will not improve the availability.
A