Joined April 2013
·
Posted to
Nginx as proxy for Amazon S3
over 1 year
ago
Doesn't this mean that you have reduced/removed the scalability or CDN features of S3? Since all requests now go through the nginx server. You are effectively using S3 to store the files, then piping them through this nginx server.
Achievements
192 Karma
3,649 Total ProTip Views
Forked 20
Have an established project that's been forked at least 20 times
Lemmings 100
Write something great enough to have at least 100 watchers of the project
Walrus
The walrus is no stranger to variety. Use at least 4 different languages throughout all your repos
Altruist
Increase developer well-being by sharing at least 20 open source projects
Forked
Have a project valued enough to be forked by someone else
Charity
Fork and commit to someone's open source project in need
Python 3
Have at least three original repos where Python is the dominant language
Python
Would you expect anything less? Have at least one original repo where Python is the dominant language
Bear 3
Have at least three original repos where Objective-C is the dominant language
Bear
Have at least one original repo where Objective-C is the dominant language
Honey Badger
Have at least one original Node.js-specific repo
Raven
Have at least one original repo where some form of shell script is the dominant language
Epidexipteryx
Have at least one original repo where C++ is the dominant language
@mikhailov Correct, S3 is not a CDN. However, my point was that you reduce the scalability by having all traffic diverge to your server. Meaning, you take on the entire load of S3 traffic, thereby sidestepping its ability to scale requests. Aren't you taking the hit for bandwidth and CPU load to serve through nginx? Nginx has to serve and buffer the request to the client. Thanks for the clarification.