Abstract: Embodiments of the present disclosure relate to rollback of services with a global variable change. Embodiment techniques detect that at least two of a plurality of services in a transaction are executed to change a value of a first global variable. Tracing information is obtained to indicate a first order in which the at least two services change the value of the first global variable during execution of the plurality of services. In response to a failure of the transaction, a rollback execution plan for a plurality of compensating services is determined at least based on the tracing information, where the plurality of compensating services are configured to compensate for the plurality of services respectively. The plurality of compensating services subsequently executed according to the rollback execution plan.

Abstract: Embodiments of the present disclosure relate to rollback of services with a global variable change. Embodiment techniques detect that at least two of a plurality of services in a transaction are executed to change a value of a first global variable. Tracing information is obtained to indicate a first order in which the at least two services change the value of the first global variable during execution of the plurality of services. In response to a failure of the transaction, a rollback execution plan for a plurality of compensating services is determined at least based on the tracing information, where the plurality of compensating services are configured to compensate for the plurality of services respectively. The plurality of compensating services subsequently executed according to the rollback execution plan.

Abstract: Approaches presented herein enable hot upgrading a microservices sequence in a cloud computing environment. More specifically, a next microservice of microservice subsequence in a running sequence is obtained, in response to a message to invoke the microservice or subsequence. The running microservice sequence includes at least one unexecuted microservice or subsequence that is to be hot upgraded. The running microservice sequence is generated based on a sequence that is to be hot upgraded which comprises an ordered list of microservices and/or subsequences. The approach may include determining the status of a next microservice or subsequence. The approach may further include invoking the next microservice or subsequence in the running sequence, in response to the status of the next microservice or subsequence being upgrade-complete.

Abstract: Approaches presented herein enable hot upgrading a microservices sequence in a cloud computing environment. More specifically, a next microservice of microservice subsequence in a running sequence is obtained, in response to a message to invoke the microservice or subsequence. The running microservice sequence includes at least one unexecuted microservice or subsequence that is to be hot upgraded. The running microservice sequence is generated based on a sequence that is to be hot upgraded which comprises an ordered list of microservices and/or subsequences. The approach may include determining the status of a next microservice or subsequence. The approach may further include invoking the next microservice or subsequence in the running sequence, in response to the status of the next microservice or subsequence being upgrade-complete.

Abstract: An example operation may include one or more of connecting, by a virtual blockchain manager node, to a blockchain configured to store a plurality of user transactions committed by a user node, identifying, by the virtual blockchain manager node, a user request transaction from the plurality of the user transactions for a creation of a virtual blockchain for the user, wherein the user request transaction contains a rule, creating, by the virtual blockchain manager node, the virtual blockchain based on the user request transaction, populating, by the virtual blockchain manager node, the virtual blockchain with the user transactions from the plurality of the user transactions from the blockchain based on the rule, and executing, by the virtual blockchain manager node, a smart contract to record the rule and a hash of all blocks from the virtual blockchain onto the blockchain.

Abstract: An example operation may include one or more of connecting, by a virtual blockchain manager node, to a blockchain configured to store a plurality of user transactions committed by a user node, identifying, by the virtual blockchain manager node, a user request transaction from the plurality of the user transactions for a creation of a virtual blockchain for the user, wherein the user request transaction contains a rule, creating, by the virtual blockchain manager node, the virtual blockchain based on the user request transaction, populating, by the virtual blockchain manager node, the virtual blockchain with the user transactions from the plurality of the user transactions from the blockchain based on the rule, and executing, by the virtual blockchain manager node, a smart contract to record the rule and a hash of all blocks from the virtual blockchain onto the blockchain.