Reliability & Delivery · Operational Resilience

Leader Election

Use a lease or distributed coordination mechanism to select one active leader while other instances remain eligible to take over. Leadership must expire safely when the current owner fails.

coordinationleasesingleton
The problem
How can multiple equivalent instances coordinate so only one performs a singleton or supervisory responsibility?
GateSift summary based on Microsoft Azure Architecture Center guidance. The wording, visualization, Azure mapping and analyzer context are original GateSift material.
Original GateSift visualization

How Leader Election works

A distributed lease selects one instance to perform singleton work while others remain available for takeover.

Equivalent instances
Lease election
Active leader
Standby instances
1

Compete for a lease with expiry and a stable owner identity.

2

Allow only the lease holder to perform the coordinated responsibility.

3

Renew leadership while healthy and allow safe takeover when the lease expires.

GateSift explanation

What this pattern helps you decide

Use a lease or distributed coordination mechanism to select one active leader while other instances remain eligible to take over. Leadership must expire safely when the current owner fails.

Which failure mode or capacity limit is this pattern intended to contain?
Which thresholds, deadlines, state or compensation data must remain durable?
How will operators know the pattern activated and whether recovery succeeded?
Common Azure implementations

Where you may see it

  • Azure Blob lease used for singleton coordination
  • Durable task or worker coordination with a distributed lock
  • One active supervisor among multiple background instances
GateSift relevance

How the analyzers can surface it

  • Several schedulers or supervisors acting on the same shared state
  • Singleton work implemented only through local process state
  • Missing lease expiry, fencing or takeover behavior

Pattern detection is contextual. GateSift should present these as architectural signals, not claim a pattern is implemented solely because one policy statement or adapter exists.

Source guidance and attribution

This page links to Microsoft Azure Architecture Center for the source architecture guidance. GateSift summaries, diagrams, Azure examples and analyzer signals are original. No endorsement by Microsoft is implied.

Back to pattern library