---
title: "Comment by Nag on \"How does BookMyShow handle concurrent bookings\" | Hashnode"
description: "I see , some fundamental problems here. although using RDBMS is the only best option. row locking is a problem. If we have 15 seats in a Row(Theatre screen) mul"
url: "https://hashnode.com/posts/how-does-bookmyshow-handle-concurrent-bookings/6252ca4275dccb6f3431f7d4/comment/65df61a6be797e562298b0b4"
---

[Discussion](https://hashnode.com/posts/how-does-bookmyshow-handle-concurrent-bookings/6252ca4275dccb6f3431f7d4)

Comment [How does BookMyShow handle concurrent bookings](https://hashnode.com/posts/how-does-bookmyshow-handle-concurrent-bookings/6252ca4275dccb6f3431f7d4)

[Nag](https://hashnode.com/@nag146)

[Feb 28, 2024](https://hashnode.com/posts/how-does-bookmyshow-handle-concurrent-bookings/6252ca4275dccb6f3431f7d4/comment/65df61a6be797e562298b0b4)

I see , some fundamental problems here. although using RDBMS is the only best option. row locking is a problem. If we have 15 seats in a Row(Theatre screen) multiple users may want to book different seats in the same Row . Row locking puts everyone on hold and concurrent users accessing/booking does not scale at all.