Giriteja

Software Engineer @ Google (Adtech) | Building distributed systems at scale | System design— no fluff | 📺 YouTube: BeyondTheInterviews

[Giriteja @mightylone]

@rushil_b_patel It’s not just a problem of javascript , it used to be a problem of every programming language and this has caused many catastrophic failures in real life - more content is on this video -

https://t.co/B23V6CSZUR

[Giriteja @mightylone]

@aayushchugh I explained this behaviour in details with real world examples , give it a watch - https://t.co/B23V6CSZUR

[Giriteja @mightylone]

@Souvik_179 @rohit_negi9 @adityatandon02 @CoderArmy I created the exact content on this - give it a watch let me know your feedback

https://t.co/B23V6CSZUR

[Giriteja @mightylone]

Created a small video on how computers see floating point numbers .

Give it a watch and let me know the feedback or suggestions

https://t.co/B23V6CSZUR

[Giriteja @mightylone]

Created a small video on how computers see floating point numbers .

Give it a watch and let me know the feedback or suggestions

https://t.co/B23V6CSZUR

[Giriteja @mightylone]

2022 — writing code
2023 — copying code from ChatGPT
2024 — prompting AI to write code
2025 — reviewing AI's code
2026 — watching AI write code
2027 — AI watching you

we call this "career progression"

[Giriteja @mightylone]

@kaaaash____ because we all love to deal with real life bugs rather than fixing on imaginary bugs in computers.

[Giriteja @mightylone]

Microservices don't solve complexity.
They move it , from code to infra.

Now you need:

Service discovery → Distributed tracing → API gateways → Eventual consistency
You traded 1 problem for 5.
Start simple. Break it only when you feel the pain.
What are you running?

[Giriteja @mightylone]

@_devJNS if you have to build the same now , you can't even choose a radio option for gender .lol 😂😂

[Giriteja @mightylone]

@GergelyOrosz A junior engineer on day 1 doesn't get prod access. An AI agent shouldn't either.🙂

[Giriteja @mightylone]

@iikypjjyl Fair catch!

No study , it's a hook, not a stat.

The real stat that should matter is how many engineers have actually debugged a cascading failure in prod vs how many have just read about circuit breakers?

My guess? Still a pretty wide gap.

[Giriteja @mightylone]

99% of engineers design systems that work.

1% design systems that survive. The difference isn't intelligence.

It's knowing these 5 failure points that nobody teaches you in interviews, but every senior engineer learns the hard way.

🧵 Thread:

[Giriteja @mightylone]

Failure point #5: Tail latency

Average response: 50ms. Looks great.
P99: 4 seconds.

At 1M requests/day — that's 10,000 users getting a broken experience. Daily. Averages lie.

Dashboards hide this.

Senior engineers watch P95, P99, P999. Not medians.

[Giriteja @mightylone]

Failure point #4: Hot partition

Shard DB by user_id.
One viral user generates 10,000x normal traffic.
That shard melts. Rest sit idle.
Fix: Consistent hashing + virtual nodes.Distribute by request pattern , not just by key. The worst bottlenecks are invisible until prod.

[Giriteja @mightylone]

Failure point #3: Retry storms

Service dies for 10 seconds.

Every client retries instantly.

Service comes back and dies again.

Fix: Exponential backoff + jitter. Not 1s, 2s, 3s. Try 1s, 4s, 16s ... randomized. AWS uses this. Google uses this.

So should you.

[Giriteja @mightylone]

Failure point #2: Thundering herd

Cache expires. 10,000 users hit your DB at the same millisecond. DB collapses.

Fix: TTL jitter. Add randomness to expiry times. Only 1 request rebuilds cache , rest wait.

One line of jitter. Entire system saved.

[Giriteja @mightylone]

Failure point #1
Cascading failures
You design Service A → Service B → Service C.
C slows down. B queues up requests.
A's thread pool fills. Your entire system dies

Fix: Circuit breakers. If C fails N times, stop calling it.
Return a degraded response instead of dying

[Giriteja @mightylone]

How many of you are still doing DSA ?

[Giriteja @mightylone]

Give me the most common graph related question asked by top companies in interviews.

#interviewPreparation #CodingChallenge #dsa

[Giriteja @mightylone]

@nirbhay_74 Seek referral from employees