RedisConf18 - Migrating from Coherence to Redis
0 likes1,038 views
This document summarizes RCI's migration from Coherence to Redis for caching and session storage. It discusses why RCI migrated (to reduce costs, licensing fees, complexity, and improve performance and agility) and how it implemented Redis, including Redis architecture with masters, slaves and sentinels, configuration of Redis and Redisson client, and lessons learned. The migration helped RCI scale its web application by moving to a simpler caching solution with Redis.
RedisConf18 - Migrating from Coherence to Redis
- 1. Migrating from Coherence to Redis Balaji Mariyappan – Sr. Solutions Engineer Vivek Rajput – DevOps Engineer
- 2. Disclaimer The information contained in this presentation & expressed by the speakers are solely based on rci.com application experiences and practices
- 3. www.rci.com - Leader in vacation exchange
- 4. What RCI uses for caching & session-store? RCI.com web application serves members for booking the resort using self-service and guided portals. Web session management 24 GB Service-level caching 64 GB What
- 5. Why 2 How 3 What 1 Coherence to Redis Migration Cost Licensing Complexity Performance Monitoring Agility Redis Architecture Redis configuration Testing Harness
- 6. Coherence infrastructure What Durability Availability Scalability Client Load Balancer Coherence Proxy Coherence Proxy Coherence Proxy Coherence Cache nodes Coherence Cache nodes Coherence Cache nodes Coherence Cache nodes Web Clients
- 7. What Near Cache Local Cache Dist Cache Remote Cache Replicated Cache
- 9. Complexities and choices • Cluster implementation • Connection options • Multiple cache storage types • JVM Config / dependencies • Automation issues Why
- 10. Licensing & other factors On-Premise Oracle Licenses (1) Why AWS/Azure/Google cloud Oracle Licenses (2) • Licensing disparity • Scalability restrictions • Cache eviction controls • Operational overhead • Testing limitation • Performance • Monitoring
- 11. Redis Architecture How Web Session clients Load Balancer Master (Slot: 0-16384) Slave (Slot: 0-16384) Redis-Sentinel Redis-Sentinel
- 12. Future Architecture Redis Cluster Client Load Balancer Master 1 (Active) (Slot: 0-8000) Slave 1 (Passive) (Slot: 0-8000) Redis-Sentinel Redis-Sentinel Master 2 (Active) (Slot: 8001-16384) Slave 2 (Passive) (Slot: 8001-16384) Redis-Sentinel Redis-Sentinel How
- 13. Redis Configuration – Redis.conf • ################# NETWORK #################### • bind x.x.x.x • port 6379 • protected-mode yes • ################# REPLICATION ################# • slaveof <masterip> <masterport> • ################### LIMITS #################### • maxclients 10000 • maxmemory <bytes> • maxmemory-policy LRU How
- 14. Redis Configuration – Redisson.json { "singleServerConfig":{ "address": "redis://xx.xx.xx.xx:6379" }, "codec":{ "class":"org.redisson.codec.FstCodec" } } How
- 15. Other Configurations Server.xml (Server-side) <Context crossContext="true" path="/" docBase="/opt/tomcat8/apache-tomcat-8.5.24/applications/rcio-login.war" sessionCookiePath="/" sessionCookieName="JSESSIONID"> <Manager className="org.redisson.tomcat.RedissonSessionManager" configPath="${catalina.base}/redisson.json" readMode="REDIS"/> </Context> Cache.properties (application-side) # SPRING CACHE (CacheProperties) spring.cache.cache-names=typeAheadCache, googleCache spring.cache.redis.cache-null-values=true # Allow caching null values. spring.cache.redis.key-prefix= # Key prefix. spring.cache.redis.time-to-live=900000ms # Entry expiration. By default the entries never expire. spring.cache.redis.use-key-prefix=true # Whether to use the key prefix when writing to Redis. spring.cache.type= # Cache type. By default, auto-detected according to the environment. How
- 16. Demo • Server.xml configuration • Redisson.json configuration • Session key-store and validation How
- 17. Lessons learnt • Supportability of Redis client for different application server • Redis learning curve & Configuration • Elimination of cluster • JVM tuning issues • Voiding various Cache types • Better health-check configuration How
- 18. Thank you