You make it sound like AWS has 100% uptime and services built on top of them are completely to blame.
And for something like Heroku's managed DBs you can't just achieve 99.99999% availability on a DB without making certain sacrifices. Availability isn't everything past a certain point
Thats not what im doing at all. I even gave a link to AWS documentation of achieving 5-nines by utilizing multiple AZs, etc. I also reiterated this in the comment you responded to above..
What sacrifices you talking about when synchronously replicating to a backup environment? Write latency? How do you deal with that usually? How much is too much? There are strategies to deal with reducing replication related latency depending on level of consistency required.
Costs and general complexity. It is quite easy to accidentally reduce a system's uptime by introducing extra complexity involved with higher availability
Yeah, I suppose in some circumstances their offering is OK.
I don't think i have ever worked on a system where 10 mins of data loss is anywhere near acceptable though.
I guess for mostly static pages, or self hosting a blog its ok, although id be pissed if i had to rewrite an article. Makes you wonder who their target market is.
Comments
You make it sound like AWS has 100% uptime and services built on top of them are completely to blame.
And for something like Heroku's managed DBs you can't just achieve 99.99999% availability on a DB without making certain sacrifices. Availability isn't everything past a certain point
Thats not what im doing at all. I even gave a link to AWS documentation of achieving 5-nines by utilizing multiple AZs, etc. I also reiterated this in the comment you responded to above..
What sacrifices you talking about when synchronously replicating to a backup environment? Write latency? How do you deal with that usually? How much is too much? There are strategies to deal with reducing replication related latency depending on level of consistency required.
Costs and general complexity. It is quite easy to accidentally reduce a system's uptime by introducing extra complexity involved with higher availability
Oh yeah, there are definitely additional costs and complexity involved.
Im just saying that these cloud service providers offering managed services should be covering all that - they certainly charge as if they do!
And in the case of heroku - and their specific architecture - it is not that complex. Im aware that other cases may vary.
No particular love for Heroku, but you can pay for multi az failover if you want it.
https://devcenter.heroku.com/articles/heroku-postgres-ha
If you don’t pay you won’t get the feature. Given that multi az failover directly impacts their cost that seems pretty fair.
Yeah, I suppose in some circumstances their offering is OK.
I don't think i have ever worked on a system where 10 mins of data loss is anywhere near acceptable though.
I guess for mostly static pages, or self hosting a blog its ok, although id be pissed if i had to rewrite an article. Makes you wonder who their target market is.
has aws ever suffered multi region blackouts? or even all AZs in one?