Namespace ServiceStack.Redis

Classes

BasicRedisClientManager

Provides thread-safe retrieval of redis clients since each client is a new one. Allows the configuration of different ReadWrite and ReadOnly hosts

PooledRedisClientManager

Provides thread-safe pooling of redis client connections. Allows load-balancing of master-write and read-replica hosts, ideal for 1 master and multiple replicated read replicas.

PooledRedisClientManager.DisposablePooledClient<T>

Manage a client acquired from the PooledRedisClientManager Dispose method will release the client back to the pool.

RedisClient

The client wraps the native redis operations into a more readable c# API.

Where possible these operations are also exposed in common c# interfaces, e.g. RedisClient.Lists => IList[string] RedisClient.Sets => ICollection[string]

For interoperability GetCacheClient() and GetReadOnlyCacheClient() return an ICacheClient wrapper around the redis manager which has the affect of calling GetClient() for all write operations and GetReadOnlyClient() for the read ones.

This works well for master-replica replication scenarios where you have 1 master that replicates to multiple read replicas.

RedisClientManagerConfig

RedisClientsManagerExtensions

Useful wrapper IRedisClientsManager to cut down the boiler plate of most IRedisClient access

RedisCommandQueue

RedisConfig

RedisData

RedisDataExtensions

RedisDataInfoExtensions

RedisDiagnostics

RedisEndpoint

RedisException

Redis-specific exception. Thrown if unable to connect to Redis server due to socket exception, for example.

RedisExtensions

RedisGeo

RedisGeoResult

RedisGeoUnit

RedisLock

RedisManagerPool

Provides thread-safe pooling of redis client connections. All connections are treated as read and write hosts.

RedisNativeClient

This class contains all the common operations for the RedisClient. The client contains a 1:1 mapping of c# methods to redis operations of the same name.

Not threadsafe, use a pooled manager! All redis calls on a single instances write to the same Socket. If used in multiple threads (or async Tasks) at the same time you will find that commands are not executed properly by redis and Servicestack wont be able to (json) serialize the data that comes back.