Search

Adarsh Melath
Adarsh Melath @AdarshMelath__ ·
When one lone server starts to strain, A new design must ease the pain. Break the load, spread the key, A world of shards, for you and me. Dive into how sharding transforms scalability! medium.com/@adarshmelath1… #DatabaseSharding #SystemDesign #Backend
The Digital Expansion: From Single Server to a World of Shards

Imagine you and your friend start a tech company in a small garage. As your product gains users, you begin hiring more employees. At first…

From medium.com
7
PRAJAKTA
PRAJAKTA @prajakta_mane_ ·
Replying to @prajakta_mane_
(no locks, no consensus protocol needed) CRDTs rely on one key property: all operations must be commutative, associative, and idempotent — meaning the order you apply them doesn't matter, and applying the same op twice is safe. This guarantees convergence. #systemdesign
11
StackPilot
StackPilot @TheStackPilot ·
Last seat. Two users. One conflict. ✈️ If your system says “confirmed” twice… you’ve already lost. Here’s how real systems prevent double-booking 👇 #SystemDesign #BackendC
12
srdevopshub
srdevopshub @srdevopshub9 ·
Uber moved from monolith to microservices for scale. Problems with monolith: • Hard to scale • Slow deployments • Single failure risk Microservices benefits: • Independent services • Faster releases • Better reliability #Microservices #SystemDesign #DevOps #Cloud #Tech
1
2
Techlambda Services Pvt Ltd
Techlambda Services Pvt Ltd @blogtechlambda ·
API tip: Don’t let one user crash your system. Use rate limiting: 100 req/min → OK 101 → Block Control traffic = stable systems #Backend #APIs #SystemDesign Read complete blog:- techlambda.com/blogs/technolo…
API Rate Limiting Explained: Protecting Your Backend Systems in 2026

As your application grows, so does traffic. More users = more API requests. But what happens when: Too many requests hit your server? Bots start abusing your APIs? One user consumes all resources?...

From techlambda.com
3
SUBHAM SHAW
SUBHAM SHAW @SUBHAMS27002680 ·
Day 58 of my #SystemDesign series ⚡🛡️ Today: Circuit Breaker Pattern — preventing cascading failures 👇
1
AVINASH SINGH
AVINASH SINGH @avinash_SINGH94 ·
Learning update 🚀 • Studied graphs + solved 2 medium problems • Practiced theory + LC for L1 prep • Cleared L1 interview 🎯 (solved Add Two Numbers on the spot) • Revised CAP theorem & distributed systems basics Gaining confidence daily. #DSA #SystemDesign #BuildInPublivj
1
39
Vipul shetty
Vipul shetty @Vipulshetty7 ·
Everyone says “use microservices.” No one tells you when NOT to. I learned this building a real-time app (Flowspace) Wrote a full breakdown here 👇 shorturl.at/HKpK2M #SoftwareArchitecture #Microservices #SystemDesign #BackendDevelopment #ScalableSystems #BuildInPublic
#softwarearchitecture #microservices #systemdesign #websockets #backenddevelopment #redis #scalab...

Just because Netflix uses microservices doesn’t mean they’re the right starting point. I learned this the hard way while building Flowspace… While building Flowspace (a real-time virtual workspace),...

From linkedin.com
1
5