News for hackers. Stuff that matters.
Re:Is Nginx obsolete now that we have Amazon CloudFront? by bithive123 on Monday July 30, 2012 @07:04PM (#4315154)
I think not. Requirements change, and locking myself in to a front-end cache is not appealing. I may also have things which I can't or won't let others cache for me, so I want my local stack to be optimized anyway. You won't see me serving everything out of WEBrick anytime soon just because I have a cloud cache.

It's nice to be able to defer decisions, especially optimizations, but making performance someone else's problem entirely seems like it could promote sloppy thinking and poor work. It's the difference between augmenting a solid platform when the need arises versus front-loading dependencies because it's okay to be lazy.

Re:Is Nginx obsolete now that we have Amazon CloudFront? by peterbe on Monday July 30, 2012 @07:20PM (#4315211)
On several of my modern projects, there's not a single piece of static data that can't be cached forever in a CDN. That's because server-side code is not getting really good at managing the initial build of static assets and the delivery of their URL.
Re:Is Nginx obsolete now that we have Amazon CloudFront? by ehutch79 on Tuesday July 31, 2012 @09:52AM (#4317211)
errr. just because it's static, and a pdf, doesn't mean you want it cached on amazons servers.

sensitive business documents and such.

Re:Is Nginx obsolete now that we have Amazon CloudFront? by pavel_lishin on Tuesday July 31, 2012 @11:31AM (#4317728)
If it's serious enough, why are you serving it as a static, unprotected resource?