Though C is not cost-efficient, but solution A with EC2 option, it’s not scalable, is it? How do we tradeoff between these two to decide the better?
If you post the complete question then someone can try answer. The questions typically state what is the problem trying to solve: scalability, security, cost, availability.reliability, speed of implementation, etc
This is a good debatable question and others have debated it on this forum as well. For Option C, we’re specifically using Infrequent Access storage type definitely incorrectly as we fully expect the files to be accessed frequently. Anytime you see in an exam question where a service is not being used in the way AWS thinks you should use it, that’s a good hint that it’s a poor answer. With Option A, there’s nothing really incorrect about it…scalability could be covered by how large of an instance we choose to deploy.
I understand C not being a cost efficient option only because its infrequently access storage option but how would I compare it with option A without knowing the instance type or the traffic .. i mean, how would I be sure of the cost here.
I’m looking at this question from both technical and product lens. Which option will allow me to meet my business objective (i.e. to have successful game launch). This is where architects or engineers are supposed to help. Option A does not do well as firewalls may trip up on this arcane protocol. So folks may have ave trouble getting anything downloaded. They will then flood the client support centre (expensive) or support forums. That’s a fail. Options C is expensive but it will work (transfer over https). Face palm on launch date (option A) would end up costing the company more than option C.
Your instructions say bittorrent is option #1. While this does allow ‘lowered costs’, it also forces users to install a bittorrent client (disguised as a ‘download manager’), and expose their network to bittorrent (inbound and outbound). Many gaming heads and firewall guys will not be happy.
Additionally, you expose the company to risk customers who leave downloads mid-way due to poor p2p connectivity/bandwidth. Most ISPs restrict upload bandwidth.
Customer interaction with your core product should not be compromised, my $0.02.
And how would you separate the paid part of the download in this case. SFTP service looked to be the best bet to me.
Thanks for this!