JP7196262B1 - Service provision system and service provision method - Google Patents

Abstract

Kind Code: A1 To easily develop a system that executes a plurality of microservices. Kind Code: A1 In a service providing system 1, a service server 10 notifies a transaction server 20 of the start of processing at the start of processing. Notifies the server 20 of the processing data. When an error occurs during processing, the service server 10 requests the transaction server 20 for the processing data notified immediately before, and acquires the processing data from the transaction server 20 . Subsequently, the service server 10 uses the acquired processing data to execute error processing to be executed when an error occurs. [Selection drawing] Fig. 1

Description

Article 30, Paragraph 2 of the Patent Act applies https://axis-edge. github. io/qmonus-sdk-programming-guide/transaction/transaction/https://axis-edge. github. io/qmonus-sdk-programming-guide/scenario/scenario/https://axis-edge. github. io/qmonus-sdk-programming-guide/overview/https://axis-edge. github. io/qmonus-docs/tutorial/tutorial4. html https://axis-edge. github. io/qmonus-developer-portal/QmonusIntro. pdf Posted on website October 27, 2020

The present invention relates to a service providing system and a service providing method.

In recent years, a microservice architecture is known, which realizes a digital business system by combining small functions called microservices. In a microservices architecture, each service is built and operated with an independent system and life cycle, and transaction management is also built with a consistency scope that is closed to the service. In addition, there is an increasing trend to create new value-added services that are a concept of consolidating multiple resources across various microservices.

JP 2020-64586 A

However, the conventional technology has the problem that a transaction management must be built for each service, and a system that executes multiple microservices cannot be built easily. For example, there is an increasing tendency to create new value-added services that are a concept of consolidating multiple resources across various microservices. In such cases, a new orchestration system with new transaction management is required. In addition, complex requirements are becoming more complicated, and the state machine differs for each service, so the development cost of the orchestration system rises.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a service providing system and a service providing method that can easily construct a system that executes a plurality of microservices.

In order to solve the above-described problems and achieve the object, the service providing system of the present invention is a service providing system having a plurality of service servers and a transaction server for managing transactions of each service server. a notification unit for notifying the transaction server of the start of processing when the server starts processing, and notifying the transaction server of processing data each time a predetermined unit of processing in a series of started processing is completed; an acquisition unit for requesting the transaction server for the processing data notified immediately before and acquiring the processing data from the transaction server when an error occurs during the processing; an error processing execution unit that uses the processing data to execute error processing to be executed when an error occurs, and the transaction server, upon receiving a processing start notification from the service server, updates the state of the processing. a management unit that manages transitions; a storage unit that stores the processed data in a storage unit when processing data is received from the service server; and a storage unit that receives a request for processing data from the service server. and a transmission unit that transmits the stored processing data to the service server.

According to the present invention, it is possible to easily develop a system that executes multiple microservices.

FIG. 1 is a block diagram showing an example of the configuration of a service providing system according to an embodiment. FIG. 2 is a block diagram illustrating an example of a configuration of a service server according to the embodiment; FIG. 3 is a block diagram showing an example of the configuration of a transaction server according to the embodiment; FIG. 4 is a diagram illustrating an example of data stored in a storage unit of a transaction server; FIG. 5 is a diagram for explaining state transition management by the transaction server. FIG. 6 is a diagram illustrating processing by the scenario server and the transaction server when a request is received from the API gateway. FIG. 7 is an example of a flowchart showing processing in the scenario server according to the embodiment. FIG. 8 is an example of a flowchart showing processing in the transaction server according to the embodiment. FIG. 9 is a diagram showing a computer that executes a program.

Embodiments of a service providing system and a service providing method according to the present application will be described below in detail with reference to the drawings. Note that the service providing system and service providing method according to the present application are not limited by this embodiment.

[Embodiment]
In the following embodiments, the configuration of the service providing system, the configuration of the service server, the configuration of the transaction server, and the flow of processing in the service server and transaction server according to the first embodiment will be described in order. explain.

