Reddit is down right now with a 503 - they're on AWS.
Go to twitter, they are not on AWS.
AWS US East is experiencing high error rates on several services
141–150 of 184 posts
Re: AWS US East is experiencing high error rates on several services
#142Reddit is down right now with a 503 - they're on AWS.
Go to twitter, they are not on AWS.
Re: AWS US East is experiencing high error rates on several services
#143Earlier quoted context omitted.
Yes, as it's shifting the blame away from their choice - which was to use AWS.
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.
Re: AWS US East is experiencing high error rates on several services
#144For ADHD I would recommend Concerta/Ritalin/Adderall; that would enable you to read for not just a few seconds more but even minutes more before you judge. (I'm not joking here, I'm using 36mg Concerta for about about 4yrs now. Before that I also often came across as an asshole.) There is also a less evasive way of improving your online communication quality: http://www.paulgraham.com/disagree.html
> Before that I also often came across as an asshole
Only before that, eh?
Also, mind disclosing the fact you are blatantly advertising your own services?
Re: AWS US East is experiencing high error rates on several services
#145This 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...
Re: AWS US East is experiencing high error rates on several services
#146This 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...
Yes it is without a date range. 99.999% / year means something while 99.999% uptime does not mean anything by itself.
Re: AWS US East is experiencing high error rates on several services
#147Earlier quoted context omitted.
If down for longer than 18 minutes then they missed "5 9s" availability (.3 hours / 3.5 years). Not that it is supposed to work that way.
Software bug caused downtime vs infrastructure / hardware availability uptime to me are a different guarantee. I am pretty sure someone did something recently to DynamoDB.
Infrastructure guy here doing this for 14 years. Downtime is downtime. You get a pass if its "scheduled maintenance" you've notified your customers about to allow them to be prepared, but if you silently perform maintenance and it goes to shit, you've just counted against your metrics.
Re: AWS US East is experiencing high error rates on several services
#148Earlier quoted context omitted.
Source for service with better uptime than Amazon?
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?
Re: AWS US East is experiencing high error rates on several services
#149For ADHD I would recommend Concerta/Ritalin/Adderall; that would enable you to read for not just a few seconds more but even minutes more before you judge. (I'm not joking here, I'm using 36mg Concerta for about about 4yrs now. Before that I also often came across as an asshole.) There is also a less evasive way of improving your online communication quality: http://www.paulgraham.com/disagree.html
> Before that I also often came across as an asshole Only before that, eh? Also, mind disclosing the fact you are blatantly advertising your own services?
I wish it would be my own service. :D
How did you come to this conclusion? From smoyer's comment? (btw, thx smoyer, nice joke. :)
Also I wrote about ADHD on HN in the past. I really didn't mean it in an offensive way: https://news.ycombinator.com/item?id=3064846
Re: AWS US East is experiencing high error rates on several services
#150Earlier quoted context omitted.
DynamoDB now support cross-region replication [0] so you can build more resilient applications with it [0] http://docs.aws.amazon.com/amazondynamodb/latest/developergu...
I don't think cross-region replication would've helped in this case: "The replica tables are intended to serve as read-only copies of the data; however, it is possible to write data to a replica table. If you write data to a replica, those changes will not be propagated to the master, or to any other replicas."
You can relatively trivially build multi-master cross-region replication in DynamoDB by using kinesis and writing to kinesis instead of DynamoDB directly. On the consuming end of Kinesis you then fan out to all the DynamoDB (or whatever other database you want to use) regions[1]. Admittedly this only works with some relatively relaxed constraints on the latency you can see, intra region latency can go up to 1 second although rarely, while cross-region is around 3 seconds. An important role is also played by the structure of your objects and how accepting they are of concurrent updates coming from different regions (which is the main reason why the default replication in DynamoDB is not multi-master).
[1]: http://tech.adroll.com/blog/data/2015/06/26/kinesis.html