Ritesh Roushan

Backend Interview Question: Which API design scales better? What's your choice?

@Aditya_181105 Nope, Claude is legend

be honest, As a developer Is there any replacement better than Claude for coding ??

@tanujDE3180 Cursor based pagination Here is detailed explanation about pagination too devxritesh.medium.com/api-database-d…

A. GET /posts?page=10000 B. GET /posts?cursor=eyJpZCI6... One of these works fine at 1 million rows. The other still works at 1 billion rows. Which one are you choosing for scale ?

@Samaytwt I don't have problem, will switch domain

Vibe coders, what’s your backup plan if Ai writes better code than you in the next 1–2 years?

Most people answer: A) Database That's usually wrong. The first thing that fails is often the cache. Here's why 👇 1. Celebrity posts a tweet 50M followers. Millions immediately refresh. Everyone requests the same tweet. 2. Cache Miss Storm If the tweet isn't cached yet: Millions of requests hit Redis simultaneously. This is called a cache stampede. Suddenly: • Redis CPU spikes • Network saturation increases • Database gets hammered 3. Database Becomes the Next Victim After cache misses: - Millions of requests fall back to the database. - Now the database becomes overloaded. - Not because it's slow. Because the cache stopped protecting it. 4. How X/Twitter Handles This Request Flow: User ↓ CDN ↓ Load Balancer ↓ API Gateway ↓ Redis Cache ↓ Database Most reads never reach the database. 5. Celebrity Problem Normal users: - Fan-out on Write - Tweet gets pushed to follower timelines. - Fast reads. Celebrity users: - Fan-out on Read - Store the tweet once. - Generate timelines dynamically. Otherwise you'd write tens of millions of timeline entries. 6. Protection Layers • Redis caching • CDN edge caching • Request coalescing • Rate limiting • Read replicas • Queue-based timeline generation Production lesson: The database isn't usually the first thing that fails. The system fails when too many requests bypass the cache. Protect the cache. The cache protects everything else.

@ash_twtz Compatible and handy

@devXritesh Why that one ?

iPhone Models and Their Release Year • 🍏 iPhone - 2007 • 🌐 iPhone 3G - 2008 • 🚀 iPhone 3GS - 2009 • 💎 iPhone 4 - 2010 • ⭐ iPhone 4S - 2011 • 🎵 iPhone 5 - 2012 • 🌈 iPhone 5c - 2013 • 👑 iPhone 5s - 2013 • 📘 iPhone 6 - 2014 • ➕ iPhone 6 Plus - 2014 • ✨ iPhone 6s - 2015 • 🏆 iPhone 6s Plus - 2015 • 🎯 iPhone SE - 2016 • 🎧 iPhone 7 - 2016 • 📷 iPhone 7 Plus - 2016 • 🔋 iPhone 8 - 2017 • ⚡ iPhone 8 Plus - 2017 • 🔟 iPhone X - 2017 • 🌈 iPhone XR - 2018 • 💫 iPhone XS - 2018 • 🦅 iPhone XS Max - 2018 • 📸 iPhone 11 - 2019 • 🎬 iPhone 11 Pro - 2019 • 🚁 iPhone 11 Pro Max - 2019 • 🎯 iPhone SE (2nd generation) - 2020 • 🤏 iPhone 12 mini - 2020 • 🧲 iPhone 12 - 2020 • 💠 iPhone 12 Pro - 2020 • 🏅 iPhone 12 Pro Max - 2020 • 🪶 iPhone 13 mini - 2021 • 🎥 iPhone 13 - 2021 • 💎 iPhone 13 Pro - 2021 • 🚀 iPhone 13 Pro Max - 2021 • 🎯 iPhone SE (3rd generation) - 2022 • 🟣 iPhone 14 - 2022 • 🌟 iPhone 14 Plus - 2022 • ✨ iPhone 14 Pro - 2022 • 👑 iPhone 14 Pro Max - 2022 • 🔌 iPhone 15 - 2023 • 🌊 iPhone 15 Plus - 2023 • 🛸 iPhone 15 Pro - 2023 • 🏔️ iPhone 15 Pro Max - 2023 • 🤖 iPhone 16 - 2024 • 🌌 iPhone 16 Plus - 2024 • 🔥 iPhone 16 Pro - 2024 • 🐉 iPhone 16 Pro Max - 2024 • 💎 iPhone 16e - 2025 • 🪶 iPhone Air - 2025 • 🎉 iPhone 17 - 2025 • 🌠 iPhone 17 Pro - 2025 • 🏰 iPhone 17 Pro Max - 2025 • 🆕 iPhone 17e - 2026 Which iPhone is your favorite?

Read this for cache strategy in detail devxritesh.medium.com/caching-strate…

@neerajjj6785 Thanks bro 😊

@devXritesh Solid breakdown

@kunal_twts Yeah, cache is first to hit after heavy traffic

@devXritesh The first hit point is the cache

@neerajjj6785 Someone saying CSS is programming language 🤣

@kunal_twts They are gonna mad wth 😒

How many can do a POST request ?🙂

@ravikiran_dev7 @grok Why mark not @grok

Hey @grok remove the most evil and controversial entrepreneur from this image!

@SahilExec Exactly, after cache db will be next

@devXritesh So the cache is the real hero here, protecting the database from a stampede of requests

@SahilExec This regex is a classic ReDoS bomb "a@aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa..." will nuke your CPU.

A junior dev validates emails like this: Works perfectly for valid emails. What's the hidden vulnerability and how does an attacker use it to take down your server?

@realpvarma Loyal one more worthy

Unpopular opinion: A small audience can be worth more than a big resume.

@begade_suhas Ofcourse Suhas Let's do it, done from My side 🤝

@devXritesh Mind if we join on x?? 😉😉

System Design Question: You're designing Uber. A ride is completed. You need to update: • Billing • Driver Earnings • Notifications • Analytics What's your first choice? A) REST B) Message Queue Explain your reasoning 👇

@SakshiSugandhi User name protect the users data, we can't reveal like this.

@devXritesh Why not 🤔

Hot take: Username field is unnecessary. Change my mind.

@vivoplt Just imagine after improving this game

The last game built by Claude Fable 5.

@0xPrajwal_ Snapdragon for mobile phones and apple sillicon for laptop

Be honest, which processor is actually the best?