Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderAt work we use Temporal and ended up using a dedicated workflow and signals to do distributed locking. Working well so far and the implementation is rather simple, relying on Temporal’s facilities to do the distributed parts of the lock.
In Azure, we solve this with leasing blobs and always renewing, and additionally checking ETags when writing.
Please note that I replied to this blog post, when it was published. You may be interested in reading the counter arguments. The author of the original post acknowledged that at least one of his claim was wrong, but I don't know if they modified the post later. Anyway we gained some time perspective, too: Redlock was massively used in the last 10 years, and I have never heard of its properties failing in the practice: that is, no incidents…
(how to do distributed locking on top of Redis)
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 3
- Total points
- 483
- Total comments
- 129
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2019-06-19 | How to Do Distributed Locking (2016)First breakout | appwiz | 120 | 13 |
| 2022-07-16 | How to do distributed locking (2016) | mooreds | 15 | 3 |
| 2022-11-10 | How to do distributed locking (2016) | paulgb | 1 | 0 |
| 2023-05-12 | How to do distributed locking (2016) | thealig | 103 | 18 |
| 2024-10-20 | How to do distributed locking (2016)Best thread · Latest 20+ point return | yusufaytas | 244 | 95 |