Suthahar Jegatheesan MSDEVBUILD / blog Multi-Stack Dev Build · by Suthahar
Search
Azure

A call needs both people free. A message does not.

Sync versus async, decided by one question — and priced honestly.

What you'll learn

  • How three chained dependencies become your own downtime
  • Why going async turns an outage into lag instead
  • The three jobs you inherit the moment you queue it
Azure 10 steps 32 seconds —views

Was this useful?

Share

Understand it one step at a time

The short runs these in order in about 32 seconds. Here they are written out — pick any step to jump the short straight to it.

1 Step 1 of 10

Same request, two designs

Checkout has to tell the shipping service about a new order. That single requirement has two completely different implementations.

Frequently asked questions

Why does a chain of synchronous calls become your own downtime?
Each call in the chain has to wait for the one before it to answer, so if any dependency is slow or down, that failure propagates straight back to the caller — your service inherits the availability of every service it called synchronously.
Does going async remove the failure, or just change what it looks like?
It changes it — a dependency outage becomes lag in the queue instead of a failed request, which is real availability gained. In exchange you inherit three jobs a synchronous call never had: retries, ordering and knowing when work is actually done.

Free app · no app store

These are built for a phone

Every short is drawn at full portrait height, the shape a phone already is. Installed, it opens full-bleed with no address bar across the top — and the whole library reads offline.

How it works

Read deeper on Azure

Twenty seconds gets the shape of an idea across. These go into how it behaves in production.

More shorts

Get new posts by email

New technical articles, Azure AI and GitHub Copilot updates, and upcoming events. No spam, unsubscribe anytime.

↑↓ navigate ↵ open