CN108304271B - Distributed transaction manager and management method under micro-service architecture - Google Patents
Distributed transaction manager and management method under micro-service architecture Download PDFInfo
- Publication number
- CN108304271B CN108304271B CN201810040965.1A CN201810040965A CN108304271B CN 108304271 B CN108304271 B CN 108304271B CN 201810040965 A CN201810040965 A CN 201810040965A CN 108304271 B CN108304271 B CN 108304271B
- Authority
- CN
- China
- Prior art keywords
- service
- transaction
- calling
- context
- cache
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Hardware Redundancy (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses a distributed transaction manager and a management method under a micro-service architecture, wherein the method comprises the following steps: judging the type of the called service according to the service calling method type, if the called service is a slave service needing remote calling, obtaining a transaction context from a cache and identifying a JVM environment, if the slave service and the master service are located in the same JVM, carrying out local calling, executing preprocessing, storing compensation operation, updating the transaction context, executing the slave service, and carrying out transaction compensation according to the transaction context when a service exception occurs. The distributed transaction manager and the management method under the micro-service architecture have the following beneficial effects: the invention can obtain the transaction context from the cache, identify the JVM environment, and carry out the calling of the same JVM environment through local calling, thereby facilitating the use of service developers, leading the service developers to not need to distinguish the local calling from the remote calling, and avoiding unnecessary resource waste and performance loss.
Description
Technical Field
The invention relates to the field of cloud computing, in particular to a distributed transaction manager and a management method under a micro-service architecture.
Background
The popularity of cloud-native and micro-service architectures has made distributed transaction issues increasingly prominent. Cloud-native and micro-service architectures are essentially distributed services architectures, and popular micro-service architectures include SpringCloud and Dubbo, both SpringCloud and Dubbo, which are challenges around the past for distributed transactions. The transaction is divided into a flexible transaction and a rigid transaction, and the rigid transaction refers to a transaction strictly following the ACID principle, such as a database transaction in a single machine environment. Flexible transactions refer to transactions that follow BASE theory, and are typically used in distributed environments, with common implementations being two-phase commit (2PC), TCC compensation type commit, asynchronous message-based acknowledgement, and best effort notification type. In the transaction manager based on TCC compensation mechanism in the industry, there is great inconvenience in implementing service logic, and resource waste and performance loss.
Disclosure of Invention
The present invention provides a distributed transaction manager and a management method under a microservice architecture, aiming at the above-mentioned defects in the prior art.
The technical scheme adopted by the invention for solving the technical problems is as follows: a distributed transaction management method under a micro-service architecture is constructed, and the method comprises the following steps:
judging the type of the called service according to the service calling method type, if the called service is a slave service needing remote calling, obtaining a transaction context from a cache and identifying a JVM environment, if the slave service and the master service are located in the same JVM, carrying out local calling, executing preprocessing, storing compensation operation, updating the transaction context, executing the slave service, and carrying out transaction compensation according to the transaction context when a service exception occurs.
In the distributed transaction management method under the microservice architecture of the present invention, the method further includes:
judging the type of the called service according to the service calling method type, if the called service is a slave service needing remote calling, obtaining a transaction context from a cache and identifying a JVM environment, if the slave service and a master service are located in different JVMs, entering a remote branch according to a remote interceptor, executing preprocessing, storing compensation operation, updating the transaction context, then executing the slave service, and when a service abnormality occurs, performing transaction compensation according to the transaction context.
In the distributed transaction management method under the microservice architecture of the present invention, the method further includes:
judging the type of the called service according to the service calling method type, if the called service is a main service, creating a transaction, taking the action of calling the main service as the root of a service calling tree, updating the transaction context in a cache, calling the main service, and when a service is abnormal, calling a service logic to execute transaction compensation according to the historical state in the transaction context and submit the transaction, and directly submitting the transaction if no abnormality occurs.
In the distributed transaction management method under the microservice architecture of the present invention, the method further includes: when the business activity starts, a business interceptor is used for intercepting, generating a transaction context and storing the transaction context in a cache.
The invention also discloses a distributed transaction manager under the micro-service architecture, which comprises a remote interceptor, a service interceptor and a cache, wherein the remote interceptor is started once when the service is called remotely each time and stores the intercepted information into the cache, and the service interceptor is started once when the service is called each time and stores the intercepted information into the cache;
the transaction manager is used for judging the type of the called service according to the type of a service calling method when the service is called, obtaining a transaction context from a cache and identifying a JVM (JVM) environment if the called service is a slave service needing remote calling, carrying out local calling, executing preprocessing, storing compensation operation, updating the transaction context, then executing the slave service, and carrying out transaction compensation according to the transaction context when service abnormity occurs.
In the distributed transaction manager under the micro-service architecture, the transaction manager is further configured to, when a service is called, determine a type of the called service according to a service calling method type, obtain a transaction context from the cache and identify a JVM environment if the called service is a slave service that needs to be remotely called, enter a remote branch according to a remote interceptor if the slave service and a master service are located in different JVMs, obtain the transaction context from the cache, perform preprocessing and store a compensation operation, update the transaction context, then execute the slave service, and perform transaction compensation according to the transaction context when a service exception occurs.
In the distributed transaction manager under the micro-service architecture, the transaction manager is also used for judging the type of the called service according to the type of the service calling method when the service is called, if the called service is the main service, creating a transaction, taking the action of calling the main service as the root of a service calling tree, updating the transaction context in a cache, calling the main service, and when the service is abnormal, calling the service logic to execute transaction compensation according to the historical state in the transaction context, submitting the transaction, and directly submitting the transaction if the abnormal condition does not occur.
In the distributed transaction manager under the micro-service architecture, the transaction manager is further configured to intercept, generate a transaction context, and store the transaction context in a cache by using a service interceptor when a service activity starts.
The distributed transaction manager and the management method under the micro-service architecture have the following beneficial effects: the invention can identify the JVM environment, obtain the transaction context from the cache for the calling of the same JVM environment, and carry out the calling through the local calling, thereby facilitating the use of the service developer, leading the service developer to not need to distinguish the local calling from the remote calling, and avoiding unnecessary resource waste and performance loss.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts:
FIG. 1 is a block diagram of a transaction manager according to a preferred embodiment of the present invention;
FIG. 2 is a flowchart of a method provided in a preferred embodiment of the present invention.
Detailed Description
To facilitate an understanding of the invention, the invention will now be described more fully with reference to the accompanying drawings. Exemplary embodiments of the invention are shown in the drawings. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.
The general idea of the invention is as follows: the JVM environment is automatically identified, the transaction context is obtained from the cache for the calling of the same JVM environment, and the calling is carried out through local calling, so that the use of service developers is facilitated, the service developers do not need to distinguish local calling from remote calling, and unnecessary resource waste and performance loss are avoided.
In order to better understand the technical solutions, the technical solutions will be described in detail below with reference to the drawings and the specific embodiments of the specification, and it should be understood that the embodiments and specific features of the embodiments of the present invention are detailed descriptions of the technical solutions of the present application, and are not limited to the technical solutions of the present application, and the technical features of the embodiments and examples of the present invention may be combined with each other without conflict.
A complete application business activity consists of a main business service and a plurality of auxiliary business services, and the whole business activity is generally initiated and ended by the main business service; providing a compensation operation from a business operation provided by the business service, the compensation operation being capable of offsetting (or partially offsetting) a business result of the forward business operation; the business activity manager controls the consistency of business activities, is responsible for registering operations in the business activity, and invokes compensation operations when the business activity is cancelled.
The complete business processing process comprises a plurality of service operations, and the service operations form a call tree. The master action (i.e., the action that invokes the portal/service) is the initiator of the overall business activity and is also the root of the service operation invocation tree. The submission and rollback of the master action itself can be made to reasonably determine the submission and rollback of the entire business activity. Corresponding to a service operation call; each atomic action serves as a basic unit of business activity, satisfying ACID by local transactions. The service operation corresponding to the atomic action is of two types: request-response, asynchronous call. There are many consequences of service operation, including successful business operation, abnormal business operation, network exception/timeout, etc. The service invocation and the corresponding transaction management in the invention are mainly divided into the following two parts:
1) all services of business activities are called locally, and if the service calling is abnormal, the transaction is guaranteed by the existing database transaction manager;
2) for a (springclosed or Dubbo) business activity with a remote service invocation, if a local service invocation in the business activity is abnormal, compensation needs to be performed on the remote service and all the branches of the business activity related to the remote service invocation success. The first embodiment and the second embodiment are specific examples for implementing the contents in this section.
Example one
Referring to fig. 1, an embodiment of the invention discloses a distributed transaction manager under a micro-service architecture, and the transaction manager of this embodiment may integrate a springclosed and a Dubbo micro-service framework, so as to provide distributed transaction management for application development under a cloud environment.
Specifically, the transaction manager of this embodiment includes a remote interceptor, a service interceptor, and a cache. The remote interceptor is started once each time the service is remotely called and stores the intercepted information into the cache. The service interceptor is started once when calling service each time, and stores the intercepted information into the cache. The cache can use a cache database such as redis, memcached or mongodb.
Firstly, when the business activity starts, the transaction manager uses the internal business interceptor to intercept, generate the transaction context, and store the transaction context in the cache. The transaction context includes a global transaction id, a JVM identification, a persisted historical state, a current transaction state, and the like.
Then, when the transaction manager calls the service, the transaction manager judges the type of the called service according to the type of the service calling method, if the called service is the main service, the transaction manager creates a transaction, updates the transaction context in the cache by taking the action of calling the main service as the root of a service calling tree, and calls the main service. When the business is abnormal, the business logic is called to execute the business compensation according to the historical state in the context of the business and submit the business, and the business is directly submitted without the abnormal situation.
The transaction manager judges the type of the called service according to the type of a service calling method when calling the service, obtains a transaction context from a cache if the called service is a slave service needing remote calling, identifies a JVM environment according to a JVM identifier, obtains the transaction context from the cache according to a remote branch entered by a remote interceptor if the slave service and a master service are located in different JVMs, executes preprocessing and stores compensation operation, updates the transaction context, then executes the slave service, and performs transaction compensation according to the transaction context when a service abnormality occurs.
The transaction manager judges the type of the called service according to the service calling method type when calling the service, obtains a transaction context from a cache if the called service is a slave service needing remote calling, identifies a JVM environment according to a JVM identifier, carries out local calling if the slave service and a master service are located in the same JVM, carries out preprocessing and stores compensation operation, updates the transaction context, then executes the slave service, and carries out transaction compensation according to the transaction context when service abnormity occurs.
Example two
Referring to fig. 2, the transaction management method provided by the embodiment mainly includes:
and S100, when the business activity starts, intercepting by using a business interceptor, generating a transaction context, and storing the transaction context in a cache.
The cache can use a cache database such as redis, memcached or mongodb. The transaction context includes a global transaction id, a JVM identification, a persisted historical data state, a current transaction state, and the like.
S200, judging the type of the called service according to the type of the service calling method, if the called service is a main service, creating a transaction, taking the action of calling the main service as the root of a service calling tree, updating the transaction context in a cache, calling the main service, and when a service is abnormal, calling a service logic to execute transaction compensation according to the historical state in the transaction context, submitting the transaction, and directly submitting the transaction if no abnormality occurs.
S300, judging the type of the called service according to the type of the service calling method, if the called service is a slave service needing remote calling, obtaining a transaction context from a cache, identifying a JVM (virtual machine manager) environment according to a JVM identifier, if the slave service and the master service are located in different JVMs, entering a remote branch according to a remote interceptor, executing preprocessing, storing compensation operation, updating the transaction context, executing the slave service, and performing transaction compensation according to the transaction context when service abnormality occurs.
S400, judging the type of the called service according to the type of the service calling method, if the called service is a slave service needing remote calling, obtaining a transaction context from a cache, identifying a JVM environment according to a JVM identifier, if the slave service and the master service are located in the same JVM, carrying out local calling, executing preprocessing, storing compensation operation, updating the transaction context, then executing the slave service, and carrying out transaction compensation according to the transaction context when service abnormity occurs.
In summary, the distributed transaction manager and the management method under the micro-service architecture of the present invention have the following advantages: the invention can identify the JVM environment, obtain the transaction context from the cache for the calling of the same JVM environment, and carry out the calling through the local calling, thereby facilitating the use of the service developer, leading the service developer to not need to distinguish the local calling from the remote calling, and avoiding unnecessary resource waste and performance loss.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (8)
1. A distributed transaction management method under a micro-service architecture is characterized by comprising the following steps:
judging the type of the called service according to the service calling method type, if the called service is a slave service needing remote calling, obtaining a transaction context from a cache and identifying a JVM environment, if the slave service and the master service are located in the same JVM, carrying out local calling, executing preprocessing, storing compensation operation, updating the transaction context, executing the slave service, and carrying out transaction compensation according to the transaction context when a service exception occurs.
2. The distributed transaction management method under the microservice architecture of claim 1, wherein the method further comprises:
if the slave service and the master service are located in different JVMs, the remote interceptor enters a remote branch, preprocessing is executed, compensation operation is stored, the transaction context is updated, the slave service is executed again, and when the service is abnormal, the transaction compensation is carried out according to the transaction context.
3. The distributed transaction management method under the microservice architecture of claim 1, wherein the method further comprises:
if the called service is the main service, creating a transaction, taking the action of calling the main service as the root of a service calling tree, updating the transaction context in the cache, calling the main service, and when a service is abnormal, calling the service logic to execute transaction compensation according to the transaction context and submit the transaction, and if no abnormality occurs, directly submitting the transaction.
4. The distributed transaction management method under the microservice architecture of claim 1, wherein the method further comprises: when the business activity starts, a business interceptor is used for intercepting, generating a transaction context and storing the transaction context in a cache.
5. A distributed transaction manager under a micro-service architecture is characterized by comprising a remote interceptor, a service interceptor and a cache, wherein the remote interceptor is started once when the remote interceptor remotely calls a service each time and stores intercepted information into the cache, and the service interceptor is started once when the service is called each time and stores the intercepted information into the cache;
the transaction manager is used for judging the type of the called service according to the type of a service calling method when the service is called, obtaining a transaction context from a cache and identifying a JVM (JVM) environment if the called service is a slave service needing remote calling, carrying out local calling, executing preprocessing, storing compensation operation, updating the transaction context, then executing the slave service, and carrying out transaction compensation according to the transaction context when service abnormity occurs.
6. The distributed transaction manager under the microservice architecture of claim 5, wherein the transaction manager is further configured to enter a remote branch according to a remote interceptor when the slave service and the master service are located in different JVMs, obtain a transaction context from a cache, perform preprocessing and save compensation operations, update the transaction context, execute the slave service again, and perform transaction compensation according to the transaction context when a service exception occurs.
7. The distributed transaction manager under the microservice architecture of claim 5, wherein the transaction manager is further configured to create a transaction when the called service is a master service, update the transaction context in the cache by using an action of calling the master service as a root of a service calling tree, and perform calling of the master service, and when a service exception occurs, call the service logic to perform transaction compensation according to the transaction context and commit the transaction, and directly commit the transaction if no exception occurs.
8. The distributed transaction manager under the microservice architecture of claim 5, wherein the transaction manager is further configured to intercept, generate a transaction context, and store to a cache, at the beginning of a transaction activity using a transaction interceptor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810040965.1A CN108304271B (en) | 2018-01-16 | 2018-01-16 | Distributed transaction manager and management method under micro-service architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810040965.1A CN108304271B (en) | 2018-01-16 | 2018-01-16 | Distributed transaction manager and management method under micro-service architecture |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108304271A CN108304271A (en) | 2018-07-20 |
| CN108304271B true CN108304271B (en) | 2021-08-06 |
Family
ID=62869142
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810040965.1A Active CN108304271B (en) | 2018-01-16 | 2018-01-16 | Distributed transaction manager and management method under micro-service architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108304271B (en) |
Families Citing this family (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109597699A (en) * | 2018-11-28 | 2019-04-09 | 泰康保险集团股份有限公司 | Data processing method, device, electronic equipment and computer-readable medium |
| CN109739624B (en) * | 2018-12-27 | 2021-07-16 | 北京三快在线科技有限公司 | Distributed transaction processing method and device, electronic equipment and computer readable medium |
| CN109741176B (en) * | 2018-12-28 | 2021-04-27 | 四川新网银行股份有限公司 | Distributed service scheduling system based on internet financial scene |
| CN109947415A (en) * | 2019-02-28 | 2019-06-28 | 东软集团股份有限公司 | Configuration method, device, storage medium and the electronic equipment of blocker |
| CN110008271B (en) * | 2019-04-04 | 2020-12-15 | 航天云网科技发展有限责任公司 | Micro-service transaction submitting method based on single database |
| CN110083439B (en) * | 2019-05-23 | 2021-10-01 | 北京奥鹏远程教育中心有限公司 | Distributed transaction system |
| CN110457142B (en) * | 2019-07-10 | 2023-05-09 | 创新先进技术有限公司 | Service processing method, system, machine room, architecture and electronic equipment |
| CN112445860B (en) * | 2019-09-02 | 2023-11-03 | 北京京东振世信息技术有限公司 | Method and device for processing distributed transaction |
| CN111880908A (en) * | 2020-06-28 | 2020-11-03 | 北京沃东天骏信息技术有限公司 | Distributed transaction processing method and device and storage medium |
| CN112328406B (en) * | 2020-10-10 | 2023-05-09 | 南方电网数字平台科技(广东)有限公司 | Micro-service distributed transaction system based on TCC (TCC) and service processing method |
| CN113051043A (en) * | 2021-03-10 | 2021-06-29 | 北京沃东天骏信息技术有限公司 | Micro-service anomaly compensation method and device |
| CN113032421A (en) * | 2021-04-29 | 2021-06-25 | 电子科技大学 | MongoDB-based distributed transaction processing system and method |
| CN114553724B (en) * | 2022-03-01 | 2024-03-26 | 启明信息技术股份有限公司 | Method and system for solving operation and maintenance problems of distributed micro-service architecture platform |
| CN116225724B (en) * | 2023-05-09 | 2023-08-22 | 云筑信息科技(成都)有限公司 | Method for realizing distributed retry scheduling based on memory |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106503132A (en) * | 2016-10-19 | 2017-03-15 | 广州快塑电子商务有限公司 | A kind of distributed transaction management method and system |
| CN106888129A (en) * | 2017-04-20 | 2017-06-23 | 国家电网公司 | It is a kind of can elastic telescopic distributed service management system and its method |
| CN107247784A (en) * | 2017-06-14 | 2017-10-13 | 郑州云海信息技术有限公司 | The control method and task manager of a kind of distributed transaction |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170329635A1 (en) * | 2016-05-13 | 2017-11-16 | University Of Utah Research Foundation | Systems and methods for distributed computing |
-
2018
- 2018-01-16 CN CN201810040965.1A patent/CN108304271B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106503132A (en) * | 2016-10-19 | 2017-03-15 | 广州快塑电子商务有限公司 | A kind of distributed transaction management method and system |
| CN106888129A (en) * | 2017-04-20 | 2017-06-23 | 国家电网公司 | It is a kind of can elastic telescopic distributed service management system and its method |
| CN107247784A (en) * | 2017-06-14 | 2017-10-13 | 郑州云海信息技术有限公司 | The control method and task manager of a kind of distributed transaction |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108304271A (en) | 2018-07-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108304271B (en) | Distributed transaction manager and management method under micro-service architecture | |
| CN107045454B (en) | Cross-process distributed transaction control method and related system | |
| US8667329B2 (en) | Processing transactions in graph-based applications | |
| US9075750B2 (en) | Oracle rewind: metadata-driven undo | |
| US7778965B2 (en) | Systems and methods for common instance handling of providers in a plurality of frameworks | |
| US8127278B2 (en) | System and method for extending legacy applications with undo/redo functionality | |
| US8682998B2 (en) | Method and server cluster for map reducing flow services and large documents | |
| US8060544B2 (en) | Representation of data transformation processes for parallelization | |
| US20090125366A1 (en) | Method and system for dynamic adaptation of workflows | |
| US8341632B2 (en) | Composite task framework | |
| US8346851B2 (en) | System and method for determining when to generate subordinate coordinators on local machines | |
| US8499298B2 (en) | Multiprocessing transaction recovery manager | |
| US11200085B2 (en) | Sharing transaction contexts in an optimized colocation of java and non-java language applications | |
| US20160092296A1 (en) | Resource manager failure handling in a multi-process transaction environment | |
| US10970141B2 (en) | Integrating transaction processing system interfaces with event-driven polyglot runtime modules | |
| US6542922B1 (en) | Client/server transaction data processing system with automatic distributed coordinator set up into a linear chain for use of linear commit optimization | |
| US9268582B2 (en) | Method and device enabling the execution of heterogeneous transaction components | |
| CN112579569A (en) | Data migration method and device | |
| CN113515352B (en) | Distributed transaction different-library mode anti-transaction calling method and device | |
| US20220129332A1 (en) | Handling of Metadata for Microservices Processing | |
| CN116643854A (en) | Service arrangement method and device, flow controller and task processor | |
| CN113992750A (en) | Global transaction coordination method, device, equipment and medium | |
| US9772853B1 (en) | Dispatching a unit of work to a specialty engine or a general processor and exception handling including continuing execution until reaching a defined exit point or restarting execution at a predefined retry point using a different engine or processor | |
| US20120136778A1 (en) | Replicating data in financial systems | |
| US7752254B2 (en) | Propagating contexts between a first and second system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address |
Address after: 518000 building 501, 502, 601, 602, building D, wisdom Plaza, Qiaoxiang Road, Gaofa community, Shahe street, Nanshan District, Shenzhen City, Guangdong Province Patentee after: China Southern Power Grid Shenzhen Digital Power Grid Research Institute Co.,Ltd. Address before: 518000, two floor, fragrant building, 2075 Lianhua Road, Futian District, Shenzhen, Guangdong. Patentee before: SHENZHEN COMTOP INFORMATION TECHNOLOGY Co.,Ltd. |
|
| CP03 | Change of name, title or address | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 518000 building 501, 502, 601, 602, building D, wisdom Plaza, Qiaoxiang Road, Gaofa community, Shahe street, Nanshan District, Shenzhen City, Guangdong Province Patentee after: China Southern Power Grid Digital Platform Technology (Guangdong) Co.,Ltd. Address before: 518000 building 501, 502, 601, 602, building D, wisdom Plaza, Qiaoxiang Road, Gaofa community, Shahe street, Nanshan District, Shenzhen City, Guangdong Province Patentee before: China Southern Power Grid Shenzhen Digital Power Grid Research Institute Co.,Ltd. |
|
| CP01 | Change in the name or title of a patent holder |