Tag feed

#system-design-interview

32 posts7 followers

Explore Hashnode

Alternatives

Trending tags this week

IAI am Developeriamdevelopr.hashnode.dev19h ago · 6 min read

CAP Theorem Explained

So these days, I’ve been learning about system design to practice and brush up on my skills, and also to refresh my memory of how complex systems—or even any system—work under the hood. System design

0

KRKashif Rezaarchitecture-in-practice.hashnode.devSep 8 · 7 min read

Handling Duplicate Events Safely with Idempotency

In the previous article, we looked at retries and DLQ. Retries help you recover from temporary failures. But they also create a new risk: The same event may be delivered, retried, or processed more t

0

KRKashif Rezaarchitecture-in-practice.hashnode.devSep 7 · 8 min read

Retry Strategy in Event-Driven Systems: Resilience or Retry Storm?

Retries usually start with good intent. Typical transient failures in distributed systems A network call times out.A database becomes slow.A downstream API is unavailable. These are not edge cases. T

0

LDLakshay Dhoundiyallakshaydhoundiyal.hashnode.devSep 4 · 10 min read

How 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 inst

0

SDsanhita dawnscaledojo.hashnode.devJul 17 · 6 min read

I Built 15 System Designs on Paper and Still Failed My First Interview. Here's What Actually Fixed It.

Understanding system design and being able to build one turned out to be two very different skills. For three months, I did everything the guides told me to do. I read the System Design Primer front t

0

SMScott McMahanaitransformeronline.hashnode.devJul 15 · 2 min read

How AI Can Help You Succeed in System Design Interviews

System design interviews challenge candidates to think through complex engineering problems involving scalability, reliability, performance, security, and maintainability. Success depends on your abil

0

AAArslan Ahmadsystemdesigndg.hashnode.devJun 28 · 11 min read

What Interviewing 1,000+ Engineers at Meta and Microsoft Taught Me About System Design Rounds

I have sat on the other side of the table for more system design interviews than I can count. At Meta and Microsoft, across hiring committees and debrief rooms, I watched brilliant engineers walk out

0

AAArslan Ahmadsystemdesigndg.hashnode.devJun 21 · 15 min read

A 60-Minute Daily Routine for Learning System Design

Most engineers do not struggle with system design because they lack intelligence. They struggle because system design feels too broad. One day, you are learning caching. The next day, you are reading

0

AAArslan Ahmadsystemdesigndg.hashnode.devJun 21 · 11 min read

Grokking System Design: Caching, Sharding, Replication, and Load Balancing Explained

Every large system you use rests on a handful of core ideas. Strip away the brand names and the buzzwords, and you keep running into the same four. Caching, load balancing, replication, and sharding.

0

HGHarrison Guoharrisonsec.hashnode.devMay 14 · 18 min read

Channels Aren't Message Passing — How Parked Goroutines OOM-Killed a Pod

It's 3am. The Kafka consumer pod that's been running cleanly for six weeks gets OOM-killed. Kubernetes restarts it. Five minutes later: OOM-killed again. Restart. OOM-killed a third time. By the fourt

0

#system-design-interview

Search Hashnode

#system-design-interview

Explore Hashnode

Trending tags this week

CAP Theorem Explained

Handling Duplicate Events Safely with Idempotency

Retry Strategy in Event-Driven Systems: Resilience or Retry Storm?

How Does Gmail Know a Username Is Already Taken in Milliseconds?

I Built 15 System Designs on Paper and Still Failed My First Interview. Here's What Actually Fixed It.

How AI Can Help You Succeed in System Design Interviews

What Interviewing 1,000+ Engineers at Meta and Microsoft Taught Me About System Design Rounds

A 60-Minute Daily Routine for Learning System Design

Grokking System Design: Caching, Sharding, Replication, and Load Balancing Explained

Channels Aren't Message Passing — How Parked Goroutines OOM-Killed a Pod