├── tapjoy.png
├── addingttl.png
├── expedia.png
├── overview.png
├── summary.png
├── lazyloading.png
├── ticketleap.png
├── writethrough.png
├── elasticacheworking.png
└── README.md


/tapjoy.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/chandu-muthyala/Amazon-ElastiCache/master/tapjoy.png


--------------------------------------------------------------------------------
/addingttl.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/chandu-muthyala/Amazon-ElastiCache/master/addingttl.png


--------------------------------------------------------------------------------
/expedia.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/chandu-muthyala/Amazon-ElastiCache/master/expedia.png


--------------------------------------------------------------------------------
/overview.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/chandu-muthyala/Amazon-ElastiCache/master/overview.png


--------------------------------------------------------------------------------
/summary.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/chandu-muthyala/Amazon-ElastiCache/master/summary.png


--------------------------------------------------------------------------------
/lazyloading.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/chandu-muthyala/Amazon-ElastiCache/master/lazyloading.png


--------------------------------------------------------------------------------
/ticketleap.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/chandu-muthyala/Amazon-ElastiCache/master/ticketleap.png


--------------------------------------------------------------------------------
/writethrough.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/chandu-muthyala/Amazon-ElastiCache/master/writethrough.png


--------------------------------------------------------------------------------
/elasticacheworking.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/chandu-muthyala/Amazon-ElastiCache/master/elasticacheworking.png


--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
  1 | # Amazon-ElastiCache
  2 | 
  3 | ### AWS ElastiCache: 
  4 |   
  5 | ElastiCache is a web service used to deploy, operate and scale in-memory cache in the cloud. Elasticache improve the performance of the web application  by allowing you to retrieve information fast, managed and in-memory data storage  instead of relying entirely on slower disk-storage database.
  6 | 
  7 | <p align="center">
  8 |   
  9 |    <img
 10 |       alt="OverView of AWS Elasticache"
 11 |       src="overview.png"
 12 |       width="600"
 13 |     />
 14 | </p>
 15 | <p align="center">In the deploy, ElastiCache sits between application and data storage</p>
 16 | 
 17 | Elasticache supports two open-source in-memory caching engines.
 18 | 
 19 | 1. **Memcached**: Is an easy-to-use, high-performance, in-memory data store.
 20 | 
 21 | 2. **Redis**: **R**emote **Di**ctionary **S**erver, is a fast, open-source, in-memory key-value data store for use as a database.
 22 | 
 23 | ### How does it work:
 24 | 
 25 | <p align="center">
 26 |     <img
 27 |       alt=" AWS Elasticache Working"
 28 |       src="elasticacheworking.png"
 29 |       width="600"
 30 |     />
 31 | </p>
 32 | 
 33 | **Cache Node**: is the smallest building block of an Elasticache deployment. A node is a fixed size chunk of secured test ram, exists in isolation from or some relationship to other nodes known as cluster. Each node runs in an instance of either **Memcached** or **Redis** depends on which was chosen when you created cluster. Existing applications that use **Memcached** or **Redis** in memory engines can use ElastiCache with almost no modification.
 34 | 
 35 | **Redis**: 
 36 | 
 37 | 1. ElastiCache for Redis is fully managed in an ideal candidate for high performance use cases such as web, mobile app, Gaming, ad-Tech and IoT.
 38 | 2. ElastiCache for Redis can scale up to **90 nodes** per cluster to increase data access performance.
 39 | 
 40 | **Memcached**: 
 41 | 
 42 | 1. Can be preferable for relatively small and static data such as HTML code fragments.
 43 | 2. Memcached comparatively use less memory resources from metadata.
 44 | 3. ElastiCache with memcached can scale up to **20 nodes** per cluster.
 45 | 4. ElastiCache is used to improve the latency and throughput for various applications and compute intensive work loads. 
 46 | 
 47 | ### Caching Strategies:
 48 | 
 49 | Types of caching strategies:
 50 | 
 51 | ***1. Lazy Loading***
 52 | 
 53 | ***2. Write Through***
 54 | 
 55 | ***3. Adding TTL***
 56 | 
 57 | ***Lazy Loading***: Helps in stales the data in ElastiCache, caching Strategy that loads the data into the cache when it is necessary.
 58 |     
 59 |  <p align="center">
 60 |     <img
 61 |       alt=" Lazy Loading"
 62 |       src="lazyloading.png"
 63 |       width="600"
 64 |     />
 65 | </p>
 66 | 
 67 |    - When ever application requests data, first it request for ElastiCache if it exists then ElastiCache return the data to the application.
 68 |     
 69 |    - Otherwise application request data to the data storage and then data storage return data to the application. Then application return that data to the ElastiCache. it will be quickly retrieved for future requests.
 70 |     
 71 | ***Write Through***: Always ensure data is fresh. This Strategy add/updates the ElastiCache when data is written in to the data storage. When spinning up the new node or scaling up node we lost all the ElastiCache data and that scenarios we use Write Through.
 72 | 
 73 | <p align="center">
 74 |     <img
 75 |       alt=" Write Through"
 76 |       src="writethrough.png"
 77 |       width="600"
 78 |     />
 79 | </p>
 80 | 
 81 | ***Adding TTL***: Using this Strategy we can minimise the space in ElastiCache.
 82 | 
 83 |    - Time to live key Strategy for each cache node to how long data present in the ElastiCache.
 84 |    
 85 |    - When application try to request the data which already expires, ElastiCache will return data not found and try to fetch from the data storage. 
 86 | 
 87 | <p align="center">
 88 |     <img
 89 |       alt=" Adding TTL"
 90 |       src="addingttl.png"
 91 |       width="600"
 92 |     />
 93 | </p>
 94 | 
 95 | ### Use Cases:
 96 | 
 97 | ***1. Expedia***: **Reduce Data Store Costs**
 98 | 
 99 | <p align="center">
100 |     <img
101 |       alt=" Expedia"
102 |       src="expedia.png"
103 |       width="600"
104 |     />
105 | </p>
106 | 
107 | ***2. TicketLeap.com***: **Absorb Rapid Traffic Growth**
108 | 
109 | <p align="center">
110 |     <img
111 |       alt=" TicketLeap"
112 |       src="ticketleap.png"
113 |       width="600"
114 |     />
115 | </p>
116 | 
117 | ***3. TapJoy***: **Decrease mobile app latency**
118 | 
119 | <p align="center">
120 |     <img
121 |       alt="TapJoy"
122 |       src="tapjoy.png"
123 |       width="600"
124 |     />
125 | </p>
126 | 
127 | ### Summary:
128 | 
129 | <p align="center">
130 |     <img
131 |       alt="Summary"
132 |       src="summary.png"
133 |       width="600"
134 |     />
135 | </p>
136 | 
137 | ### References:
138 | 
139 | 1. [https://aws.amazon.com/elasticache/](https://aws.amazon.com/elasticache/)
140 | 2. [https://aws.amazon.com/redis/](https://aws.amazon.com/redis/)
141 | 3. [https://aws.amazon.com/memcached/](https://aws.amazon.com/memcached/)
142 | 4. [https://www.aws.training/Details/Video?id=16348](https://www.aws.training/Details/Video?id=16348)
143 | 


--------------------------------------------------------------------------------