The Desi Architect

🚨 Sharding Part 2 is coming very soon.

But before we break things in a real PostgreSQL setup, make sure your Part 1 theory is fresh. 😄

We covered the fundamentals you’ll need to understand the practical demo:

Shard Key → Hashing → Consistent Hashing

Because in Part 2, we’re taking this from diagrams to a real Postgres setup and seeing what actually happens when you add a new shard.

There’s going to be a failure.

An unexpected MISS.

And then we’ll fix it.

👉 Watch / revise Part 1 here:
https://youtu.be/7AmI28FPTz0

Part 2: Practical Sharding Demo, coming very soon.

If you haven't watched Part 1 yet, now is the time. 👀

#SystemDesign #Sharding #PostgreSQL #SoftwareArchitecture #DesiArchitect

1 day ago | [YT] | 8

The Desi Architect

A small preview of what paid community members get with every video.

If you have not watched Part 1 of the MCP vs API series yet, watch it here first:
https://youtu.be/VpHbxLo47QM

Every video on this channel gets a companion document. It is not a transcript and it is not a summary of the video.
It is a written guide that goes deeper than a 15 minute video can, plus working code you can actually copy into your own project.

Here is a preview of what that document looks like for this one:
drive.google.com/file/d/1z33J97dlUlTiBfiQs9gy9q_Jp…

It is a 23 page guide called "API, Function Calling and MCP". Here is what is inside:

- The one idea that actually explains the difference between the three, instead of three definitions that all sound the same
- A simple 3 question framework to decide which one your project needs, worked through step by step on a real example
- A trade off table comparing all three on coupling, latency, security, cost and how hard each one is to debug
- Five failure modes that show up after you ship, not during the demo, including the full explanation of the exact bug from the video
- Sample code for all three patterns in Java, .NET and Node, so you can see how this actually looks in the stack you use
- A short checklist you can run against your own system before you ship any of this

This is the level of detail every paid community member gets with every video.

If this is useful to you, you can press the JOIN button and join the community.

1 week ago | [YT] | 5

The Desi Architect

You’ve learned the tools. But what’s your proof? 👀

Kubernetes. System design. Architecture diagrams. Technical docs.

You can learn all of them and still not know whether you’re actually progressing toward becoming a Software Architect.

So I built a simple 5-level framework:

1️⃣ Frame the Problem
2️⃣ Design Options
3️⃣ Quantify the Decision
4️⃣ Own Production
5️⃣ Influence Decisions

The interesting part?

You can use these levels to figure out exactly where you stand today.

If you haven't watched it yet, this is the video I’d recommend watching next:

👉 Developer to Architect: The 5 Levels (Which One Are You?)

https://youtu.be/AzD5ZYtoNf8

After watching, comment your level: 1, 2, 3, 4, or 5.

Let's see where most developers actually stand. 👇

2 weeks ago | [YT] | 21

The Desi Architect

Have you watched “Backend Dev? You’re Already 70% AI Engineer” yet?

If not, this one is worth checking out. 👇

The video explains why backend developers already have many of the skills needed for AI Engineering.

Instead of just giving you a list of Python → RAG → Agents → LangChain, we build one system and see what breaks in production.

You’ll see why RAG, Evals, Observability and Tool Calling are needed through real problems, not just definitions.

📄 I’ve also shared a free 90 day AI Engineer roadmap PDF in the pinned comment.

4 weeks ago | [YT] | 17

The Desi Architect

🚨 What actually breaks when your system goes from 1M → 10M users?

It’s NOT always your application servers.

At 10M users, you start running into very different problems:

→ Database bottlenecks
→ Read vs. write scaling
→ Hot keys & cache stampedes
→ Read replicas & sharding
→ Async processing
→ And the biggest mistake: adding microservices too early

The real architect question isn’t:

“How do I handle 10M users?”

It’s:

“What are those 10M users actually doing?”

I’ve broken down the complete scaling journey — from 1M → 10M users with the architecture decisions, bottlenecks, and trade-offs you need to understand.

🎥 Watch the full video:
[Scaling 1M to 10M Users: What Breaks First | System Design](https://youtu.be/u36KhE2dgz4)

And a huge shoutout to our Pro Architect community members for supporting the channel ❤️

🙏 @debasishchakraborty4196
🙏 @vikramgandhi79
🙏 @MsDivik
🙏 @deepaar9171

Your support helps me keep creating deep, practical System Design content for engineers.

Scale the bottleneck. Not the architecture.

What do you think breaks first at 10M users? 👇

Skip the Carousel

1 2

1 month ago (edited) | [YT] | 7

The Desi Architect

🚀 Next System Design video is coming soon!

Before it drops, this is a good time to revise our previous architecture journey:

Scaling from 1 User to 1M Users: Real Architecture Journey
👉 https://youtu.be/sXohJ3pYAfI

The next video picks up from where this one left off and this time, we’re taking Tadka from 1M to 10M users.

But here’s the catch:

At 10M users, simply adding more servers is not enough.

Sharding? Redis? Microservices?

We’ll make each decision only when the system actually needs it.

Problem first. Technology later.

Coming soon. 🔥

1 month ago | [YT] | 4