[Configuration of service providing system]
A configuration of a service providing system 1 according to an embodiment will be described. FIG. 1 is a block diagram showing an example of the configuration of a service providing system according to an embodiment. As shown in FIG. 1, the service providing system 1 has a plurality of service servers 10A to 10C, a transaction server 20, an API (Application Programming Interface) gateway 30 and user terminals 40. FIG. Note that the service servers 10A to 10C will be referred to as the service server 10 when they are described without distinction. Moreover, the configuration shown in FIG. 1 is merely an example, and the specific configuration and the number of each device are not particularly limited. Regarding the form of the network shown in FIG. 1, each device may communicate via any communication network such as the Internet, LAN, or VPN (Virtual Private Network), whether wired or wireless.

In the service providing system 1, a common transaction server 20 performs transaction management for each microservice provided by a plurality of service servers 10A to 10C. Therefore, in the service providing system 1, it is possible to easily construct a system that executes a plurality of microservices without constructing transaction management for each microservice.

A plurality of service servers 10A to 10C are server devices that provide microservices. When each of the service servers 10A to 10C receives a request from the user terminal 40 via the API gateway 30, it executes processing related to microservices and transmits a response to the request to the user terminal 40. FIG.

The transaction server 20 performs transaction management for each microservice provided by each of the plurality of service servers 10A-10C. For example, when the service server 10 receives a begin notification from the service server 10 when the service server 10 starts a series of processes related to a service, the transaction server 20 assigns a transaction ID to the series of processes, and indicates the status of the processes. to manage.

The API gateway 30 has various functions for API utilization by API users. For example, API gateway 30 routes requests received from user terminal 40 to respective microservices.

The user terminal 40 is a device used for providing and using APIs. For example, the user terminal 40 transmits a microservice-related request to the service server 10 via the API gateway 30 and receives a response from the service server 10 via the API gateway 30 . The user terminal 40 may be any device, for example, an information processing device such as a tablet terminal, a notebook PC, a smart phone, or a PDA (Personal Digital Assistant).

As described above, in the service providing system 1 according to the embodiment, the common transaction server 20 performs transaction management for each microservice provided by each of the plurality of service servers 10A to 10C. Therefore, in the service providing system 1, it is possible to easily construct a system that executes a plurality of microservices without constructing transaction management for each microservice.

In other words, in the service providing system 1 according to the embodiment, the transaction management function itself that guarantees overall consistency across various different services is treated as a meta-micro service, and can be applied as a framework to various orchestration projects. . In addition, in the service providing system 1, the developer who defines the orchestration workflow of the service composite can focus only on business processing such as normal processing and cancellation processing without being conscious of transaction management, thereby improving productivity. It will be possible to increase the production of multiple service composite orchestration type microservices.

[Service server]
Next, the service server 10 will be explained. FIG. 2 is a block diagram illustrating an example of a configuration of a service server according to the embodiment; As shown in FIG. 2 , the service server 10 has a communication processing section 11 , a control section 12 and a storage section 13 .

The communication processing unit 11 communicates with other devices wirelessly or by wire. The communication processing unit 11 is a communication interface that transmits and receives various information to and from other devices connected via a network or the like. The communication processing unit 11 is realized by a NIC (Network Interface Card) or the like, and performs communication between another device and the control unit 12 (described later) via an electric communication line such as a LAN (Local Area Network) or the Internet. . For example, the communication processing unit 11 receives a request from the API gateway 30 and transmits a response to the request to the API gateway 30 .

The storage unit 13 is a storage device such as an HDD (Hard Disk Drive), an SSD (Solid State Drive), an optical disc, or the like. Note that the storage unit 13 may be a rewritable semiconductor memory such as a RAM (Random Access Memory), a flash memory, or an NVSRAM (Non Volatile Static Random Access Memory). The storage unit 13 stores an OS (Operating System) and various programs executed by the service server 10 . Further, the storage unit 13 stores various information used in executing the program.

The control unit 12 controls the service server 10 as a whole. The control unit 12 is, for example, an electronic circuit such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit), or an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). The control unit 12 also has an internal memory for storing programs defining various processing procedures and control data, and executes each processing using the internal memory. Further, the control unit 12 functions as various processing units by running various programs. The control unit 12 has a creation unit 12a, a notification unit 12b, an acquisition unit 12c, and an error processing unit 12d.

