Timeline for Microservices distributed lock mechanism
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 15, 2023 at 1:10 | history | edited | DavidT | CC BY-SA 4.0 | Added additional solution that doesn't require the use of the Users service. |
| Apr 13, 2023 at 11:46 | comment | added | Andre Silva | If I receive a request to assign orders for the same user at exactly the same time How can I prevent from that user to end up with 2 orders? findAndModify will not work, because both replicas will execute it, and user will end up with 2 orders assigned to him | |
| Apr 13, 2023 at 11:44 | comment | added | Andre Silva | Our business requirements demand creating orders that are unassigned (userId field is null). And this microservice that owns the orders collection has an endpoint that allows to assign the first order available to that user. | |
| Apr 13, 2023 at 11:29 | history | answered | DavidT | CC BY-SA 4.0 |