Download the PHP package noizu-labs/fragmented-keys without Composer
On this page you can find all versions of the php package noizu-labs/fragmented-keys. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download noizu-labs/fragmented-keys
More information about noizu-labs/fragmented-keys
Files in noizu-labs/fragmented-keys
Package fragmented-keys
Short Description Fragmented Key Management and Invalidation Library for use with Memcache.
License mit
Informations about the package fragmented-keys
FragmentedKey
tl;dr; A php library for managing cache invalidation by tracking tag-value pair versions on memcache, apc or other storage device and generating derived cache keys based on those values.
For a Java port of this library please see (https://github.com/noizu/fragmented-keys-4java)
Overview
Fragmented Keys provide a straightforward way to manage and invalidate composite cache keys.
It does this by persisting in memcache (or other back-end persistance layer of your choice) tag-instance versionining information. When constructing composite/fragmented keys these tags and their versions are used to generate the final composite key.
Thus if you wanted to tie something to to the granularity of say a specific thing like username you can do the following:
You can then Invalidate only items linked to your user's username by calling:
Behind the scenes this looks something like blocking out everything below the [Targeted User] bucket.
Or you could just go crazy and invalidate all keys that rely on Global.Greating
but amke sure your database is ready for it.
Setup & Installation
Installation
This project is available on composer, just add noizu-labs/fragmented-keys to your required list. "require": { "noizu-labs/fragmented-keys": "dev-master", }
Setup
The code depends on a Memcached, Memcache or APC handle being available and configured along with a global prefix to avoid collisions.
Components
Cache Handlers
Tags
Tags are a logical grouping that you would under certain circumstance invalidate assocaited cached data.
A User:$id pair, a Site:$siteId, etc. This library takes they tag-instance pairs and appends @version fields to them so that when you want to invalidate a large swatch of related items you don't need to send dozens of invalidate requests to memcache, or apc. You just make a single $tag->increment() call and any associated keys that us that tag-instance (User:$userId) will generate new keys;
Tag Class | Description |
---|---|
Standard | Basic Key. Persists version to specified cache handler |
Delayed* | Basic Key with built in Delay. Only internal key versions greater than the specified delay will cause a new version to be returned. Allowing you to pull cached content that only updates every hours, 30 seconds, etc. |
Constant | Key with Constant associated Version. E.g. version can only be set once at construction time. useful for incorporating non version tag-instance details in large composite keys |
*Delayed is not yet implemented
Key Rings
Key rings help may your life easier by letting you define common key structures one and then reuse him in your code as needed. You can tweak settings in your config, or even define custom keys that always include some additional tag s with out requiring your cache caller to manually include them!
Example
*The ability to auto include params isnt fully backed into the config process yet but you can emulate it easily by extending the base keyring class and doing the following