The creator 12a creates a scenario for executing a service. Specifically, the creating unit 12a accepts a developer's operation on a scenario editor for creating a scenario, so that endpoints are defined on the scenario editor and a workflow is created. The developer who defines the workflow here can focus only on business processing such as normal processing and cancellation processing without being conscious of transaction management, which improves productivity. Also, the developer needs to describe the normal process and the cancel process when an error occurs in the flow editor. can be simplified.

The notification unit 12b notifies the transaction server 20 of the start of processing at the start of processing, and notifies the transaction server 20 of processing data each time a predetermined unit of processing in the series of started processing is completed. For example, the notification unit 12b divides a series of microservice processes into preset blocks, creates a snapshot each time a block process is completed, and checks the timing at which the block process is completed. As a point, the snapshot is notified to the transaction server 20 and stored in the transaction server 20 .

If an error occurs during processing, the acquisition unit 12c requests the transaction server 20 for the processing data notified immediately before, and acquires the processing data from the transaction server 20 . For example, when an error occurs during processing, the acquisition unit 12c executes the processing at the time of error occurrence and notifies the transaction server 20 of abort. Then, the acquisition unit 12c acquires a snapshot of the processing data of the immediately preceding checkpoint from the transaction server 20. FIG.

The error processing unit 12d uses the processing data acquired by the acquisition unit 12c to execute error processing to be executed when an error occurs. For example, the error processing unit 12d uses a snapshot acquired from the transaction server 20 to execute cancellation processing when an error occurs, or roll back processing to the immediately preceding checkpoint.

[Transaction Server]
Next, the transaction server 20 will be explained. FIG. 3 is a block diagram showing an example of the configuration of a transaction server according to the embodiment; As shown in FIG. 3, the transaction server 20 has a communication processing unit 21, a control unit 22 and a storage unit 23.

The communication processing unit 21 communicates with other devices wirelessly or by wire. The communication processing unit 21 is a communication interface that transmits and receives various information to and from other devices connected via a network or the like. The communication processing unit 21 is realized by a NIC (Network Interface Card) or the like, and performs communication between another device and the control unit 22 (described later) via an electric communication line such as a LAN (Local Area Network) or the Internet. .

The storage unit 23 is a storage device such as an HDD (Hard Disk Drive), an SSD (Solid State Drive), an optical disc, or the like. Note that the storage unit 23 may be a rewritable semiconductor memory such as a RAM (Random Access Memory), a flash memory, or an NVSRAM (Non Volatile Static Random Access Memory). The storage unit 23 stores an OS (Operating System) and various programs executed by the transaction server 20 . Further, the storage unit 23 stores various information used in executing the program.

For example, the storage unit 23 stores snapshots, endpoint information, and indexes saved at checkpoints in association with transaction IDs that uniquely identify transactions. The storage unit 23 also stores lock information for exclusive control of transactions. Locks are automatically released when a transaction is committed. Also, for example, as illustrated in FIG. 4, the storage unit 23 stores a status indicating the state of the transaction in association with the transaction ID. The storage unit 23 updates the status data each time the state of the transaction corresponding to the transaction ID changes.

Here, management of state transition by the transaction server 20 will be described with reference to FIG. FIG. 5 is a diagram for explaining state transition management by the transaction server. The transaction server 20 manages transactions through a state machine as illustrated in FIG. As exemplified in FIG. 5, the transaction server 20 has the following statuses: "Processing", "Complete", "Suspending", "Aborted", "Cancelling", "Cancelled", "Recovery Processing", "Recovery Complete", Transition to any of "Force Recovery Complete".

For example, when the transaction server 20 receives a begin notification from the service server 10, the transaction ID is issued and the status is changed to "Processing". When the transaction server 20 receives from the service server 10 a commit notification requesting confirmation of the transaction processing, the transaction server 20 transitions to the status "Complete" and then terminates the transaction.

