MCMatteo Collinainblog.platformatic.dev·3d ago · 10 min readIntroducing @platformatic/memcachedmemcached has been a reliable cache for more than twenty years and still competes with newer options. It’s a simple, in-memory key/value store with very low latency, no background threads, and just on00
LDLakshay Dhoundiyalinlakshaydhoundiyal.hashnode.dev·6d ago · 10 min readThe Hidden Distributed System Behind YouTube’s “Continue Watching” Button 🎬⚙️Imagine this. You’re watching a YouTube video about system design. The explanation is getting interesting. The speaker has just started discussing database sharding. You pause the video at 08:37. Life20
BKBOBBY KUMARinthe-engineers-notebook.hashnode.dev·6d ago · 9 min readWhen Personalization Meets the EdgeA modern application might need to show different experiences to different users. The same URL could display developer-focused content for one user, business-focused content for another, or different 00
BKBOBBY KUMARinthe-engineers-notebook.hashnode.dev·Sep 5 · 10 min readCaching: It Isn't Just a Performance ProblemWhen an application gets slower, one of the first solutions we think about is - "Let’s cache it." And often, that’s the right answer. Instead of doing the same expensive work for every request, we can00
LDLakshay Dhoundiyalinlakshaydhoundiyal.hashnode.dev·Sep 4 · 10 min readHow Does Gmail Know a Username Is Already Taken in Milliseconds?You type a username. Maybe it is something simple like example123@gmail.com. Before you have even finished thinking about it, the signup page responds: “Username already taken.” ❌ It feels almost inst20
PKPRINCE KUMARinprincekumar-engineer.hashnode.dev·Aug 30 · 28 min readBuilding Scalable Systems: Caching, Rate Limiting and ObservabilityWhat happens when your application suddenly gets 1 million users? At small scale, a web application can look deceptively simple: User → Application → Database → Response As traffic grows, however, ev00
BKBOBBY KUMARinthe-engineers-notebook.hashnode.dev·Aug 29 · 7 min readThe Journey of a Request in a Next.js ApplicationWhen we build a frontend feature, we often think about what happens after the page reaches the browser. We think about components. Page ├── Header ├── ProductList ├── ProductCard └── Footer But w00
SKShivam Kumarinshivamshrma09.hashnode.dev·Aug 28 · 27 min readDeep dive into Database scaling and cachingWhy databases are the bottleneck Out of every component in a system, the database is usually the one that makes or breaks it. Your app servers are stateless, so you can spin up ten more of them in a m00
JSJaveed Shaikinfreecodecamp.org·Aug 27 · 9 min readI Added a CDN Cache to My Site and It Got Slower. Here's the Math I Should Have Done First.Last week I put a CDN cache in front of a static site, expecting it to get faster. But instead, it got measurably slower. Not subtly: an independent crawler that had flagged 38 slow pages before the c00
VSVinícius S. de Pontesinvsdepontes.com·Aug 21 · 5 min readDistributed Memoization: Avoid Repeating Expensive WorkSome operations produce the same output when given the same input. Without caching, every request still reaches the service, accesses its dependencies, and performs the same work again. This happens e62LI
