Bran Kop, Founder and Engineer @Agentise.Me·18h agoI Answered a Question They Never Asked40 minutes of boxes, queues, and retries — and the rejection that finally made sense
Jiyad Ahammad·5d agoDatabase Sharding: when your database gets too big for one machineReplication solves availability and read scale. But what happens when your data itself is too large for any single server? That’s when you…
Nitanshu Joshi·Oct 26AI Engineer Interview Questions — Level 2 (Part 1)Mastering LLM Fine-Tuning, PEFT, and GPU Memory Economics
ADITYA RANJAN·Oct 16System Design for Developers #9: Database Scaling Replication and ShardingWhat to do when one database server isn’t enough (and why you should try everything else first)A response icon1A response icon1
ADITYA RANJAN·Oct 15System Design for Developers #8: Databases SQL vs NoSQLWhich database should you pick, and how do you explain your choice in an interview?
ADITYA RANJAN·Oct 14System Design for Developers #7: Web Servers, Proxies, and Load BalancingYou added more servers. Now who decides which server handles which request?
ADITYA RANJAN·Oct 10System Design for Developers #6: ScalabilityWhat happens when one server isn’t enough: vertical vs horizontal scaling
ADITYA RANJAN·Oct 9System Design for Developers #5: Capacity EstimationHow to turn “10 million users” into real numbers for traffic, storage, and bandwidth
Ashwini T·Oct 4What Nobody Tells You About System Design InterviewsA repeatable process, a worked example, and a four-week practice plan, so “design a system” stops feeling like a trap.A response icon1A response icon1
