3 ms·
We use DynamoDB for storage and state and its unaffected. Are you referring to this kind of scenario? https://github.blog/2018-10-30-oct21-post-incident-analys
by carlsborg 7y ago
We use DynamoDB for storage and state and its unaffected.
Are you referring to this kind of scenario? https://github.blog/2018-10-30-oct21-post-incident-analysis/ https://github.blog/2018-10-30-oct21-post-incident-analysis/
- lxgr 7y agoThen you probably don't have the strict consistency and durability requirements that I mentioned. That is probably true for many use cases, but certainly not for all. Yes, after skimming your referenced article, this is exactly the type of issue that prevents a "simple" failover when databases are involved. Depending on your application, even returning stale data on one AZ in a split brain scenario might not be acceptable (this is a stronger requirement than not allowing non-reconcilable conflicting writes).
- carlsborg 7y agoDynamoDB allows strongly consistent reads and your data is replicated across AZs. Id argue that its even better than an RDS setup in that respect. RDS lets you choose a DB Engine (MySQL, Postgres, etc). the replication depends on the engine you choose, e.g. Postgres native streaming. Heres a good writup on how it works and best practices (https://aws.amazon.com/blogs/database/best-practices-for-amazon-rds-postgresql-replication/ https://aws.amazon.com/blogs/database/best-practices-for-ama...)