Compete for a lease with expiry and a stable owner identity.
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.
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.
How Leader Election works
A distributed lease selects one instance to perform singleton work while others remain available for takeover.
Allow only the lease holder to perform the coordinated responsibility.
Renew leadership while healthy and allow safe takeover when the lease expires.
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.
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
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.
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.