-
database_locks
-
pessimistic_lock
-
-
pessimistic_payments
- Optimistic lock can't be used in combination with pessimistic lock?
change_payment_intent_amount
with optimistic lock can't prevent concurrent updates withcharge_payment_intent
with pessimistic lock
- Optimistic lock can't be used in combination with pessimistic lock?
-
optimistic_payments
-
Update amount use case
-
Charge Payment Intent use case - with optimistic & semantic locks
-
Update
PaymentIntent.version
in-place inDynamoDBPaymentIntentRepository.update
? -
Consistent read is no longer needed because the optimistic lock will ensure a stale aggregate update is rejected
-
-
__eq__
method on aggregate objects?-
test_domain.py
-
-
Idempotence keys
- README