---
title: "Nag (@nag146) | Hashnode"
description: "Nag (@nag146) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@nag146"
---

@nag146

# Nag

@nag146 · Joined February 2024

## Comments

[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.](https://hashnode.com/posts/how-does-bookmyshow-handle-concurrent-bookings/6252ca4275dccb6f3431f7d4/comment/65df61a6be797e562298b0b4)

Comment · Article · Feb 28, 2024 · [How does BookMyShow handle concurrent bookings](https://hashnode.com/posts/how-does-bookmyshow-handle-concurrent-bookings/6252ca4275dccb6f3431f7d4)