Figure 13-2: Multishard Payment Without Atomic Commit

Figure 13-2: Multishard Payment Without Atomic Commit A data-flow diagram generated by Archify. 01 / Request 02 / Source Shard 03 / Fan-Out 04 / Apply 05 / Done Client Request · unique request ID · 01 / Request · append Client Request unique request ID append Source Processor · checks + reserves · 02 / Source Shard · derived DB Source Processor checks + reserves derived DB 3 Derived Events · 03 / Fan-Out · same request ID 3 Derived Events same request ID Destination Proc · apply + dedup · 04 / Apply · request ID Destination Proc apply + dedup request ID Source Log · outgoing+declined · 04 / Apply · subscribe Source Log outgoing+declined subscribe Fees Processor · apply + dedup · 04 / Apply · request ID Fees Processor apply + dedup request ID Completed · eventually written · 05 / Done · no 2PC Completed eventually written no 2PC request + unique ID reserve + emit 3 events incoming payment outgoing payment fee payment completed / declined Legend primary data data store data flow