Amazon ElastiCache 8/1/17. Why Amazon ElastiCache is important? Introduction:

Transcription

1 Amazon ElastiCache Introduction: How to improve application performance using caching. What are the ElastiCache engines, and the difference between them. How to scale your cluster vertically. How to scale your redis Cluster horizontally using replication groups. How to backup and recover your redis cluster. Why Amazon ElastiCache is important? 1

2 Why Amazon ElastiCache is important? When the application is getting popular, its performance will suffers under heavy load. At peak time, users are just giving up. Real-Time analytics. Data velocity. Amazon ElastiCache. Amazon ElastiCache is a manage web service. It supports two most popular key-value store engines which are redis and memcached. It is fully manage which means you don t have to worry beside your data. It is highly available, reliable. Cache Engines Amazon Elasticache supports two most popular key-value store engines. 1- Memcached. 2- Redis. These cache engines may seem similar, but they support a variety of different use cases and provide different functionality 2

3 Memcached Memchaed It is a flat cach. It support data structure which is a string You can support up to 1 megabyte in each value. It provides a very simple interface that allow you to write and read object inmemory key/value data stores. It has no persistence. So, If you added shards in a memcache cluster You can grow and shrink a cluster of memcached nodes to meet your demands. Redis 3

4 Redis It supports a rich set of data types like String, sets, and lists. It allows you to create a snapshots that back up your data, and then recover from the backups. Easy to sort and rank data Serving high speed message in distributed system. Redis- Data Types String Set Redis- Data Types List 4

5 Redis- Data Types Hashes More Info: Which one should I use? 5

6 Node and Clusters A cluster is a collection of one or more cache nodes. When you create a cluster, you specify the engine that all of the nodes will use. There are different nodes type, which can change over time, they rang from t2.micro node type with 555MB of memory up to an r3.8xlarge with 237 GB of memory. More info: Node and Clusters MemCached cluster can contain up to 20 nodes. Horizontally partition the data. Scaling Increasing or decreasing in your business grows or experiencing normal fluctuations in demand, needs you to meet your current demand. If you self-manage your cache, you need to provision sufficient hardware for your demand peaks, which can be expensive. By using Amazon ElastiCache you can scale to meet current demand, paying only for what you use. More info: 6

7 Scalling Horizontal Scaling: Memcached clusters comprises from 1 to 20 nodes, and up to 200 nodes in the same region. Scaling a Memcached cluster out and in is as easy as adding or removing nodes from the cluster. Redis consists of a single cache node that is handle read and write transactions, you can have up to five read replicas handle read-only requests. Also, Additional clusters can be created and group into a Redis replication group. Scalling Vertical Scaling: Change the node type and scale vertically. ElastiCache does not directly allow you to resize your cluster in this manner. When you scale your Memcached cluster up or down you must create a new cluster. Memcached clusters always start out empty unless your application populates it. By Redis, you can spin up a new cluster with the new cache node types and start redirect traffic to the new cluster, The new cluster can be initialized from a backup. Node and Clusters Redis clusters can contain a single node or up to 6 nodes inside a shard; however multiple clusters can be grouped into a redis replication group. Can have up to 15 shard, with data partitioning across the shard. All nodes within a cluster are designed to be of the same node type and have the same parameter and security group settings. 7

8 Replication and Multi-AZ Replication and Multi-AZ Replication is a useful technique Provides rapid recovery in the event of node failure. Servs up very high volumes or read queries beyond the capabilities of a single node. Cache clusters running Memcached are stand alone in memory services without any redundant data protection service. Cache clusters running Redis Replication group. Consists of up to 6 clusters, one prime and 5 replicas Allowing scaling horizontal.. Increase availability and minimize lost of data. Multi-AZ Replication Groups Increase availability and minimize lost of data. Primary node failure Multi-AZ selects a read replica to be the new prime node. Amazon Elasticache updates the DNS entry of a new primary node to allow your application to continue processing. 8

9 Backup and Recovery Create snapshot of Redis clusters via few clicks on the console. Create automatic or manual snapshots. Using snapshots for data persistence, scaling and archiving. Amazon elasticache generates a standard redis database backup file that gets stored in Amazon S3. Recovery: It is able to restore a RDB file generated from any other compatible Redis cluster. Note: Snapshots can not be created for memcached engine, because it is purely in-memory key/value store and always starts empty. Access Control Do I have permissions to access an ElastiCache cachecluster.? Access to your Amazon elasticache is controlled primarily by restricting inbound network access to your cluster, which are restricted through the use of security group. When nodes deployed inside VPC, each node will be issued a private IP address within one or more subnets. Access Control Can I access to manage configuration and infrastructure of the cluster with the primary permission? You have to use AWS Identity and access management (IAM) service. You can define policies that control which AWS users can manage the Amazon elasticache infrastructure itself. 9

10 Conclusion What is the concept of Amazon ElastiCache. Define the two engines that are used by Amazon Elasticache. Differentiate between the two engines and the use cases for them. Scaling: Horizontal scaling and Vertical scaling. Replication and Multi-AZ. Backup and recovery. Access control. 10