931–940 of 1001 posts
Earlier quoted context omitted.
durability is different from availability
Which is why he made the distinction between the two.
Earlier quoted context omitted.
The 10% savings of ~$10 does not compare to time/potential business lost, but thanks for the tip :)
> potential business lost My startup's op team had a great discussion today because of this that basically boils down to "if we hit our sales goals, an incident like this a year from now would end our company". Looks like our plans to start prepping for multi-cloud support will be a higher priority.
Earlier quoted context omitted.
The 10% savings of ~$10 does not compare to time/potential business lost, but thanks for the tip :)
> potential business lost My startup's op team had a great discussion today because of this that basically boils down to "if we hit our sales goals, an incident like this a year from now would end our company". Looks like our plans to start prepping for multi-cloud support will be a higher priority.
Earlier quoted context omitted.
The 10% savings of ~$10 does not compare to time/potential business lost, but thanks for the tip :)
> potential business lost My startup's op team had a great discussion today because of this that basically boils down to "if we hit our sales goals, an incident like this a year from now would end our company". Looks like our plans to start prepping for multi-cloud support will be a higher priority.
S3 is currently (22:00 UTC) back up. The timeline, as observed by Tarsnap: First InternalError response from S3: 17:37:29 Last successful request: 17:37:32 S3 switches from 100% InternalError responses to 503 responses: 17:37:56 S3 switches from 503 responses back to InternalError responses: 20:34:36 First successful request: 20:35:50 Most GET requests succeeding: ~21:03 Most PUT requests succeeding: ~21:52
Down for us as well. We have cloudfront in front of some of our s3 buckets and it is responding with CloudFront is currently experiencing problems with requesting objects from Amazon S3. Can I also say I am constantly disappointed by AWS's status page: https://status.aws.amazon.com/ it seems whenever there is an issue this takes a while to update. Sometimes all you see is a green checkmark with a tiny icon saying a n…
To mitigate the effect of S3 going down I use cross-region replication to replicate objects to another S3 region. If S3 went down in my primary region I could update the app config to write back to the backup region and update the CDN configuration to use the backup region as an origin. I did that out of paranoia but it turns out this could happen to us. Does that sound like a sensible approach? Fortunately all my co…
Earlier quoted context omitted.
Honestly, if you're a big service that millions of people use, you should not put all your eggs in a single basket and should probably use a mix, in case one of the clouds goes down like in this case.
That depends if you're willing to pay for the cost of hosting all your content twice and the development overhead of managing that. Twice the persistences means twice the chance of an issue occurring.
Twice the persistence means always having at least one backup and thus the occurance of downtime reduces not up
I never understood why so many devs flocked to AWS. I actually find their abstraction of services gets in the way and slows down my dev instead of making it easier like so many devs claim it does. I prefer Linode.
Earlier quoted context omitted.
I've used both Google Cloud and AWS, and as of a year or so ago, I'm a Google Cloud convert. (Before that, you guys didn't at all have your shit together when it came to customer support) It's not in bad taste, despite other comments saying otherwise. We need to recognize that competition is good, and Amazon isn't the answer to everything.
We were on GCP for around a year, it was my decision I really wanted to love GCP and I initially did. But we recently switched to AWS. I think there is little GCP does better than AWS. Pricing is better on paper, but performance per buck seems to be on par. Stability is a lot worse on GCP, and I don't just mean service outages like this one (which they had their fair share) but also individual issues like instances s…