Welcome back to TechTalks with Manoj — where we stop pretending distributed systems are simple and start designing them like they’re not.

Today’s topic: Cloud Storage—beyond the infinite bucket.

On a slide, storage is the easiest part of the stack. You drag a “bucket” icon, point your app at an endpoint, and assume it’s someone else’s problem. But in production, storage is where data gravity anchors your budget, where IOPS throttling creates ghost latencies in your DBs, and where a “simple” archival strategy turns into a 15-hour waiting game for a single critical file.

We’re going to look at the architectural trade-offs between Azure and AWS that actually impact your uptime. We’ll talk about why S3’s “intelligent tiering” can be a trap for small files, how Azure’s Hierarchical Namespace changes the game for Big Data, and why provisioning storage performance is the one lever that will either save your performance or bleed your bank account dry.

If you’re building systems that have to survive data corruption, massive egress fees, and the brutal reality of multi-petabyte scale—not just a Todo-list demo—this episode is for you.

Let’s get started. 🎙️

Thanks for reading! Subscribe for free to receive new posts and support my work.

Welcome back to TechTalks with Manoj — where we stop pretending distributed systems are simple and start designing them like they’re not.

Today’s topic: message queues beyond the basics.

On diagrams, they look clean — producers, brokers, consumers, done.In production, they’re where consistency breaks, lag grows silently, and “exactly-once” turns out to mean “almost never.”

We’ll talk about delivery guarantees that actually matter, why idempotency is non-negotiable, how the outbox pattern saves you from data corruption, and when exactly-once is worth the cost — and when it absolutely isn’t.

If you’re building systems that have to survive retries, failures, and real traffic — not demos —this episode is for you.

Let’s get started. 🎙️

Thanks for reading! Subscribe for free to receive new posts and support my work.

Welcome back to TechTalks with Manoj — the show where we cut through distributed systems theory and talk about what actually survives production.

Today, we’re diving into Choreography vs Orchestration in microservices.

On paper, choreography promises freedom — no central controller, no bottlenecks, just services reacting to events.In reality, it’s also how teams end up with distributed workflows no one can fully see, trace, or explain at 2 AM.

In this episode, we’ll break down how choreography really works with Sagas, events, and compensation — why the Transactional Outbox is non-negotiable — and when orchestration is still the smarter, more boring, but safer choice.

If you’ve ever wondered where your request actually went, or why your “decoupled” system feels harder to operate every month —this one’s for you.

Let’s get into it. 🎙️

Thanks for reading! Subscribe for free to receive new posts and support my work.