Re:Show HN: FaunaDB, a strongly consistent, globally distrib...
by freels on Wednesday March 15, 2017 @08:35PM
(#13881302)
One thing that makes this easier is that FaunaDB does not support session transactions, rather you must express your transaction logic as a single Fauna query, which is executed atomically. Transactions can still involve arbitrary keys, however.
And yes, for reads, by default the coordinating node chooses a timestamp and uses that to query all involved data partitions. Each partition will respond with the requested data as of at that timestamp, or will delay responding until it has caught up.
One nice thing about this approach is that any chosen timestamp is enough to provide a consistent snapshot view of the dataset at that time. This ends up being useful for bulk or incremental reads, where a longer running process needs a stable view of the dataset.
Re:Show HN: FaunaDB, a strongly consistent, globally distrib...
by ewrcoffee on Thursday March 16, 2017 @09:06PM
(#13890520)
Without session transaction, how does the application performs transactional read modify write?
Re:Show HN: FaunaDB, a strongly consistent, globally distrib...
by Efrim-Lipkin on Wednesday March 15, 2017 @07:33PM
(#13880941)
Okay, Last question because I'm in Asia and it's 7:30 and I am tired. (But yea, I'm a Midwestern computer scientist who just happens to be in Asia ;-)
Question #2 -- Two, or Three, or More transactions occur simultaneously that want to change data D. each of these transactions send out transaction logs that contradict each other. What happens?
EL
Is this correct?
EL