// boilerplate code example with Memcached, but any // MatthiasMullie\Scrapbook\KeyValueStore adapter will work $client = new \Memcached(); $client->addServer('localhost', 11211); $cache = new \MatthiasMullie\Scrapbook\Adapters\Memcached($client); // create transactional cache layer over our real cache $cache = new \MatthiasMullie\Scrapbook\Buffered\TransactionalStore($cache); // begin a transaction $cache->begin(); // set a value // it won't be stored in real cache until commit() is called $cache->set('key', 'value'); // returns true // get a value // it won't get it from memcached (where it is not yet set), it'll be read from // PHP memory $cache->get('key'); // returns 'value' // now commit write operations, this will effectively propagate the update to // 'key' to memcached (or whatever adapter we decide to use) $cache->commit(); // ... or rollback, to discard uncommitted changes! $cache->rollback();
TransactionalStore makes it possible to defer writes to a later point in time. Similar to transactions in databases, all deferred writes can be rolled back or committed all at once to ensure the data that is stored is reliable and complete. All of it will be stored, or nothing at all.
You may want to process code throughout your codebase, but not commit it any changes until everything has successfully been validated & written to permanent storage.
While inside a transaction, you don’t have to worry about data consistency. Inside a transaction, even if it has not yet been committed, you’ll always be served the one you intend to store. In other words, when you write a new value to cache but have not yet committed it, you’ll still get that value when you query for it. Should you rollback, or fail to commit (because data stored by another process caused your commit to fail), then you’ll get the original value from cache instead of the one your intended to commit.
It too is a KeyValueStore, but adds 3 methods:
Initiate a transaction: this will defer all writes to real cache until commit() is called.
Transactions can be nested. A new transaction can be begin while another is already in progress. Committing the nested transaction will apply the changes to the one that was already in progress. Changes will only be committed to cache once the original transaction is committed. Rolling back a nested transaction will only roll back those changes and leave changes in the parent transaction alone.
Commits the deferred updates to real cache. If the any write fails, all subsequent writes will be aborted & all keys that had already been written to will be restored to their original value.
Roll back all scheduled changes.