anchor.diff:  declarative transactions.
   
   Spring Cloud AWS integrates the http://aws.amazon.com/elasticache/[Amazon ElastiCache] service into the Spring unified
  -caching abstraction providing a cache manager based on the memcached protocol.
  -
  -[TIP]
  -====
  -Support for the Redis cache protocol is planned in a future release.
  -====
  +caching abstraction providing a cache manager based on the memcached and the redis protocol. The caching support fo Spring
  +Cloud AWS provides an own implementation memcached implementation for Elasitcache and uses
  +http://projects.spring.io/spring-data-redis/[Spring Data Redis] for Redis caches.
  +
  +=== Configuring dependencies for Redis caches
  +Spring Cloud AWS delivery an own implementation of a memcached cache, therefore no other dependencies are needed. For memcached
  +Spring Cloud AWS relies on Spring Data Redis to support caching and also to allow multiple Redis drivers to be used. Spring
  +Cloud AWS supports all Redis drivers that Spring Data Redis supports (currently Jedis, JRedis, SRP and Lettuce) with Jedis
  + being used internally for testing against Elasticache. A dependency definition for Redis with Jedis is shown in the example
  +
  +[source,xml,indent=0]
  +----
  +<dependencies>
  +    <dependency>
  +        <groupId>org.springframework.data</groupId>
  +        <artifactId>spring-data-redis</artifactId>
  +        <version>${spring-data-redis.version}</version>
  +    </dependency>
  +    <dependency>
  +    	<groupId>redis.clients</groupId>
  +    	<artifactId>jedis</artifactId>
  +    	<version>2.6.1</version>
  +    </dependency>
  +</dependencies>
  +----
  +
  +Spring CLoud AWS will automatically detect the Redis driver and will use one of them automatically.
   
   === Configuring caching with XML
   The cache support for Spring Cloud AWS resides in the context module and can therefore be used if the context module
  
positive.code: to support an expiry time. The Spring Cloud AWS cache configuration supports the expiry time setting per cache. The
  expiry time will be passed to the memcached service.
  
  The `cache` and `cache-cluster` elements accept an expiration attribute that defines the expiration time in seconds.
  No configured values implies that there is an infinite expiration time.
  
  [source,xml,indent=0]
  ----
  <beans>
  	<aws-cache:cache-manager>
  		<aws-cache:cache address="someLocalServer:4321" name="memc" expiration="423"/>
  		<aws-cache:cache-cluster expiration="10000" name="CacheCluster" />
  	</aws-cache:cache-manager>
  </beans>
  
negative.code: inside the cache manager.
  
  The example below demonstrates a configuration example that contains a pre-configured cache with an `cache-ref` element
  (which might be a local cache) and a `cache-cluster` configuration for Elasticache cache clusters.
  
  [source,xml,indent=0]
  ----
  <beans ...>
  	<aws-cache:cache-manager id="cacheManager">
  		<aws-cache:cache-ref ref="memcached" />
  		<aws-cache:cache-cluster name="SimpleCache"/>
  	</aws-cache:cache-manager>
  </beans>
  