Software Engineering Stack Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle. It only takes a minute to sign up.
Sign up to join this community
Suppose I have a web app where sellers add their products and set them as available for sale. Then I show a list of products in my mobile app, where I get products via my REST API. My problem: suppose two clients view the same product(and there's only 1 item available from the seller) and they make simultaneous order. How do I resolve such collision?
My technology stack: RoR, PostgreSQL, heroku.
There's no such thing a simultaneous order. Your server is going to have to process one of the basket add actions first. At the point that happens the product should be locked, and any subsequent basket add actions should return an out-of-stock message. If the customer doesn't checkout within a fixed time (often one hour) it's normal to remove the lock on the product and return it to sale. This can be supplemented with messaging on the basket page explaining that the item in their bag is only going to be available for a fixed time due to low stock.
The critical thing from the user's perspective is that whichever one of them tries to add the item to their basket second should receive a message indicating the item is out of stock immediately after trying to add it to their basket. It's terrible UX to let them get into the checkout thinking they've got an item and then reject the sale later.
In general ecommerce websites get around this problem by automatically marking items as out of stock when they get down to low but non-zero product levels. This allows the merchandisers to restock the items without ever having taken an order that they're unable to fulfil; though that might not be possible in your case if the sellers are selling unique items.
