Re:Global Multi-Cloud Replication in FaunaDB Serverless Cloud
by redwood on Thursday June 08, 2017 @06:56PM
(#14517823)
How do you handle write conflicts?
Re:Global Multi-Cloud Replication in FaunaDB Serverless Cloud
by evanweaver on Thursday June 08, 2017 @07:30PM
(#14518013)
Transactions are strictly serialized; the paper explains how this works the best: https://fauna.com/pdf/FaunaDB-Technical-Whitepaper.pdf
We use a single-phase model inspired by Calvin, rather than Spanner's two-phase model. The tradeoff is that interactive transactions (like in SQL) are not supported, but overall latency and throughput are much better.
You don't have to set any priorities, and partition events don't change commit latency for the cluster majority.
Currently FaunaDB drivers use geo DNS in route53 to automatically find the closest region, although you can pin to specific regions if you know the cname. If that region doesn't own the data for the logical database in question, FaunaDB forwards the request internally.
In the future, drivers will maintain their own ϕ accrual failure detectors and make faster and smarter routing decisions than DNS can provide.