Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have been looking into using http caching for one of my projects on heroku. The site is serving primarily dynamicish (meaning that the actual contents doesn't change that often) iFrame's and javascripts.

If I am understanding http caching services correctly (ie CloudFront, Edgecast & Akamai also has a similar solution) I will be able to technically scale my server nodes down considerably so long as I set the ttl on the cache to a reasonable amount of time. I am thinking 24-48 hours which means there should be only one request to the server in that time right?

Am I correct with this assumption?


share|improve this question
up vote 0 down vote accepted

Yes, something like CloudFront would allow you to dramatically reduce load.

If you use unique URLs for updated resources - like script_201110091213.js - you can even set a far-future TTL and just change the URL to the script whenever you change things in the script.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.