Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. 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 am planning to use cloud storage for my app. What my app will do is retrieval of users data and user authentication and have the ability to sync data continuously.

Is it a good idea to use Amazon Glacier? Is there a bandwidth limitation or request or any downside of using it?

share|improve this question
up vote 4 down vote accepted

The use case you describe sounds like a better fit for Amazon S3. Amazon Glacier is designed for long term archives, rarely read and not required immediately.

share|improve this answer
@michaelOn Amazon S3 if I have a 1000 devices that uses my apps will it cost me much even I optimized my request? – kedomonzter Nov 5 '12 at 3:19
@mocca You should have a look at the pricing calculator but I don't think it would cost you much unless you transfer a massive amount of data – Michael Rutherfurd Nov 5 '12 at 5:37

Glacier is an archiving service. According to their site "Amazon Glacier is optimized for data that is infrequently accessed and for which retrieval times of several hours are suitable". It's meant for data that you don't want to throw away but don't need to access regularly.

To draw a metaphor with paper documents. If the paper on your desk is RAM, the filing cabinet in your office is your HDD, the departmental records room is Amazon S3, the offsite record archival that takes a week to requisition a box of files is Glacier.

share|improve this answer
Nice analogy... – Michael Rutherfurd Nov 5 '12 at 2:56

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.