MSDEVBUILD Azure The queue was in order. Your workers were not. A customer paid $120 for an item they removed, and Service Bus did nothing wrong.
- · That FIFO delivery and FIFO processing are different things, and concurrency is what separates them
- · Why SessionId is a partition-key choice, not a yes/no on ordering
- · The one setting that silently gives back the race after you enable sessions
Azure · 12 steps
MSDEVBUILD Azure The outage lasted 18 minutes. Your retries lasted 4 seconds. 720 good orders in the dead-letter queue, and not one of them was poison.
- · Why ten redeliveries take about four seconds, not four minutes
- · That MaxDeliveryCount caps attempts and says nothing at all about time
- · How to build the backoff Service Bus does not give you, with ScheduledEnqueueTimeUtc
Azure · 12 steps
MSDEVBUILD Azure The agent worked fine. It cost $4,260. Nothing failed. The loop just paid for its own history, twelve times per task.
- · Why an agent loop’s input tokens grow with the square of its step count
- · What prompt caching actually charges — reads at 0.1×, writes at 1.25×
- · The one line that silently stops the cache being read, with no error
Azure · 12 steps
MSDEVBUILD Azure You tapped View Product. Five Azure services answer before the page paints. Here is the order they run in.
- · Why the edge answers first and your API never hears about a cache hit
- · What cache-aside actually does on a Redis miss, including the write-back
- · Why product images take a different path and never reach your API
Azure · 12 steps
MSDEVBUILD Azure A rack just lost power. The shop kept selling. Why Azure places your VMs on different physical racks, and what breaks the moment it does not.
- · What a rack shares — one power feed, one switch, one blast radius
- · How an availability set spreads VMs across fault domains for you
- · Why two VMs in the same fault domain is not redundancy
Azure · 16 steps
MSDEVBUILD Azure Azure rebooted the server. The bank never noticed. How update domains let Microsoft patch the hosts under your VMs without dropping a single customer.
- · How Azure reboots hosts one update domain at a time
- · Why the load balancer always has a healthy VM to use
- · Update domain versus fault domain, in one line
Azure · 16 steps
MSDEVBUILD Azure Azure is rebooting your server. Nobody notices. How an Azure Availability Set keeps an online shop selling straight through planned server maintenance.
- · Why one VM cannot survive Azure patching the host under it
- · How an availability set spreads VMs across fault and update domains
- · What the load balancer health probe does during a reboot
Azure · 14 steps
MSDEVBUILD Azure One server goes down. Nobody can buy anything. How Azure Availability Zones keep an Amazon-scale shopping app online while an entire datacenter fails.
- · What a single-server outage actually costs a shopping app
- · How three zones in one region are physically separate buildings
- · Why sub-2 ms replication turns 99.9% into 99.99%
Azure · 10 steps
MSDEVBUILD Azure What is MCP? Model Context Protocol — how an AI assistant reaches GitHub, your database, your files and Slack.
- · Why a model on its own cannot reach GitHub, SQL or Slack
- · How an MCP client and server carry one request down and back
- · Why M + N connectors beats M × N bespoke integrations
Azure · 8 steps
MSDEVBUILD copilot LLMs have no memory So how does Copilot know your code? It never remembers. It re-reads, re-ranks and re-sends your context on every single request.
- · Why the model holds nothing between two requests
- · How your editor rebuilds the whole prompt every time
- · What competes for the same fixed token budget
GitHub Copilot · 9 steps
MSDEVBUILD Azure From a model to a shipped AI product Azure AI Foundry is the platform Microsoft built for the part everyone underestimates — everything after the demo.
- · Why the demo works and the product still does not ship
- · How one Foundry project holds the model, your data and the agent
- · What to evaluate and filter before a release, not after
Azure · 8 steps
MSDEVBUILD Azure Your Durable Function runs many times The orchestrator body re-executes from line one, over and over, until every step is answered.
- · Why an orchestrator body re-executes from line one, many times
- · How completed activities are answered from the event history
- · Why DateTime.Now and Guid.NewGuid break a Durable Function
Azure · 8 steps
MSDEVBUILD Design Pattern Netflix does not stream from Netflix The video you watch tonight is already sitting inside your internet provider.
- · Why the video almost never comes from Netflix’s own datacentres
- · How the control plane answers play with a ranked manifest
- · How Open Connect boxes inside your ISP are filled overnight
Architecture · 8 steps
MSDEVBUILD Python In Python, a name is a sticker, not a box Two names can sit on one object. Whether it can change is what makes lists and strings behave differently.
- · Why b = a is a second name, not a copy
- · Which Python types change in place and which are replaced
- · How the mutable default argument bug gets written
Programming · 8 steps
MSDEVBUILD Azure A call needs both people free. A message does not. Sync versus async, decided by one question — and priced honestly.
- · 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
MSDEVBUILD Azure Two Azure queues. Which one do you pick? Five questions that settle it, and the one where the cheap option wins.
- · The five questions that decide which Azure queue you need
- · Where Queue Storage stops: no topics, no sessions, 64 KB
- · Why the cheap queue is the right call for most background work
Azure · 10 steps
MSDEVBUILD Azure Somebody said “we need Kafka”. A broker and a log are not two brands of the same thing.
- · The real difference between a broker and an append-only log
- · Why Kafka partitions put a ceiling on your consumer count
- · When the Event Hubs Kafka endpoint is the cheaper answer
Azure · 10 steps
MSDEVBUILD Azure The sale opened. The orders vanished. What a queue actually does to a traffic spike your server cannot absorb.
- · What a flash sale does to an order API with nothing in front of it
- · How a queue decouples arrival rate from processing rate
- · Why an uncompleted message comes back without a retry loop
Azure · 10 steps
MSDEVBUILD Azure The gateway timed out. Where did the payment go? Retries, delivery counts and the queue Azure fills for you whether you read it or not.
- · Why you never complete a message you cannot confirm
- · How delivery count and MaxDeliveryCount stop an endless retry
- · What lands in the dead-letter queue, and what to alert on
Azure · 10 steps
MSDEVBUILD Azure Security said no inbound ports. How the cloud reaches a server it is not allowed to connect to.
- · How the cloud reaches an on-prem service with no inbound port
- · Why the private side dials out to a rendezvous point instead
- · When Relay beats a VPN, and when a queue beats both
Azure · 10 steps
MSDEVBUILD Azure You picked the topic. Then it filled up. Five Service Bus traps that only show themselves six months later.
- · How the $Default rule keeps matching everything you filtered
- · Why one idle subscription fills the topic and pages the publisher
- · The five settings that prevent all of it, none of them code
Azure · 10 steps
MSDEVBUILD Azure The upload froze the app for 8 seconds. The fix is the cheapest queue Azure sells, and a pointer instead of a payload.
- · Why image processing inside the request exhausts the web tier
- · The claim check: put a blob path on the queue, not the file
- · How visibility timeout and DequeueCount handle a dead worker
Azure · 10 steps
MSDEVBUILD Azure Three teams. One queue. Everyone missed messages. A queue is a DM. A topic is the group broadcast. The difference is a real bug.
- · Why three teams on one queue each get a third of the messages
- · How competing consumers differ from real subscribers
- · What a subscription gives you that a second reader never will
Azure · 10 steps
MSDEVBUILD Azure One push. A million phones. Why looping over device tokens is the answer that fails the interview.
- · Why a loop over a million device tokens finishes too late
- · How one send becomes APNs, FCM and WNS payloads
- · How tag targeting replaces holding device tokens yourself
Azure · 10 steps
MSDEVBUILD Azure 15,000 GPS pings a second. Do not put that in a queue. Partitions, offsets and the reason four teams can read the same event.
- · Why a queue cannot hand the same event to four teams
- · How a partition key keeps one driver’s pings in order
- · How consumer groups and offsets let a slow reader catch up
Azure · 10 steps
MSDEVBUILD Azure Everyone confuses these two. One is a doorbell. The other is a tape you can rewind.
- · The doorbell-or-tape question that settles which one you need
- · Push with retries versus pull with offsets and retention
- · Why a real pipeline usually ends up using both
Azure · 10 steps
MSDEVBUILD Azure One order. Four teams need to know. Why the fourth subscriber is the only argument for Event Grid that matters.
- · Why checkout should not call email, stock and shipping itself
- · How subscriptions and filters fan one event out to four teams
- · What Event Grid retries before a delivery is dead-lettered
Azure · 10 steps
MSDEVBUILD Azure The queue drained. Nothing was consuming it. One Service Bus default, six hours, and 4,318 orders that never existed.
- · How a message TTL deletes orders with no error and no log line
- · Why a queue draining with no consumer is deletion, not recovery
- · The three queue properties and one alert that would have caught it
Azure · 10 steps
Nothing matches that. Try a different term, or clear the category filter.
