Transaction orchestration for microservice
US-2018307514-A1 · Oct 25, 2018 · US
US2023230098A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2023230098-A1 |
| Application number | US-202318153694-A |
| Country | US |
| Kind code | A1 |
| Filing date | Jan 12, 2023 |
| Priority date | Dec 20, 2019 |
| Publication date | Jul 20, 2023 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Aspects described herein may relate to a transaction exchange platform using a streaming data platform (SDP) and microservices to process transactions according to review and approval workflows. The transaction exchange platform may receive transactions from origination sources, which may be added to the SDP as transaction objects. As the transactions are processed, the transactions may require access to a resource (e.g., a key value in a database). A microservice processing the transaction may request, from a locking microservice, a lock for the resource. The locking microservice may query a local cache to determine whether a lock exists for the resource. If the local cache determines that no lock exists for resource, the locking mechanism may employ a consensus protocol to obtain a lock for the resource from a plurality of clusters. If consensus is reached, a lock for the resource may be granted to the requesting microservice.
Opening claim text (preview).
What is claimed is: 1 . A computer-implemented method comprising: receiving, by a transaction exchange platform, a transaction object corresponding to a first payment transaction, wherein the transaction exchange platform comprises a first streaming data platform associated with a first geographic region and a second streaming data platform associated with a second geographic region different from the first geographic region; in response to retrieving a plurality of transaction objects from the first streaming data platform and based on a determination that a workflow stage of the transaction object matches a first workflow stage associated with a first microservice, determining, by the first microservice while processing the transaction object, that the processing of the transaction object requires use of a first resource, wherein the first microservice is associated with the first geographic region; acquiring, by a first locking microservice associated with the first geographic region and based on a determination that the processing of the transaction object requires use of the first resource, a first lock for the first resource; determining, by a watchdog microservice, that processing of the transaction object has failed; releasing, by the watchdog microservice and based on a determination that processing of the transaction object using the first resource has failed, the first lock from the first resource; transferring, by the watchdog microservice, processing of the first transaction object to the second geographic region; acquiring, by a second locking microservice associated with the second geographic region and based on a determination that the processing of the transaction object requires use of the first resource, a second lock for the first resource; and in response to receiving the second lock, processing, by a second microservice, the transaction object using the first resource to generate an updated value of the first resource. 2 . The computer-implemented method of claim 1 , further comprising: in response to receiving the first lock, processing, by the first microservice, the transaction object using the first resource, wherein processing the transaction object comprises updating a workflow stage associated with the transaction object, wherein the updated workflow stage is transmitted to the second geographic region when the transaction object is transferred. 3 . The computer-implemented method of claim 1 , further comprising: updating a region associated with the first transaction object to the second geographic region in response to transferring the transaction object. 4 . The computer-implemented method of claim 1 , wherein the determination that processing of the transaction object using the first resource has failed is based on a predetermined amount of time elapsing since the first lock was acquired. 5 . The computer-implemented method of claim 1 , wherein acquiring the first lock for the first resource comprises: receiving, by the first locking microservice from the first microservice, a request for a lock for the first resource; based on a determination that a lock does not exist for the first resource in the local data structure, transmitting, by the locking microservice to a distributed lock manager, an inquiry whether a lock exists for the first resource; receiving, from the distributed lock manager, a response indicating a lock does not exist for the first resource; transmitting, by the locking microservice to the distributed lock manager and based on the response indicating that a lock does not exist for the first resource, the request for a lock for the first resource; and receiving, by the locking microservice from the distributed lock manager, the first lock for the first resource, wherein the lock is granted based on a consensus protocol indicating that the first lock should be granted to the first microservice. 6 . The computer-implemented method of claim 1 , further comprising: transmitting, by the second locking microservice, a request to release the lock based on a determination that the second microservice has completed processing of the transaction object using the first resource. 7 . A transaction exchange platform comprising: at least one processor; and memory storing instructions that, when executed by the at least one processor, cause the transaction exchange platform to: receive a transaction object corresponding to a first payment transaction, wherein the transaction exchange platform comprises a first streaming data platform associated with a first geographic region and a second streaming data platform associated with a second geographic region different from the first geographic region; in response to retrieving a plurality of transaction objects from the first streaming data platform and based on a determination that a workflow stage of the transaction object matches a first workflow stage associated with a first microservice, determine, by the first microservice while processing the transaction object, that the processing of the transaction object requires use of a first resource, wherein the first microservice is associated with the first geographic region; acquire, by a first locking microservice associated with the first geographic region and based on a determination that the processing of the transaction object requires use of the first resource, a first lock for the first resource; determine, by a watchdog microservice, that processing of the transaction object has failed; release, by the watchdog microservice and based on a determination that processing of the transaction object using the first resource has failed, the first lock from the first resource; transfer, by the watchdog microservice, processing of the first transaction object to the second geographic region; acquire, by a second locking microservice associated with the second geographic region and based on a determination that the processing of the transaction object requires use of the first resource, a second lock for the first resource; and in response to receiving the second lock, process, by a second microservice, the transaction object using the first resource to generate an updated value of the first resource. 8 . The transaction exchange platform of claim 7 , wherein the instructions, when executed by the at least one processor, cause the transaction exchange platform to: in response to receiving the first lock, process the transaction object using the first resource, wherein processing the transaction object comprises updating a workflow stage associated with the transaction object, wherein the updated workflow stage is transmitted to the second geographic region when the transaction object is transferred. 9 . The transaction exchange platform of claim 7 , wherein the instructions, when executed by the at least one processor, cause the transaction exchange platform to: update a region associated with the first transaction object to the second geographic region in response to transferring the transaction object. 10 . The transaction exchange platform of claim 7 , wherein the determination that processing of the transaction object using the first resource has failed is based on a predetermined amount of time elapsing since the first lock was acquired. 11 . The transaction exchange platform of claim 7 , wherein the instructions, when executed by the at least one processor, cause the transaction exchange platform to: receive, by the first locking microservice from the first microservice, a request for a lock for the first resource; based on a determination that a lock does not exist for the first resource in the local data
in transactions (updating of structured data in databases G06F16/23) · CPC title
Error or fault detection not based on redundancy (power supply failures G06F1/30; network fault management H04L41/06) · CPC title
for performance assessment · CPC title
where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50) · CPC title
using two different networks, one for transaction and one for security confirmation · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.