News for hackers. Stuff that matters.
Re:EC2 Price Reduction (C4, M4, and R3 Instances) by mattbillenstein on Wednesday January 06, 2016 @01:04AM (#10848901)
App on AWS, data on S3, Varnish caches on Linode, Digital Ocean, etc. Route53 for managing geo-DNS.
Re:EC2 Price Reduction (C4, M4, and R3 Instances) by fideloper on Wednesday January 06, 2016 @08:26AM (#10850348)
Not sure I get the logic of Varnish being on different providers. Are your static assets also hosted on Linode/DO, in addition to Varnish?
Re:EC2 Price Reduction (C4, M4, and R3 Instances) by toomuchtodo on Wednesday January 06, 2016 @01:09PM (#10852264)
Varnish caches dynamic app data. Your static assets should be in a CDN, served outside of your infrastructure.
Re:EC2 Price Reduction (C4, M4, and R3 Instances) by fideloper on Wednesday January 06, 2016 @04:28PM (#10853914)
So to put what I'm cofused about plainly (my fault on the confusion I'm sure :D ):

It sounds like the reason for having that outside of your primary infrastructure (or more accurately, inside a cheaper bandwidth host) are lower bandwidth costs with the trade-off of some slower requests getting sent to your origin server when the cached resource expires/is invalidated.

Re:EC2 Price Reduction (C4, M4, and R3 Instances) by toomuchtodo on Wednesday January 06, 2016 @04:43PM (#10854037)
Exactly! You're architecting your infrastructure to take advantage of the most efficient cost option at each layer.
Re:EC2 Price Reduction (C4, M4, and R3 Instances) by mattbillenstein on Thursday January 07, 2016 @05:24AM (#10857132)
So mainly thinking of Varnish as the CDN -- paying a 3rd party CDN is pricey.