Caching

.....

Like the course? Get enrolled and start learning!

Asim Bhatti

· a year ago

testing1 content

Show 1 reply

Anonymous

· 3 years ago

Use read aside caching when optimizing read performance is the primary concern and use read-through caching when ensuring data consistency between the cache and backend storage is critical.

Choose write-through caching when data consistency is critical, write-back caching when write performance is paramount and some data loss or inconsistency can be tolerated, and write-around caching when write operations are infrequent or when certain data should not be cached.

Anonymous

· 4 years ago

LIFO cache eviction policy is wrong. You evict the newest added cache entry regardless of how recently it was accessed. Your incorrect definition mixes up LIFO with MRU

Show 1 reply

Anonymous

· 4 years ago

If the system we are building is not large enough to have its own CDN, we can ease a future transition by serving the static media off a separate subdomain (e.g., static.yourservice.com) using a lightweight HTTP server like Nginx, and cut-over the DNS from your servers to a CDN later.

So how does this help exactly? Isn't this just sending requests to a back-end server? Is that idea that having all of your static media on a dedicated back-end somehow faster than having both your static stuff and other stuff on the same back-end?

Anonymous

· 4 years ago

Write-around cache: This technique is similar to write-through cache, but data is written directly to permanent storage, bypassing the cache

So how does this solve cache invalidation problem?

Show 2 replies

Anonymous

· 5 years ago

Under this scheme, data is written into the cache and the corresponding database simultaneously.

How is this done in practice? I know that DDID references XA being one approach. Are there others?

Reading Progress

Vote for new content