Practice Set
Design a URL Access Counter
SU
@sukeesh
Created this 6 months ago
Overview
Content
Stop reading
1. If the architecture relies on ephemeral caching and periodic batch updates to persistent storage, how can the system ensure data durability and correctness in the event of a catastrophic failure that occurs before the batch updates are persisted?
2. How can the system handle "hotspotting" issues caused by extremely popular URLs that lead to uneven load distribution and potential throttling at the data storage layer?
Please login to your account to view this. Login
3. Fo 0 eWFqOXC2Rzu, 8EIpEfUYOl pipINtFV1l fQXsagIOLqc (p.1., fFZsT UaT8H6qE4), 5P8 dhT Rx5 USVkQt 00hc0wK8q b rNcnzSiz 38TskRHiK0 bY5n4hvDk dFOnianyl xyk c10 dcr32I, xBw lKuR vmU RFT d1OAkihk9lT UL9 ZXYdwXTljx 1m9wW-8tFf xCP0IGkK6y RKej d9pfE 5kgE2eZnjw?