Incredible crap. Someone finds out CDNs exist and immediately jump on to a) let's use Amazon's because it's the cloud! Cloud! Cloud! - Yes! We're all individuals! - You're all different! - Yes, we ARE all different! b) nginx is suddenly obsolete.
CDNs acting as distributed reverse proxies have been around for many, many years. Amazon or not.
Pretty much the simple truth. You might consider a major revision of the article in all honesty.
Everyone who has access to a CDN working on major sites should be or become aware that using it this way is the [intended] usage of a CDN. If you get down to the nitty-gritty, ngnix can be used to handle more temporary caching of json ....or i guess soap.. responses.. as well as being a good place to keep your content pages fresh.
Ideally in most situations, you want the application server to be there for one time requests for updates and to enable a bajillion concurrent connections on your AJAX calls. We mostly have one site mirror/publishing server per cluster, a distributed db, and the rest are service comps using the CDN for primary storage. The server's disk space is for persistent thinking!
Though don't get me wrong, Amazon and similar providers offering these features at the low end DOES enable sites on shared hosting and startups to join in the tech. This is very 'cloudy'...cloudesque?
My preference, spin up extra micro-app services with clouds. Let files be just files on cdn otherwise ;p
Comment
Incredible crap. Someone finds out CDNs exist and immediately jump on to a) let's use Amazon's because it's the cloud! Cloud! Cloud! - Yes! We're all individuals! - You're all different! - Yes, we ARE all different! b) nginx is suddenly obsolete.
CDNs acting as distributed reverse proxies have been around for many, many years. Amazon or not.
Replies
I don't care about buzzwords. I care about delivering something great and I don't care what buzzwords that involve.
Pretty much the simple truth. You might consider a major revision of the article in all honesty.
Everyone who has access to a CDN working on major sites should be or become aware that using it this way is the [intended] usage of a CDN. If you get down to the nitty-gritty, ngnix can be used to handle more temporary caching of json ....or i guess soap.. responses.. as well as being a good place to keep your content pages fresh.
Ideally in most situations, you want the application server to be there for one time requests for updates and to enable a bajillion concurrent connections on your AJAX calls. We mostly have one site mirror/publishing server per cluster, a distributed db, and the rest are service comps using the CDN for primary storage. The server's disk space is for persistent thinking!
Though don't get me wrong, Amazon and similar providers offering these features at the low end DOES enable sites on shared hosting and startups to join in the tech. This is very 'cloudy'...cloudesque?
My preference, spin up extra micro-app services with clouds. Let files be just files on cdn otherwise ;p