Race Conditions: Beware of Using List Fields in Objects If You Plan To Scale

[gf_wolfer]

Thanks for the detail and bringing this up. I have had constant issues regarding this in my own registration type app. Each year there is a specific event that I faces race condition issues. I’ve tried lists, searches and almost everything I can think of, nothing has worked perfectly - so while I would say Searches are better than Lists for this, they still have drawbacks.

My most recent solution for this specific event worked, but would be costly with the WU pricing (searches and then double checking searches for timestamps) and slightly ‘clunky’ of a UX that it would not make sense to use as a standard registration process. So I can toggle certain events to have this registration flow turned on.

I don’t know if there is a simple solution to this unless Bubble works on something for us as it’s just not structured for a high demand app like this, which I’ve mentioned here before

More on the subject here:

Concurrent db changes

Hello! I need your help with an issue that we are facing. We’ve created an application that manages and generates orders for e-commerce stores. And we now have customers that generate multiple orders at the same second on the same product. Our exact use case is that let’s say we have 1 product in stock and there are 2 users placing an order for that product at the same second. What happens is that we are currently processing both orders and we end up having -1 stock for that product. We tried…