# Shashi Madappa - Ephemeral Volatile Caching in the Cloud (Highlights)  ## Metadata **Review**:: [readwise.io](https://readwise.io/bookreview/61937608) **Source**:: #from/readwise #from/reader **Zettel**:: #zettel/fleeting **Status**:: #x **Authors**:: [[Shashi Madappa]] **Full Title**:: Ephemeral Volatile Caching in the Cloud **Category**:: #articles #readwise/articles **Category Icon**:: 📰 **Document Tags**:: #work **URL**:: [netflixtechblog.com](https://netflixtechblog.com/ephemeral-volatile-caching-in-the-cloud-8eba7b124589) **Host**:: [[netflixtechblog.com]] **Highlighted**:: [[2026-07-08]] **Created**:: [[2026-07-11]] ## Highlights - AWS Zone-Aware and data can be replicated across zones. ([View Highlight](https://read.readwise.io/read/01kx1xtw2napypvkmjaqmd89a2)) ^1032721122 - This is a Best Effort Cache and the data can get inconsistent. The architecture we have chosen is speed instead of consistency and the applications that depend on EVCache are capable of handling any inconsistency. ([View Highlight](https://read.readwise.io/read/01kx1y0ht8gst88ahhaembe26z)) ^1032721241 - A Java client discovers EVCache servers and manages all the CRUD[3] (Create, Read, Update & Delete) operations. The client automatically handles the case when servers are added to or removed from the cluster. The client replicates data (AWS Zone[5] based) during Create, Update & Delete Operations; on the other hand, for Read operations the client gets the data from the server which is in the same zone as the client. ([View Highlight](https://read.readwise.io/read/01kx1y3vca9m97t1zdn0j64qkp)) ^1032721340 #takeaway - When the Web App in Zone-A needs to Write or Delete the data for a key, the EVCache client looks up the EVCache Server instances in Zone-A and Zone-B and writes or deletes it. ([View Highlight](https://read.readwise.io/read/01kx1y9apvpcm8ka5hczetvh0e)) ^1032721585