PHPackages                             noizu-labs/fragmented-keys - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Caching](/categories/caching)
4. /
5. noizu-labs/fragmented-keys

ActiveLibrary[Caching](/categories/caching)

noizu-labs/fragmented-keys
==========================

Fragmented key cache invalidation library. Compose cache keys from independently versioned tags — increment a tag to invalidate all dependent keys without explicit deletes.

0.2.1.1(12y ago)179.4k1[1 issues](https://github.com/noizu/fragmented-keys/issues)1mitPHP

Since Aug 8Pushed 11y ago4 watchersCompare

[ Source](https://github.com/noizu/fragmented-keys)[ Packagist](https://packagist.org/packages/noizu-labs/fragmented-keys)[ RSS](/packages/noizu-labs-fragmented-keys/feed)WikiDiscussions master Synced 1w ago

READMEChangelogDependencies (1)Versions (4)Used By (1)

FragmentedKey
=============

[](#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 ()

Overview
--------

[](#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:

```
use NoizuLabs\FragmentedKeys\Key\StandardKey;
use NoizuLabs\FragmentedKeys\Tag\StandardTag;

$globalGreetingTag = new StandardTag("Global.Greeting", "global");
$userUserNameTag = new StandardTag("User.Username", $userId);
$keyObj = new StandardKey(
    "CacheDataThatInvalidatesWhenUserNamesAreChanged",
    [$userUserNameTag, $globalGreetingTag],
);
$cacheKey = $keyObj->getKeyStr();
```

You can then Invalidate only items linked to your user's username by calling:

```
$userUserNameTag = new StandardTag("User.Username", $userId);
$userUserNameTag->increment();
```

Behind the scenes this looks something like blocking out everything below the \[Targeted User\] bucket.

```
  AllKey
    \
     \-[ ]Global.Greeting
            \
             \-[ ]Other User Cached Greeting
              \
               \-[x]Targeted User

```

Or you could just go crazy and invalidate all keys that rely on Global.Greating

```
$globalGreetingTag->increment();
```

but amke sure your database is ready for it.

```
  AllKey
    \
     \-[x]Global.Greeting
            \
             \-[x]Other User Cached Greeting
              \
               \-[x]Target User

```

Setup & Installation
========================

[](#setup--installation)

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
-----

[](#setup)

The code depends on a Redis, Memcached or APCu handle being available and configured along with a global prefix to avoid collisions.

```
use NoizuLabs\FragmentedKeys\CacheHandler\APCuHandler;
use NoizuLabs\FragmentedKeys\CacheHandler\MemcachedHandler;
use NoizuLabs\FragmentedKeys\Configuration;
use NoizuLabs\FragmentedKeys\Tag\StandardTag;

$m = new \Memcached();
Configuration::setDefaultCacheHandler(new MemcachedHandler($m));
Configuration::setGlobalPrefix("MyApp");

// you may override the handler per tag by calling
$tag->setCacheHandler($alternativeHandler);

// or by passing a handler to the constructor.
$tag = new StandardTag("Users", "1234", null, new APCuHandler());
```

Components
==========

[](#components)

Cache Handlers
--------------

[](#cache-handlers)

```
use NoizuLabs\FragmentedKeys\CacheHandler\APCuHandler;
use NoizuLabs\FragmentedKeys\CacheHandler\MemcachedHandler;
use NoizuLabs\FragmentedKeys\CacheHandler\MemoryHandler;
use NoizuLabs\FragmentedKeys\CacheHandler\RedisHandler;

$apcuHandler     = new APCuHandler();
$inMemoryHandler = new MemoryHandler();
$memcachedHandler = new MemcachedHandler(new \Memcached());
$redisHandler    = new RedisHandler(new \Redis());
```

Tags
----

[](#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 ClassDescriptionStandardTagBasic tag. Persists version to the specified cache handler.DelayedTagTag with a built-in grace window. For `delaySeconds` after an increment, readers keep seeing the previous version, letting you serve cached content that only rolls over every N seconds/minutes/hours.ConstantTagTag with a constant associated version, set once at construction time. Useful for incorporating non-versioned tag-instance details in large composite keys.Via a `KeyRing`, select the type with the `'type'` option (`'standard'`, `'delayed'`, or `'constant'`); `DelayedTag` also reads a `'delay_seconds'` option.

Key Rings
---------

[](#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

```