InUX CollectivebyTakuma Kakehi·Jul 26The seams are where the system livesPartitioning a system into clean modules doesn’t remove complexity — it relocates it to the seams. Cities learned this by zoning. Software…A response icon2
InLevel Up CodingbyRico Fritzsche·Jun 23Microservices Are Not the Next Step After a Modular MonolithWhy Architecture Must Follow Business Needs and Organizational RealityA response icon7
InNetflix TechBlogbyNetflix Technology Blog·May 29From Silos to Service Topology: Why Netflix Built a Real-Time Service MapBy Parth Jain, Rakesh Sukumar, Yingwu Zhao, Renzo Sanchez-Silva & Nathan Fisher How we built a living map of our distributed infrastructure…A response icon13
InGoPenAIbyOndřej Popelka·May 12Documenting architecture of a mid-size chaosWhat I learned building an AI skill to document 1.8M lines of code across 40 repositoriesA response icon3
InLevel Up CodingbyRico Fritzsche·May 14Request Processing Units and ReactorsDecoupling User Interactions from Internal Domain CapabilitiesA response icon3
Gaddam.Naveen·Sep 6Designing a Notification System That Can Handle 10 Million UsersDesign a Notification System at 10 Million UsersA response icon5
InJavarevisitedbyVinod Pal·May 10Why I Defend Monoliths in Every Architecture Review NowEight years of microservices changed my default. Here’s what I learned.A response icon8
The Speedcraft Lab·Aug 17Prime Video cut costs 90% by deleting its serverless architecture. Then the post vanished.The design hit a wall at 5% of expected load. The fix was one process on one box.A response icon27
Arvind Kumar·Jun 26System Design Interview: How Would You Let Users Upload Huge Files Even If the Internet Disconnects…Uploading a file sounds simple.A response icon10
InJavarevisitedbyArvind Kumar·Jun 17System Design Interview: How Would You Prevent a Payment from Being Processed Twice?There are some system design questions that look deceptively simple.A response icon12
Henry YP Ho·Just nowSay yes to the monolith and microservicesHow to build an agentic media platform you can split later
Anithareddy·Just nowMicroservices Are Not Always the Answer: The Architecture Decision Nobody Wants to RevisitWhy choosing a simpler architecture can sometimes be the most sophisticated engineering decision.
Vuteem·2h agoI built a free tool that shows where your system design breaks — with maths, not serversWhiteboard designs never push back. You draw a load balancer, two servers, and a database, someone asks, “What happens at 5,000 requests…
chandrasekhar naidu·3h agoAll Green Before Release. P99 Turns Red in Production?How a burst of traffic turns one integrated API into a money movement bottleneck
Wellington Araújo·5h agoMicroservices Are Not Always the Answer: When a Modular Monolith Makes More SenseMicroservices have become almost synonymous with modern software architecture. When an application grows, one of the first suggestions is…