Also, for example, when the transaction server 20 receives an abort notification from the service server 10 or when a timeout occurs, the transaction server 20 transitions to the status "Aborted". Then, for example, when the transaction server 20 performs cancellation processing or forced cancellation processing, the transaction server 20 changes the status to “canceled”. When the transaction server 20 receives a commit notification from the service server 10, the transaction server 20 transitions to "Cancelled" to confirm the cancellation process, and then ends the transaction.

The control unit 22 controls the transaction server 20 as a whole. The control unit 22 is, for example, an electronic circuit such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit), or an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). The control unit 22 also has an internal memory for storing programs defining various processing procedures and control data, and executes each processing using the internal memory. Further, the control unit 22 functions as various processing units by running various programs. The control unit 22 has a management unit 22a, a storage unit 22b, and a transmission unit 22c.

When the management unit 22a receives a notification of the start of processing from the service server 10, the management unit 22a manages the state transition of the processing. For example, when receiving a begin notification from the service server 10, the management unit 22a assigns a new transaction ID and stores it in the storage unit 23 as the status "Processing" of the transaction ID. Then, when the management unit 22a receives a commit notification requesting confirmation of transaction processing from the service server 10, the management unit 22a changes the status to "Complete", and then ends the management of the transaction.

Further, for example, when the management unit 22a receives an abort notification from the service server 10 for a transaction whose status is "Processing", the management unit 22a assigns the status stored in the storage unit 23 to the transaction ID of the transaction. Update the status to "Aborted".

Further, the management unit 22a performs rollback processing using the processing data stored in the storage unit 23 when a timeout occurs. For example, when a timeout (transaction timeout) occurs for a transaction whose status is "Processing", the management unit 22a changes the status corresponding to the transaction ID of the transaction stored in the storage unit 23 to "Aborted". ”. Then, the management unit 22a reads the snapshot corresponding to the transaction ID of the transaction from the storage unit 23, and rolls back the processing to the previous checkpoint using the read snapshot.

Upon receiving the processing data from the service server 10 , the storage unit 22 b stores the processing data in the storage unit 23 . For example, when receiving a snapshot from the service server 10, the storage unit 22b stores the snapshot, the endpoint information, and the index in the storage unit 23 in association with the transaction ID. Further, for example, the storage unit 22b may receive any remaining required time from the service server 10 while receiving the snapshot. When the storage unit 22b receives this arbitrary remaining required time, the aforementioned management unit 22a extends the transaction timeout so as to meet the remaining required time if the remaining required time cannot be satisfied by the transaction timeout. In other words, if the time from the present to the transaction timeout is shorter than the desired remaining time, the management unit 22a extends the transaction timeout so as to satisfy the desired remaining time. As a result, the service server 10 side can extend the time-out period according to the processing, so that it is possible to improve the detection accuracy of the occurrence of an abnormality.

When receiving a request for processing data from the service server 10 , the transmission unit 22 c transmits the processing data stored in the storage unit 23 to the service server 10 . For example, when the transmission unit 22c receives an abort notification from the service server 10 and also receives a snapshot request, the transmission unit 22c transmits a snapshot of the processing data of the last checkpoint to the service server 10 . That is, when an error occurs during processing, the service server 10 requests the transaction server 20 for a snapshot of the processing data of the immediately preceding checkpoint in order to execute the processing at the time of error occurrence.

Processing by the scenario server 10 and the transaction server 20 when a request is received from the API gateway 30 will now be described with reference to FIG. FIG. 6 is a diagram for explaining processing by the scenario server and the transaction server when a request is received from a user terminal. As illustrated in FIG. 6, when the scenario server 10 receives a request by accessing the endpoint from the API gateway 30, it verifies the request and starts a series of processing related to the service. Here, the scenario server 10 notifies the transaction server 20 of begin when starting a series of processing related to the service.

Then, the scenario server 10 sequentially executes processing from block 0 to block n, creates a snapshot each time the processing of a block is completed, and creates a snapshot using the timing at which processing of the block is completed as a checkpoint. Notifies the transaction server 20 and causes the transaction server 20 to store it. When the transaction server 20 receives from the service server 10 a commit notification requesting confirmation of the transaction processing, the transaction server 20 transitions to the status "Complete" and then terminates the transaction.

