The web app i'm working on downloads mp3's from a separate source and provides them to the users. I'm worried this won't scale, since given a ton of users making requests for mp3's, my server has to download each of mp3 from the separate source before they are available for download by the users. Am i underestimating the performance of modern hosting services like AWS? Obviously I'd like to avoid the latency of the "extra" download, but rewriting that code in javascript is daunting to me so if its feasible I'd like avoid it for now.
Conceptually its similar to those youtube-to-mp3 websites. Do those work by having the client machines directly download and convert the files from youtube? Or do their servers download the files and do all the work before uploading them to the client?
Aucun commentaire:
Enregistrer un commentaire