---
title: "Comment by Evelyn Wyatt on \"Fencing Tokens in .NET\" | Hashnode"
description: "One point worth emphasizing is that leader election solves who should act, while fencing tokens enforce who is allowed to commit changes. That separation makes"
url: "https://hashnode.com/posts/fencing-tokens-in-net/6a723685183addc17be0b86b/comment/6a7458a7d81501016f5fb3cf"
---

[Discussion](https://hashnode.com/posts/fencing-tokens-in-net/6a723685183addc17be0b86b)

Comment [Fencing Tokens in .NET](https://hashnode.com/posts/fencing-tokens-in-net/6a723685183addc17be0b86b)

[Evelyn Wyatt](https://hashnode.com/@Evelynwyatt)

[Aug 6](https://hashnode.com/posts/fencing-tokens-in-net/6a723685183addc17be0b86b/comment/6a7458a7d81501016f5fb3cf)

One point worth emphasizing is that leader election solves who should act, while fencing tokens enforce who is allowed to commit changes. That separation makes distributed systems much more resilient because correctness is enforced at the write boundary rather than relying on every node to behave perfectly.

[Patrick Kearns](https://hashnode.com/@fullstackcity)

[Aug 6](https://hashnode.com/posts/fencing-tokens-in-net/6a723685183addc17be0b86b/comment/6a7458a7d81501016f5fb3cf#reply-6a74f4e7460ce63f8aedeac0)

Exactly, a good point. And you can guarantee that anyone that does expect their system to behave as it should all of the time is in for a shock!