If an error occurs during processing, the scenario server 10 may perform recovery processing to proceed with the processing, or may perform cancellation processing to roll back the processing to the previous checkpoint. . Whether the scenario server 10 performs recovery processing or cancellation processing when an error occurs may be set in advance, or may be determined according to conditions.

For example, in the example of FIG. 6, if an error occurs in the processing of block 0, the scenario server 10 executes error recovery processing and notifies the transaction server 20 of abort. Then, the scenario server 10 acquires a snapshot of the processed data of the immediately preceding checkpoint from the transaction server 20 . Then, the scenario server 10 uses the snapshot acquired from the transaction server 20 to perform recovery processing and complete the processing of block 0 .

Also, since an error has occurred in the processing of block n, the scenario server 10 executes the cancel processing at the time of error occurrence and notifies the transaction server 20 of abort. Then, the scenario server 10 acquires a snapshot of the processed data of the immediately preceding checkpoint from the transaction server 20 . Then, the scenario server 10 uses the snapshot obtained from the transaction server 20 to perform cancellation processing and rolls back the processing to the previous checkpoint.

Also, the transaction server 20 may detect the occurrence of an error in the scenario server 10 and perform recovery processing or cancellation processing. For example, when a timeout occurs for a transaction whose status is "Processing", the transaction server 20 updates the status corresponding to the transaction ID of the transaction stored in the storage unit 23 to "Aborted". . Then, the transaction server 20 reads the snapshot corresponding to the transaction ID of the transaction from the storage unit 23, and uses the read snapshot to roll back the processing to the previous checkpoint.

[Processing procedure of scenario server and transaction server]
Next, an example of processing procedures by the scenario server 10 and the transaction server 20 according to the first embodiment will be described with reference to FIGS. 7 and 8. FIG. FIG. 7 is a flowchart illustrating an example of processing in the scenario server according to the embodiment; 8 is a flowchart illustrating an example of processing in the transaction server according to the embodiment; FIG.

First, an example of processing of the scenario server 10 will be described with reference to FIG. As illustrated in FIG. 7, when the notification unit 12b of the scenario server 10 receives a request from the API server 30 and starts microservice-related processing (Yes at step S101), it notifies the transaction server 20 of begin (step S102). Then, the acquiring unit 12c of the scenario server 10 determines whether the processing of the block being processed has been completed (step S103).

Then, when the acquiring unit 12c determines that an error has occurred in the middle of processing and the processing of the block has not been completed (No at step S103), it notifies the transaction server 20 of abort (step S104). Subsequently, the acquiring unit 12c acquires a snapshot of the processed data of the immediately preceding checkpoint from the transaction server 20 (step S105). After that, the error processing unit 12d performs recovery processing using the acquired processing data (step S106), and returns to step S103.

Further, when the obtaining unit 12c determines that an error has occurred in the middle of the processing and the processing of the block has been completed (Yes at step S103), the notification unit 12b determines whether the processing of all blocks has been completed. (step S107). As a result, if the notification unit 12b determines that the processing of all blocks has not been completed (No at step S107), it instructs the transaction server 20 to take a checkpoint snapshot (step S108), and proceeds to step S103. return.

If the notification unit 12b determines that the processing of all blocks has been completed (Yes at step S107), it notifies the transaction server 20 of commit requesting confirmation of the transaction processing (step S109), and ends the processing. do.

Next, an example of processing of the transaction server 20 will be described using FIG. As illustrated in FIG. 8, when the management unit 22a of the transaction server 20 receives a begin notification from the service server 10 (Yes at step S201), it issues a new transaction ID (step S202).

Then, the management unit 22a determines whether or not a commit notification requesting confirmation of transaction processing has been received from the service server 10 (step S203). As a result, when the management unit 22a determines that it has not received a commit notification requesting confirmation of transaction processing from the service server 10 (No at step S203), it receives a snapshot instruction from the service server 10. (step S204). As a result, when a snapshot instruction is received from the service server 10 (Yes at step S204), the storage unit 22b stores the snapshot in the storage unit 23 in association with the transaction ID (step S205). Return to the processing of S203.

