181–184 of 184 posts
This is why 99.99999999% uptime is a fallacy It is not really measuring the time you're going to be up. That interpretation is based on faulty assumptions. It's like the statement "the sun will burn out before one bit is flipped" is wrong. It is quite likely that by that time, all the bits will be gone. https://signalvnoise.com/posts/3067-lets-get-honest-about-up...
Earlier quoted context omitted.
I expect the reason is because Heroku could switch to a new provider in the future and it would be a pain to always update every reference to their provider. Parent seems to imply there's something wrong with choosing AWS. There is not. (forgive me if I mistook the tone)
You did; there is nothing wrong - but it's a choice. I.e. your site being down is your fault ultimately, not AWS's - you choose AWS (instead of many other choices OR making something with multiple, etc). Blaming it upstream is hiding passing the buck on your decision.
Earlier quoted context omitted.
I believe he meant things like using RabbitMQ instead of SQS (SQS isn't very good anyway IMHO) and things like that. More services running on plain old instances rather than AWS specific APIs, Azure specific APIs, etc. This prevents you from getting too locked in and losing control over your application. I honestly can't believe that Netflix can't even load their home page without DynamoDB and all this other stuff. E…
This is silly. Do you think you and your staff will maintain your homebrew RabbitMQ installation with better uptime than Amazon's team? And how much time/expense/manpower are you willing to devote to setting it up and monitoring it? And is that going to make your startup more successful than if you spent those resources developing the features your customers are asking for?
We do serious hosting for government and company and if we had a outage like amazon had yesterday, we would loose at least half of our clients and pay heavy cash penality.
I don't understand why people give so much a break to amazon. They have one of the worst uptime.
Earlier quoted context omitted.
It's the primary AWS region. You spin up your resources by default there unless you explicitly select another region in the console.
It's probably a good idea to pick other regions, especially the ones closest to yourself However, us-east is usually the cheapest one as well