Figaro Transactional Data Store, or TDS, adds full ACID transaction support to Figaro Concurent Data Store (CDS). Changes to databases or their contents are atomic, consistent, isolated, and durable when using TDS. Transactions can be short lived or long running, lasting days if necessary. Transactions can improve system throughput in concurrent applications by grouping actions into a single commit to disk. Applications that use secondary indices to manage relationships require transactions to keep those relationships consistent.
The Figaro TDS transactional system in the Berkeley DB database engine offers a great deal of flexibility to accommodate your desired performance and durability requirements. For example, Figaro TDS supports the ability to trade off durability for speed, or to allow readers to see uncommitted data to reduce locking overhead. Figaro TDS utilizes log files to contain information about transactional data that can be used to recover from application or systems failure.
Choose Figaro TDS when:
- There is a balance of concurrent readers and writers.
- Data integrity is critical.
- Recovery of committed data is a requirement.
- Database corruption is unacceptable.
- Replication is not required.
See http://bdbxml.net/blog/figaro-6-1-4-changelog.html for more information.
This package has no dependencies.
|18.104.22.16879 (current version)||29||9/19/2017|