If the management unit 22a has not received a snapshot instruction from the service server 10 (No at step S204), the management unit 22a determines whether a timeout has occurred or an abort has been received from the service server 10 (step S206). As a result, when a timeout occurs or an abort is received from the service server 10 (Yes at step S206), the transmission unit 22c performs recovery processing (step S207). For example, the transmission unit 22c performs recovery processing by transmitting a snapshot of the processing data of the immediately preceding checkpoint to the service server 10 .

In addition, in the processing of step S203, when the management unit 22a determines that a commit notification requesting confirmation of transaction processing has been received from the service server 10 (Yes in step S203), the status of the transaction ID is changed to "Complete." ” (step S208), and then ends the management of the transaction.

[Effects of Embodiment]
In the service providing system 1, the service server 10 notifies the transaction server of the start of processing at the start of processing. to notify you. When the transaction server 20 receives a processing start notification from the service server 10, it manages the state transition of the processing. Subsequently, when the transaction server 20 receives the processing data from the service server 10 , it stores the processing data in the storage unit 23 . When an error occurs during processing, the service server 10 requests the transaction server 20 for the processing data notified immediately before, and acquires the processing data from the transaction server 20 . Subsequently, the service server 10 uses the acquired processing data to execute error processing to be executed when an error occurs. After that, when the transaction server 20 receives a request for processing data from the service server 10 , it transmits the processing data stored in the storage unit 23 to the service server 10 .

As described above, in the service providing system 1 according to the embodiment, the common transaction server 20 performs transaction management for each microservice provided by each of the plurality of service servers 10A to 10C. Therefore, in the service providing system 1, it is possible to easily construct a system that executes a plurality of microservices without constructing transaction management for each microservice.

In other words, in the service providing system 1 according to the embodiment, the transaction management function itself that guarantees overall consistency across various different services is treated as a meta-micro service, and can be applied as a framework to various orchestration projects. . As a result, in the service providing system 1, developers who define service-composite orchestration workflows can focus only on business processing such as normal processing and cancellation processing without being conscious of transaction management, thereby improving productivity. . In addition, it becomes possible to increase the production of multiple service complex orchestration type microservices.

Further, when a timeout occurs, the transaction server 20 of the service providing system 1 performs rollback processing using the processing data stored in the storage unit 23. Therefore, even if the service server 10 crashes during the workflow, However, it is possible to rollback.

In addition, the service server 10 of the service providing system 1 creates a snapshot each time a process for each preset unit is completed, and uses the timing at which the process is completed as a checkpoint to store the snapshot in the transaction server 20 . to notify. Therefore, the service server 10 can perform rollback processing and the like using the snapshot stored in the transaction server when an error occurs.

[System configuration, etc.]
Also, each component of each device illustrated is functionally conceptual, and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution and integration of each device is not limited to the one shown in the figure, and all or part of them can be functionally or physically distributed and integrated in arbitrary units according to various loads and usage conditions. Can be integrated and configured. Furthermore, all or any part of each processing function performed by each device is realized by a CPU or GPU and a program analyzed and executed by the CPU or GPU, or as hardware by wired logic can be realized.

Further, among the processes described in this embodiment, all or part of the processes described as being automatically performed can be performed manually, or the processes described as being performed manually can be performed manually. All or part of this can also be done automatically by known methods. In addition, information including processing procedures, control procedures, specific names, and various data and parameters shown in the above documents and drawings can be arbitrarily changed unless otherwise specified.

[program]
It is also possible to create a program in which the processing executed by the service server 10 or the transaction server 20 described in the above embodiment is written in a computer-executable language. For example, it is possible to create a program in which the processing executed by the service server 10 or the transaction server 20 in the embodiment is written in a computer-executable language. In this case, the same effects as those of the above embodiments can be obtained by having the computer execute the program. Further, such a program may be recorded in a computer-readable recording medium, and the program recorded in this recording medium may be read by a computer and executed to realize processing similar to that of the above embodiments.

