Firebase allows for a resource to be updated transactionally. As I understand it, the client does this buy sending requests to the server saying \"If the old value is X, ma
there is another way.... very tedious... and not really transactions...
As Firebase allows atomically changes on a value, you could create a lock or semaphore with the meaning of "started a transaction on the resources x, y and z"... of course, it is not a real transaction as it doesn't block resources, a part from the lock. We could call it transaction by convention. The clients needs to know that when the lock is occupied, they should not change x, y and z resources....