Comparing Redis , AWS Elasticache giving multiple options to cache the data in cloud . Its enhanced with two ways of Access control options in PaaS Service
Below are the few mission handling features we loved in elastic cache ,
- Detecting data failures and recovery the nodes automatically
- Multi AZ features with automatic failover to replication nodes
- Redis Cluster mode enabled supports data partitioning up to 500 shards in different zones
- Redis managed backups , automatic failure detection and log files transfer to Kinesis Firehouse and cloud watch
- Easy online migration from any Redis source
- Encryption at rest and Encryption in transit are supported
- Data volume up to peta bytes with micro second response time
Preparing our source and target Redis nodes for migration
- Launched two EC2 machines and installed redis 5.x version
- Configured replication between master and replica
- protected-mode no
- bind datablogs.xcnphd.ng.0001.use1.cache.amazonaws.com 6379
- requirepass should be disabled
Note : Transferring source master or replica should not have AUTH configured and protected mode disabled
Starting Migration
Data looks good , once all the data transferred from IaaS to PaaS . Complete the migration in the Elasticache console and point the application endpoints to Elasticache node