Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Our storage model must support the concept of transactions #102

@jmaferreira

Description

@jmaferreira

Something in the sense of BeginTransaction, EndTransaction, Commit.

The filesystem may or may not implement this (I would champion a big YES here).

Luis, think about this please. It would be a solution similar to the ESS checkout functionality .

Fedora Commons states:

Transactions
Fedora 4.0 transactions provide the ability to effectively wrap a series of repository actions which can be committed or aborted as an atomic unit. Not only is this useful for managing inter-dependent actions, it has also proven beneficial in terms of general performance. One of the largest slowdowns in any repository modification action is the actual "persist" phase. Every REST API call that results in a repository modification completes with a "save". In the cases where performance is of higher value than synchronous consistency, bundling multiple API calls into a single transaction shows a 30% to 60% performance improvement, depending on the type of events involved.

https://wiki.duraspace.org/display/FF/Fedora+4.0+Feature+Set#Fedora4.0FeatureSet-Transactions

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions