You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

2.7 KiB


Build Status

An experimental interface to use different caches interchangeably via URIs. The goal for this library is to simplify using a caching layer for use with different services, enabling easy swapping of backends without the hassle of configuration.

To achieve this, we use unique "uris" for each driver, giving us a single string to configure the settings, much like database servers and other software.


Cache Types


Implemented using, this driver provides an in-memory lru cache implementation. Items in this cache will be evicted on an as-needed basis, with the most frequently used items staying in memory longer.


Implemented using, this driver provides an in-memory object cache. This driver specifically supports non-serialized storing of objects when using Get(key, dstPointer)


Implemented using, this driver provides a Memcache connector for the Memcached protocol and compatible servers.


Implemented using, this driver provides a Redis connector for the ever popular Redis key-value store.


When the driver requires it, values are almost always serialized into []byte. The library can automatically handle this as long as the structures are supported by msgpack. Future plans may include other serialization methods or customized serialization.

The exception to the above is for raw []byte values and strings (stored as a []byte), as they can be easily converted.


The CacheInterface interface has all methods. All drivers will implement this on a best-effort basis.

type CacheInterface interface {
	Has(key string) bool
	Get(key string, dst ...interface{}) ([]byte, error)
	Set(key string, val interface{}, ttl time.Duration) (err error)
	Del(key string) error

In addition to this, cache drivers can be used without the cacheinterface.New method by using the New<Driver>Cache method and providing the necessary parameters.

Code & Testing

As many test methods as we can add have been implemented, with the exception being those the CI service (Drone) cannot support (Memcache, Redis) due to limitations using extra services.

All code should have tests to verify there isn't anything broken with a new commit.