← Project archiveFEATURED QUEST · sanitized

Registration Pipeline Redesign

Replacing a blocking queue with parallel event-driven work

My role
Architect & implementer
Measured outcome
45+ min → ~5 sec
  • Azure Service Bus
  • Azure Functions
  • SQL Server
  • Event-driven architecture
PROLOGUE

A registration redesign built around parallel work and eventual reconciliation.

Registration was a chain where every user could wait behind everybody else: identity uploads, card registration, device setup, checks and activation all competed for the same path. Under contention, the queue could exceed 45 minutes.

The breakthrough was accepting that most of that work did not belong in the synchronous user journey.

I

What I walked intoThe setup

Sequential stages and SQL contention could make registration exceed 45 minutes.

II

How I untangled itThe turning point

Independent work moved behind Azure Service Bus and Functions. The user waits only for essentials; background work reconciles later.

01Registration request
02Service Bus
03Parallel Functions
04Eventual reconciliation
05Activated account
III

What changedWhere it landed

Approximate user-visible blocking fell from 45+ minutes to about 5 seconds, with horizontally scalable workers.