You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At FrOSCon 2017, someone asked about support for 2-phase commits. Currently this can be done by running the first phase in the module's apply() callbacks and the second phase in the finish() callback.
It might make sense to build explicit support for 2pc instead.
The text was updated successfully, but these errors were encountered:
Events in the transaction log could contain a field noting their phase.
Appending an event would allow setting the field.
During apply, the transaction manager walks over the log once for each required phase.
A set of database/network/etc modules could apply changes to structured data during the first phase; with a common record number handed out by a record-manager module
The record-manager module commits the transaction's record number as part of the second phase; thus making the record active.
At FrOSCon 2017, someone asked about support for 2-phase commits. Currently this can be done by running the first phase in the module's apply() callbacks and the second phase in the finish() callback.
It might make sense to build explicit support for 2pc instead.
The text was updated successfully, but these errors were encountered: