Workflow design for long-running distributed operations using no sql databases
OwnerPablo Chico de Guzman Huerta, Alberto Arias Maestroinventors
Life of this patent
Estimating the term…
Abstract
Transactions or operations associated with a received request are performed with a NoSQL database. A request ID is assigned to the request, an operation ID to the operation, and an entity ID to the entity associated with the operation. The entity is locked in the database, and the operation is performed. The database is unlocked, and a message is transmitted to a lock queue to release an entry therein associated with the request. If a second request attempt to lock the same entity while the first is concurrent, it requests that the lock queue inform it when the lock is released.
Claims16
A method for executing transactions with a NoSQL database, the method comprising:
- receiving a request to perform an operation on an entity in a NoSQL database;
- assigning a request ID to the request, an operation ID to the operation, and an entity ID to the entity;
- locking the entity in the NoSQL database using the entity ID and request ID;
- performing the operation associated with the operation ID;
- unlocking the entity in the NoSQL database;
- and
- transmitting a message to a lock queue to release an entry therein associated with the request.
A system for executing transactions with a NoSQL database, the system comprising:
- computer processors configured for executing computer instructions for computationally executing the steps of:
- i. receiving a request to perform an operation on an entity in a NoSQL database;
- ii. assigning a request ID to the request, an operation ID to the operation, and an entity ID to the entity;
- iii. locking the entity in the NoSQL database using the entity ID and request ID;
- iv. performing the operation associated with the operation ID;
- v. unlocking the entity in the NoSQL database;
- and
- vi. transmitting a message to a lock queue to release an entry therein associated with the request;
- and
- a database for storing performance data related to the execution of the plurality of virtual machines.
Dependencies are inferred from the claim text.