Distributed asynchronous remote service arrangement and calling technology
A remote service and distributed technology, applied in the Internet field, can solve the problems of not receiving response results immediately, low system processing capacity, blocking and waiting for results, etc., to improve compatibility and execution efficiency, improve service utilization, and improve throughput volume effect
- Summary
- Abstract
- Description
- Claims
- Application Information
AI Technical Summary
Problems solved by technology
Method used
Image
Examples
Embodiment 1
[0054] refer to figure 1 , is a distributed asynchronous remote service orchestration and invocation system disclosed in the present invention, including a control center 1 , multiple application containers 2 and multiple service gateways 3 . The control center 1 is used to arrange several service processes, each service process corresponds to a corresponding service, and each service process includes at least two service nodes. The application container 2 has a one-to-one correspondence with the service nodes, and when the application container 2 is started, it will automatically register the corresponding service node with the control center 1 . The service gateway 3 has a one-to-one correspondence with the service process and is bound to the corresponding service process. After the service process binding is completed, the service gateway 3 can call the corresponding service process.
[0055] refer to figure 1 , the control center 1 includes a service aggregation module 1...
Embodiment 2
[0058] refer to image 3 The difference between this embodiment and Embodiment 1 is that each service process includes a first node 4 and a second node 5, the first node 4 is the starting service node, and the second node 5 is the terminating service node. The service process shares the first node 4 and the second node 5 , that is, each service request enters the corresponding service process from the first node 4 and outputs response data from the second node 5 . Wherein, the first node 4 and the second node 5 are any two of the service nodes. In this embodiment, the service node a is the first node 4 , and the service node g is the second node 5 .
Embodiment 3
[0060] refer to figure 1 , the difference between this embodiment and the first embodiment is that the application container 2 is divided into a first-class characteristic container 23 and a second-type characteristic container 24, and each second-type characteristic container 24 corresponds to a spare container 6, and each spare container 6 corresponds to a A backup node with the same function as the service node of the corresponding type-two feature container 24 . Among them, the first type of feature container 23 is the application container 2 whose use frequency is less than the set value, and the second type of feature container 24 is the application container 2 whose use frequency is greater than the set value. When the standby container 6 is started, it will also automatically register its standby node to the control center 1. When the service process associated with the corresponding service node reaches the set threshold and the service process needs to use the functi...
PUM
Login to View More Abstract
Description
Claims
Application Information
Login to View More 