FIG. 9 is a diagram showing a computer that executes a program. As illustrated in FIG. 9, computer 1000 includes, for example, memory 1010, CPU 1020, hard disk drive interface 1030, disk drive interface 1040, serial port interface 1050, video adapter 1060, and network interface 1070. , and these units are connected by a bus 1080 .

The memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM 1012 as illustrated in FIG. The ROM 1011 stores a boot program such as BIOS (Basic Input Output System). Hard disk drive interface 1030 is connected to hard disk drive 1090 as illustrated in FIG. A disk drive interface 1040 is connected to the disk drive 1100 . A removable storage medium such as a magnetic disk or optical disk is inserted into the disk drive 1100 . Serial port interface 1050 is connected to mouse 1110 and keyboard 1120, for example. Video adapter 1060 is connected to display 1130, for example.

Here, as illustrated in FIG. 9, the hard disk drive 1090 stores an OS 1091, application programs 1092, program modules 1093, and program data 1094, for example. That is, the above program is stored, for example, in hard disk drive 1090 as a program module in which instructions to be executed by computer 1000 are described.

Various data described in the above embodiments are stored as program data in the memory 1010 or the hard disk drive 1090, for example. Then, the CPU 1020 reads the program modules 1093 and program data 1094 stored in the memory 1010 and the hard disk drive 1090 to the RAM 1012 as necessary, and executes various processing procedures.

Note that the program module 1093 and program data 1094 related to the program are not limited to being stored in the hard disk drive 1090. For example, they may be stored in a removable storage medium and read by the CPU 1020 via a disk drive or the like. . Alternatively, the program module 1093 and program data 1094 related to the program are stored in another computer connected via a network (LAN (Local Area Network), WAN (Wide Area Network), etc.), and are transmitted via the network interface 1070. It may be read by CPU 1020 .

The above-described embodiments and modifications thereof are included in the scope of the invention described in the claims and their equivalents, as well as in the technology disclosed in the present application.

1 Service Providing System 10, 10A to 10C Service Server 11, 21 Communication Processing Unit 12, 22 Control Unit 12a Creation Unit 12b Notification Unit 12c Acquisition Unit 12d Error Processing Unit 13, 23 Storage Unit 20 Transaction Server 30 API Gateway 40 User Terminal

Claims (4)

A service providing system having a plurality of service servers and a transaction server for managing transactions of each service server,
Each service server
a notification unit that notifies the transaction server of the start of processing at the start of processing, and notifies the transaction server of processing data each time a predetermined unit of processing in a series of started processing is completed;
an acquisition unit that, when an error occurs during the processing, requests the transaction server for the processing data notified immediately before and acquires the processing data from the transaction server;
an error processing execution unit that executes error processing to be executed when an error occurs using the processing data acquired by the acquisition unit;
The transaction server is
a management unit that manages the transition of the state of the processing when a notification of the start of processing is received from the service server;
a storage unit that, upon receiving processing data from the service server, stores the processing data in a storage unit;
and a transmitting unit configured to transmit the processed data stored in the storage unit to the service server when a request for the processed data is received from the service server. 2. The service providing system according to claim 1, wherein, when a timeout occurs, the management section performs rollback processing using the processing data stored in the storage section. The notification unit is configured to create a snapshot each time a process for each preset unit is completed, and to notify the transaction server of the snapshot with the timing of completion of the process as a checkpoint. 2. The service providing system according to claim 1. A service providing method executed by a service providing system having a plurality of service servers and a transaction server for managing transactions of each service server,
A notification step in which each service server notifies the transaction server of the start of processing at the start of processing, and notifies the transaction server of processing data each time a predetermined unit of processing in the series of processing that has been started is completed. When,
a management step of, when the transaction server receives a processing start notification from the service server, managing the state transition of the processing;
a storing step of, when the transaction server receives processing data from the service server, storing the processing data in a storage unit;
an acquisition step of requesting the transaction server for the processing data notified immediately before and acquiring the processing data from the transaction server when an error occurs during the processing;
an error processing execution step in which each service server executes error processing to be executed when an error occurs using the processing data acquired in the acquisition step;
and a transmission step of transmitting, when the transaction server receives a request for processing data from the service server, the processing data stored in the storage unit to the service server.

Images