---
title: "Discussion on \"Locking a Seat Without Losing the Sale: Atomic Booking in Reverix 2.0\" | Hashnode"
description: "Discussion on \"Locking a Seat Without Losing the Sale: Atomic Booking in Reverix 2.0\". Redis's atomic lock looked airtight — until a concurrency test revealed 3 threads could lock the same seat. Here's the bug, the fix, and the proof."
url: "https://hashnode.com/posts/locking-a-seat-without-losing-the-sale-atomic-booking-in-reverix-2-0/6a64bc848dd3d9df1e421910"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Locking a Seat Without Losing the Sale: Atomic Booking in Reverix 2.0](https://thestacktrace.hashnode.dev/locking-a-seat-without-losing-the-sale-atomic-booking-in-reverix-2-0?utm_source=hashnode&utm_medium=feed)

Redis's atomic lock looked airtight — until a concurrency test revealed 3 threads could lock the same seat. Here's the bug, the fix, and the proof.

Jul 25 · 7 min read · thestacktrace.hashnode.dev  
Read the article

-   [#redis](https://hashnode.com/tag/redis)
-   [#kotlin](https://hashnode.com/tag/kotlin)
-   [#concurrency](https://hashnode.com/tag/concurrency)
-   [#system-design](https://hashnode.com/tag/system-design)
-   [#race-condition](https://hashnode.com/tag/race-condition)

## Written by

[Ashish Babu](https://hashnode.com/@ashish-babu)

@ashish-babu · Chennai, India

  
[View profile](https://hashnode.com/@ashish-babu)

Backend Engineer building distributed systems from scratch

Backend Software Engineer who builds scalable, distributed systems. I write about the real bugs, tradeoffs, and lessons I run into while building things from scratch — mostly backend architecture, concurrency, and systems design.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
