Skip to main content
Software Engineering

Return to Question

Post Timeline

added 43 characters in body
Source Link
tusharRawat
tusharRawat
  • 221
  • 1
  • 6
  1. Payment Initiation: The user initiates prepayment in the User-Order Service. If the order is user-canceled, the payment fails; otherwise, a "user-cancellation lock" is applied to prevent order cancellation during conversion.
  2. Event Publishing: A check-event is sent to the Seller-Order Service, which applies its own locks (shipment/cancellation) and evaluates the order’s eligibility(should not be seller cancelled and shipped) for prepayment.
  3. Decision: Based on the Seller-Order Service response (eligible/ineligible), the User-Order Service either confirms prepayment or rejects it and initiateswith initiating a refund and release the lock which was acquired.
  1. Payment Initiation: The user initiates prepayment in the User-Order Service. If the order is user-canceled, the payment fails; otherwise, a "user-cancellation lock" is applied to prevent order cancellation during conversion.
  2. Event Publishing: A check-event is sent to the Seller-Order Service, which applies its own locks (shipment/cancellation) and evaluates the order’s eligibility(should not be seller cancelled and shipped) for prepayment.
  3. Decision: Based on the Seller-Order Service response (eligible/ineligible), the User-Order Service either confirms prepayment or rejects it and initiates a refund.
  1. Payment Initiation: The user initiates prepayment in the User-Order Service. If the order is user-canceled, the payment fails; otherwise, a "user-cancellation lock" is applied to prevent order cancellation during conversion.
  2. Event Publishing: A check-event is sent to the Seller-Order Service, which applies its own locks (shipment/cancellation) and evaluates the order’s eligibility(should not be seller cancelled and shipped) for prepayment.
  3. Decision: Based on the Seller-Order Service response (eligible/ineligible), the User-Order Service either confirms prepayment or rejects it with initiating a refund and release the lock which was acquired.
added 65 characters in body
Source Link
tusharRawat
tusharRawat
  • 221
  • 1
  • 6
  1. Irreversible writes in system - What if any system after taking a request for update, rejects update when system ahead of it has accepted change, we won't have any way to bring system to initial state ? How can we protect this to happen OR have a way to bring entire system to previous state, here we are not saving old state of the system anywhere so not sure if this is actually possible or not. UsingShould we think around using something like versioning to save the old states on each system to bring the system back to initial state.
  1. Irreversible writes in system - What if any system after taking a request for update, rejects update when system ahead of it has accepted change, we won't have any way to bring system to initial state ? How can we protect this to happen OR have a way to bring entire system to previous state, here we are not saving old state of the system anywhere so not sure if this is actually possible or not. Using something like versioning to save the old states on each system.
  1. Irreversible writes in system - What if any system after taking a request for update, rejects update when system ahead of it has accepted change, we won't have any way to bring system to initial state ? How can we protect this to happen OR have a way to bring entire system to previous state, here we are not saving old state of the system anywhere so not sure if this is actually possible or not. Should we think around using something like versioning to save the old states on each system to bring the system back to initial state.
added 1212 characters in body
Source Link
tusharRawat
tusharRawat
  • 221
  • 1
  • 6
  1. Irreversible writes in system - What if any system after taking a request for update, rejects update when system ahead of it has accepted change, we won't have any way to bring system to initial state ? How can we protect this to happen OR have a way to bring entire system to previous state, here we are not saving old state of the system anywhere so not sure if this is actually possible or not. Using something like versioning to save the old states on each system.
  1. Irreversible writes in system - What if any system after taking a request for update, rejects update when system ahead of it has accepted change, we won't have any way to bring system to initial state ? How can we protect this to happen OR have a way to bring entire system to previous state, here we are not saving old state of the system anywhere so not sure if this is actually possible or not. Using something like versioning to save the old states on each system.
added 1212 characters in body
Source Link
tusharRawat
tusharRawat
  • 221
  • 1
  • 6
Source Link
tusharRawat
tusharRawat
  • 221
  • 1
  • 6