ASAbhijeet Shindeinweeklyupdate.hashnode.dev·20h ago · 10 min readHow HTTP Works: What Happens After DNS Hands You an IP1. Why This Topic Matters The last post ended on a promise: once DNS resolves a name to an IP, what actually happens next? Every post in this series up to now — TCP, UDP, and finally DNS — has been ab00
AAbhishekindesirarman.hashnode.dev·1d ago · 20 min readBuilding a Single-Node Rate Limiter with Redis in Node.jsIntroduction Rate limiting is a way of controlling how frequently a client can access an API. Without rate limiting, a single client could send a large number of requests in a short period of time. Th00
AOAarogya Ojhainaarogyaojha.hashnode.dev·2d ago · 5 min readThe Architecture Decision Everyone OverthinksThere's a moment in almost every growing codebase where someone asks: "should we break this into microservices?" It's usually asked right after a deploy goes wrong, or right after someone reads a blog00
BWBlogs Worldinankitkhoiwal.hashnode.dev·4d ago · 15 min readFrom 102 Queries to 3: A Better Way to Fix Laravel N+1 ProblemsA Laravel page can feel perfectly fast in development and still become painfully slow after real data arrives. That is what makes N+1 problems annoying. They rarely look like bugs. Nothing crashes. No00
ASAbhijeet Shindeinprojectlog.hashnode.dev·5d ago · 6 min readAudio, Subtitles, and the Backend Nobody Sees An update from Building a Distributed Media Platform from ScratchDirect-to-S3 ended with the next piece being background processing — making sure a completed upload reliably becomes a watchable title. This post is that piece, and it turned into more than "reliably 00
DHDeploy Hatchindeployhatch.hashnode.dev·4d ago · 7 min readKeeping Docker Containers Running When a Deployment Worker RestartsWhen you first build a deployment system, it's easy to accidentally tie the lifetime of a workload to the lifetime of the process managing it. A worker starts. It receives a deployment job, builds the00
AVAntoine Valtoninvirtuprobe.hashnode.dev·5d ago · 8 min readHow to Test an Email Verification Flow End to EndAn email-verification feature can return 200 OK and still be broken. The signup endpoint may accept the request while the message is never delivered. The email may arrive with the wrong token. The v10
MMoliyindigitalinfrastructure.hashnode.dev·5d ago · 6 min readHow TradFi Infrastructure Is Becoming More Software-DefinedSubtitleFrom batch settlement and siloed systems to APIs, event-driven workflows, and programmable financial infrastructure. Traditional finance has always depended on software. Banks run on databases00
DJDevanupriy Jainindevanu.hashnode.dev·5d ago · 2 min readBuilding CityScale 🏙️ — Engineering a City-Scale Logistics System What started as an idea to simulate urban parcel distribution turned into CityScale — a full-stack logistics platform for modelling deliveries, locations, routes, and distribution workflows. 🏗️ Archi11D
EGEliran Godovinelirangodov.hashnode.dev·6d ago · 7 min readAccepted Isn't Delivered: What WhatsApp API Status Codes Actually Tell YouIf you've built any kind of WhatsApp automation, you've probably had this moment: your code calls the WhatsApp Business API, gets back an HTTP 200 and a message ID, logs "message sent," and moves on. 00