CN114461424A - Inter-unit service discovery method, device and system under unitized deployment architecture - Google Patents

Abstract

The invention provides a method, a device and a system for discovering inter-unit services under a unit deployment architecture, which can be applied to the field of finance, wherein the invention takes a cross-unit service manager as an execution main body and comprises the following steps: monitoring the starting action of the cross-unit service, and registering the service provider information of the cross-unit service; and sending the registered service provider information to the cross-unit calling server so that the cross-unit calling server sends the service provider information to the service consumer. The method and the device solve the problem that under the service scene that a transaction opponent exists or part of services cannot be unitized, the transaction cannot be closed in the unit, and the transaction between two cross-unit services is realized.

Description

Inter-unit service discovery method, device and system under unitized deployment architecture

technical field

The present application belongs to the field of computer technology, and in particular, relates to an inter-unit service discovery method, device and system under a unitized deployment architecture.

Background technique

The unitized architecture is to use the unit as the basic unit of system deployment. Several units are deployed in all computer rooms of the whole station. All the applications required by the system are deployed in any unit. The data is the full amount of data according to a certain dimension (usually the customer dimension) part of the horizontal division. Unitization is the process of designing services and data to conform to the characteristics of a unit. Under the background of unitized deployment architecture, under normal circumstances, transactions can basically be closed in this unit, but in business scenarios where there is a counterparty or some services cannot be unitized, transactions cannot be closed in this unit, so how to Implementing transactions between two services in different units is a problem.

At present, for cross-unit scenarios, the main technical solutions adopted in the industry include: zProxy solution, antVIP solution and registry synchronization solution.

As shown in Figure 1, when the consumer service is called in the zProxy scheme, if the target unit is not the unit, the zProxy node will be automatically screened, and then the zProxy node will call the service of the target unit by RPC. However, the proxy node needs to subscribe to a large number of services, and there is a large subscription cache pressure. At the same time, the cross-unit service call is forwarded by the zProxy node, which will increase the cost of one service call.

As shown in Figure 2, when the consumer service is called in the antVIP scheme, if the target unit is not the unit, the antVIP rule is used to assemble the URL address, the provider address of the target unit is obtained, and the service is called by RPC. However, this solution requires the cooperation of the cloud platform, and the manual configuration method cannot guarantee the timeliness.

As shown in Figure 3, data is synchronized between registration centers, and each registration center has a complete list of service providers; when the consumer service is invoked, the provider list can be filtered according to the target unit. However, the zookeeper and the sofa registration center used by the bank do not support data synchronization, and according to the research, there is no suitable zookeeper/sofa data synchronization tool; at the same time, the consumer needs to subscribe to the service providers of all units, and there is pressure to subscribe to the cache and the number of connections.

SUMMARY OF THE INVENTION

The present application provides an inter-unit service discovery method, device and system under a unitized deployment architecture, so as to at least solve the problem of the large subscription cache pressure in the cross-unit service in the prior art, the overhead is high, and the manual configuration method cannot guarantee the timeliness And other issues.

According to an aspect of the present application, an inter-unit service discovery method under a unitized deployment architecture is provided, using a cross-unit service manager as an execution subject, including:

Monitor the startup action of the cross-unit service, and register the service provider information of the cross-unit service;

The registered service provider information is sent to the cross-unit invocation server, so that the cross-unit invocation server sends the service provider information to the service consumer.

In a specific embodiment, the inter-unit service discovery method under the unitized deployment architecture further includes:

Monitor the information change action of the service provider, update the service provider information of the cross-unit service, and push it to the cross-unit invocation server.

According to another aspect of the present application, an inter-unit service discovery method under a unitized deployment architecture is also provided to invoke a server across units, including:

Receive service provider registration or change information sent by the cross-unit service manager and forward it to the service consumer;

Parse the service call request initiated by the service consumer to obtain the address of the service provider;

According to the address of the service provider, a call is made to the server of the service provider based on the soft load balancing algorithm.

In one embodiment, the inter-unit service discovery method under the unitized deployment architecture further includes:

When initiating a call to the service provider fails, the server of other service providers in the pre-stored local service provider address list is called by means of a point-to-point RPC connection.

According to a third aspect of the present application, an inter-unit service discovery system under a unitized deployment architecture is provided, including: several monitoring units respectively deployed on the service provider, a cross-unit service manager and a cross-unit invocation server; The monitoring unit is in communication connection with the cross-unit service manager, and the cross-unit service manager is in communication and connection with the cross-unit invocation server;

The monitoring unit is used to monitor the actions of the service provider;

The cross-unit service manager is used to manage and register cross-unit services;

The cross-unit invocation server is used to implement subscription and invocation of cross-unit transactions.

According to a fourth aspect of the present application, an inter-unit service discovery device under a unitized deployment architecture is provided, using the cross-unit management server as the execution body, including:

The monitoring unit is used to monitor the startup action of the cross-unit service and register the service provider information of the cross-unit service;

The information sending unit is configured to send the registered service provider information to the cross-unit invocation server, so that the cross-unit invocation server sends the service provider information to the service consumer.

In one embodiment, the inter-unit service discovery apparatus under the unitized deployment architecture further includes:

The information changing unit is used to monitor the information changing action of the service provider, update the service provider information of the cross-unit service, and then push it to the cross-unit calling server.

According to the fifth aspect of the present application, an inter-unit service discovery device under a unitized deployment architecture is also provided with the cross-unit invocation server as the execution body, including:

a receiving unit, configured to receive the service provider registration or change information sent by the cross-unit service manager and forward it to the service consumer;

The parsing unit is used to parse the service invocation request initiated by the service consumer to obtain the address of the service provider;

The calling unit is configured to initiate a call to the server of the service provider based on the soft load balancing algorithm according to the address of the service provider.

In one embodiment, the inter-unit service discovery apparatus under the unitized deployment architecture further includes:

The standby invocation unit is used for invoking the servers of other service providers in the pre-stored local service provider address list by adopting the RPC long connection point-to-point mode when the invocation to the service provider fails.

In this application, by deploying several units in all computer rooms of the whole station, all applications required by the system are deployed in any unit, and then the service and data are designed and transformed to conform to the characteristics of the unit. In the context of the unitized deployment architecture, Under normal circumstances, the service provider registers the services it provides with the registration center in this unit when it starts up, and the service consumer subscribes the services it needs to the registration center in this unit when it starts up. Therefore, under normal circumstances, the transaction is basically A closed loop can be realized in this unit. This application solves the problem that the transaction cannot be closed-loop within the unit to realize the transaction between two cross-unit services in a business scenario where a counterparty exists or some services cannot be unitized.

Description of drawings

In order to explain the embodiments of the present invention or the technical solutions in the prior art more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained according to these drawings without creative efforts.

1 to 3 are structural diagrams of a cross-unit service invocation system in the prior art.

FIG. 4 is a structural block diagram of an inter-unit service discovery system under a unitized deployment architecture provided by the present application.

FIG. 5 is a flowchart of an inter-unit service discovery method provided by the present application with a cross-unit management server as an execution subject.

FIG. 6 is a flowchart of an inter-unit service discovery method with a cross-unit invocation server as an execution subject provided by the present application.

FIG. 7 is a structural block diagram of an inter-unit service discovery apparatus with a cross-unit management server as an execution subject provided by the present application.

FIG. 8 is a structural block diagram of an inter-unit service discovery apparatus with a cross-unit invocation server as an execution subject provided by the present application.

FIG. 9 is a specific implementation manner of an electronic device in an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

Under the background of unitized deployment architecture, under normal circumstances, transactions can basically be closed in this unit, but in business scenarios where there is a counterparty or some services cannot be unitized, transactions cannot be closed in this unit, so how to Implementing transactions between two services in different units is a problem.

In order to solve this problem, the present application provides an inter-unit service discovery system under a unitized deployment architecture, as shown in FIG. 4 , including: several monitoring units respectively deployed on the service provider, a cross-unit service manager and a cross-unit service manager. The unit call server; the monitoring unit is communicated and connected with the cross-unit service manager, and the cross-unit service manager is communicated and connected with the cross-unit call server;

The monitoring unit is used to monitor the actions of the service provider;

The cross-unit service manager is used to manage and register cross-unit services;

The cross-unit invocation server is used to implement subscription and invocation of cross-unit transactions.

The unitized architecture is to use the unit as the basic unit of system deployment. Several units are deployed in all computer rooms of the whole station. All applications required by the system are deployed in any unit. The data is a part of the full data divided according to the customer dimension level. . Unitization is the process of designing services and data to conform to the characteristics of a unit.

In a specific embodiment, under the background of the unitized deployment architecture, under normal circumstances, the service provider registers the service provided by itself with the registration center in the unit when it is started. When the service consumer starts, it also subscribes to the service it needs from the registration center in this unit. Therefore, under normal circumstances, transactions can basically be closed-loop in this unit.

However, in the business scenario where there is a counterparty or some services cannot be unitized, the transaction cannot be closed in this unit. Therefore, as shown in the following figure, for cross-unit services, the present invention proposes a cross-unit service discovery method. Specifically set up a cross-unit service manager (control state) and a cross-unit call mechanism (running state) to implement calls between cross-unit services.

Cross-unit service manager: It is mainly used for the management and registration of cross-unit services. When the cross-unit service starts, the provider service information will be automatically registered on the cross-unit service manager. After the registration is successful, the registration information of the service will be displayed. It will be automatically pushed to the cross-unit invocation mechanism. If there is a change in the cross-unit provider service, such as a new provider going online or the original provider going offline, it will also be automatically updated and registered in the cross-unit service manager and will be updated. The post state is automatically pushed to the cross-unit invocation mechanism.

Cross-unit invocation mechanism: The function of this mechanism is to realize the subscription and invocation of cross-unit transactions. After receiving the provider information sent by the cross-unit service manager, the cross-unit invocation mechanism will return the service provider address list to the consumer for supply. When the consumer calls, if the service information of the provider changes (for example, a new provider goes online, or the original provider goes offline), the cross-unit call mechanism will also push the changed data to the consumer based on the long connection, so that the consumer can pass the The mechanism automatically subscribes and calls cross-unit providers to realize cross-unit transaction scenarios.

Based on the above system, with the cross-unit service manager as the execution body, the present application also provides an inter-unit service discovery method under a unitized deployment architecture, as shown in FIG. 5 , including:

S501: Monitor the start action of the cross-unit service, and register the service provider information of the cross-unit service.

S502: Send the registered service provider information to the cross-unit invocation server, so that the cross-unit invocation server sends the service provider information to the service consumer.

In one embodiment, the inter-unit service discovery method under the unitized deployment architecture further includes:

Monitor the information change action of the service provider, update the service provider information of the cross-unit service, and push it to the cross-unit invocation server.

In a specific embodiment, for the provider of cross-unit services, when it starts up, it not only registers the service provided by itself in the service registration center in its unit, but also automatically registers the cross-unit service provided by itself in the cross-unit service. The service manager, when the service goes offline, will also be automatically registered in the cross-unit service manager, which is convenient for later management of the service. After the cross-unit service is successfully registered with the cross-unit service manager, the cross-unit manager will automatically push the information of the service to the cross-unit call mechanism. At the same time, if the cross-unit service is registered offline, the offline information will also be automatically pushed. to the cross-unit invocation mechanism.

Taking the cross-unit invocation server as the execution body, the present application also provides an inter-unit service discovery method under the unitized deployment architecture, as shown in FIG. 6 , including:

S601: Receive the service provider registration or modification information sent by the cross-unit service manager and forward it to the service consumer.

S602: Parse the service invocation request initiated by the service consumer to obtain the address of the service provider.

S603: According to the address of the service provider, initiate a call to the server of the service provider based on the soft load balancing algorithm.

In one embodiment, the inter-unit service discovery method under the unitized deployment architecture further includes:

When initiating a call to the service provider fails, the server of other service providers in the pre-stored local service provider address list is called by means of a point-to-point RPC connection.

In a specific embodiment, for a consumer that wants to invoke services in other units, during the startup process of the consumer, the cross-unit invocation mechanism will also query the provider address list to be invoked. From the provider address list, Based on the soft load balancing algorithm, select one provider to call, and if the call fails, select another provider to call. The service call adopts the RPC method of java, and uses the long connection for point-to-point communication. In this way, it can subscribe to the cross-unit service that it needs to call. At the same time, when the cross-unit calling mechanism receives a notification of provider information change pushed by the cross-unit service manager, it will also push the change data to the consumer based on the long connection. .

Based on the same inventive concept, the embodiments of the present application also provide an inter-unit service discovery apparatus under a unitized deployment architecture, which can be used to implement the methods described in the foregoing embodiments, as described in the following embodiments. Since the principle of solving the problem of the inter-unit service discovery device under the unitized deployment architecture is similar to that of the inter-unit service discovery method under the unitized deployment architecture, the implementation of the inter-unit service discovery device under the unitized deployment architecture can refer to the unitary deployment. The implementation of the inter-unit service discovery method under the architecture. As used below, the term "unit" or "module" may be a combination of software and/or hardware that implements a predetermined function. Although the systems described in the following embodiments are preferably implemented in software, implementations in hardware, or a combination of software and hardware, are also possible and contemplated.

Taking the cross-unit management server as the execution body, an inter-unit service discovery device under the unitized deployment architecture is provided, as shown in Figure 7, including:

A monitoring unit 701, configured to monitor the startup action of the cross-unit service, and register the service provider information of the cross-unit service;

The information sending unit 702 is configured to send the registered service provider information to the cross-unit invocation server, so that the cross-unit invocation server sends the service provider information to the service consumer.

In one embodiment, the inter-unit service discovery apparatus under the unitized deployment architecture further includes:

The information changing unit is used to monitor the information changing action of the service provider, update the service provider information of the cross-unit service, and then push it to the cross-unit calling server.

In a specific embodiment, for the provider of cross-unit services, when it starts up, it not only registers the service provided by itself in the service registration center in its unit, but also automatically registers the cross-unit service provided by itself in the cross-unit service. The service manager, when the service goes offline, will also be automatically registered in the cross-unit service manager, which is convenient for later management of the service. After the cross-unit service is successfully registered with the cross-unit service manager, the cross-unit manager will automatically push the information of the service to the cross-unit call mechanism. At the same time, if the cross-unit service is registered offline, the offline information will also be automatically pushed. to the cross-unit invocation mechanism.

Taking the cross-unit invocation server as the execution body, an inter-unit service discovery device under the unitized deployment architecture is also provided, as shown in Figure 8, including:

A receiving unit 801, configured to receive the service provider registration or change information sent by the cross-unit service manager and forward it to the service consumer;

A parsing unit 802, configured to parse a service invocation request initiated by a service consumer to obtain an address of a service provider;

The calling unit 803 is configured to initiate a call to the server of the service provider based on the soft load balancing algorithm according to the address of the service provider.

In one embodiment, the inter-unit service discovery apparatus under the unitized deployment architecture further includes:

The standby invocation unit is used for invoking the servers of other service providers in the pre-stored local service provider address list by adopting the RPC long connection point-to-point mode when the invocation to the service provider fails.

In a specific embodiment, for a consumer that wants to invoke services in other units, during the startup process of the consumer, the cross-unit invocation mechanism will also query the provider address list to be invoked. From the provider address list, Based on the soft load balancing algorithm, select one provider to call, and if the call fails, select another provider to call. The service call adopts the RPC method of java, and uses the long connection for point-to-point communication. In this way, it can subscribe to the cross-unit service that it needs to call. At the same time, when the cross-unit calling mechanism receives a notification of provider information change pushed by the cross-unit service manager, it will also push the change data to the consumer based on the long connection. .

In this application, by deploying several units in all computer rooms of the whole station, all applications required by the system are deployed in any unit, and then the service and data are designed and transformed to conform to the characteristics of the unit. In the context of the unitized deployment architecture, Under normal circumstances, the service provider registers the services it provides with the registration center in this unit when it starts up, and the service consumer subscribes the services it needs to the registration center in this unit when it starts up. Therefore, under normal circumstances, the transaction is basically A closed loop can be realized in this unit. This application solves the problem that the transaction cannot be closed-loop within the unit to realize the transaction between two cross-unit services in a business scenario where a counterparty exists or some services cannot be unitized.

As will be appreciated by those skilled in the art, the embodiments of the present application may be provided as a method, a system, or a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block in the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce Means for implementing the functions specified in a flow or flow of a flowchart and/or a block or blocks of a block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions The apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

These computer program instructions can also be loaded on a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that The instructions provide steps for implementing the functions specified in the flow or blocks of the flowcharts and/or the block or blocks of the block diagrams.

In this application, specific examples are used to illustrate the principles and implementations of the application, and the descriptions of the above examples are only used to help understand the method and the core idea of the application; The idea of the application will have changes in the specific implementation and application scope. To sum up, the content of this specification should not be construed as a limitation on the application.

The embodiments of the present application also provide specific implementations of an electronic device capable of implementing all the steps in the methods in the foregoing embodiments. Referring to FIG. 9 , the electronic device specifically includes the following contents:

a processor (processor) 901, a memory 902, a communications interface (Communications Interface) 903, a bus 904 and a non-volatile memory 905;

The processor 901, the memory 902, and the communication interface 903 communicate with each other through the bus 904;

The processor 901 is configured to call the computer program in the memory 902 and the non-volatile memory 905, and when the processor executes the computer program, all steps in the methods in the foregoing embodiments are implemented, for example, the The processor implements the following steps when executing the computer program:

S501: Monitor the start action of the cross-unit service, and register the service provider information of the cross-unit service.

S502: Send the registered service provider information to the cross-unit invocation server, so that the cross-unit invocation server sends the service provider information to the service consumer.

as well as

S601: Receive the service provider registration or modification information sent by the cross-unit service manager and forward it to the service consumer.

S602: Parse the service invocation request initiated by the service consumer to obtain the address of the service provider.

S603: According to the address of the service provider, initiate a call to the server of the service provider based on the soft load balancing algorithm.

The embodiments of the present application also provide a computer-readable storage medium capable of implementing all the steps in the methods in the foregoing embodiments, where a computer program is stored on the computer-readable storage medium, and the computer program implements the foregoing when executed by a processor All steps of the method in the embodiment, for example, the processor implements the following steps when executing the computer program:

S501: Monitor the start action of the cross-unit service, and register the service provider information of the cross-unit service.

S502: Send the registered service provider information to the cross-unit invocation server, so that the cross-unit invocation server sends the service provider information to the service consumer.

as well as

S601: Receive the service provider registration or modification information sent by the cross-unit service manager and forward it to the service consumer.

S602: Parse the service invocation request initiated by the service consumer to obtain the address of the service provider.

S603: According to the address of the service provider, initiate a call to the server of the service provider based on the soft load balancing algorithm.

Each embodiment in this specification is described in a progressive manner, and the same and similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the hardware+program embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for related parts, please refer to the partial description of the method embodiment. Although the embodiments of the present specification provide method operation steps as described in the embodiments or flow charts, more or less operation steps may be included based on conventional or non-creative means. The sequence of steps enumerated in the embodiments is only one of the execution sequences of many steps, and does not represent the only execution sequence. When an actual device or terminal product is executed, it can be executed sequentially or in parallel according to the methods shown in the embodiments or the drawings (eg, a parallel processor or multi-threaded processing environment, or even a distributed data processing environment). The terms "comprising", "comprising" or any other variation thereof are intended to encompass a non-exclusive inclusion such that a process, method, product or device comprising a list of elements includes not only those elements, but also others not expressly listed elements, or also include elements inherent to such a process, method, product or device. Without further limitation, it does not preclude the presence of additional identical or equivalent elements in a process, method, product or apparatus comprising the stated elements. For the convenience of description, when describing the above device, the functions are divided into various modules and described respectively. Of course, when implementing the embodiments of this specification, the functions of each module may be implemented in the same one or more software and/or hardware, and the modules implementing the same function may be implemented by a combination of multiple sub-modules or sub-units. The apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms. The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block in the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce Means for implementing the functions specified in a flow or flow of a flowchart and/or a block or blocks of a block diagram. As will be appreciated by one skilled in the art, the embodiments of the present specification may be provided as a method, a system or a computer program product. Accordingly, embodiments of this specification may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein. Each embodiment in this specification is described in a progressive manner, and the same and similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, as for the system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and for related parts, please refer to the partial descriptions of the method embodiments. In the description of this specification, description with reference to the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples", etc., mean specific features described in connection with the embodiment or example , structures, materials, or features are included in at least one example or example of embodiments of this specification. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, those skilled in the art may combine and combine the different embodiments or examples described in this specification, as well as the features of the different embodiments or examples, without conflicting each other. The above descriptions are merely examples of the embodiments of the present specification, and are not intended to limit the embodiments of the present specification. For those skilled in the art, various modifications and variations can be made to the embodiments of the present specification. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the embodiments of the present specification shall be included within the scope of the claims of the embodiments of the present specification.

Claims (11)

1. A method for discovering inter-unit services under a unitized deployment architecture, comprising:

monitoring the starting action of the cross-unit service, and registering the service provider information of the cross-unit service;

and sending the registered service provider information to a cross-cell calling server so that the cross-cell calling server sends the service provider information to a service consumer.

2. The method of discovering inter-unit services under a unitized deployment architecture of claim 1, further comprising:

and monitoring the information change action of the service provider, updating the service provider information of the cross-unit service, and pushing the updated service provider information to the cross-unit calling server.

3. A method for discovering inter-unit services under a unitized deployment architecture, comprising:

receiving service provider registration or change information sent by a cross-unit service manager and forwarding the service provider registration or change information to a service consumer;

analyzing a service calling request initiated by a service consumer to obtain a service provider address;

and initiating a call to a server of the service provider based on a soft load balancing algorithm according to the address of the service provider.

4. The method of discovering inter-unit services under the unitized deployment architecture of claim 3, further comprising:

and when the calling to the service provider fails, calling the servers of other service providers in the pre-stored local service provider address list in a point-to-point mode by adopting RPC long connection.

5. An inter-unit service discovery system under a unitized deployment architecture, comprising: the system comprises a plurality of monitoring units, a cross-unit service manager and a cross-unit calling server, wherein the monitoring units, the cross-unit service manager and the cross-unit calling server are respectively deployed at a service provider; the monitoring unit is in communication connection with the cross-unit service manager, and the cross-unit service manager is in communication connection with the cross-unit call server;

the monitoring unit is used for monitoring the action of the service provider;

the cross-unit service manager is used for managing and registering cross-unit services;

the cross-unit calling server is used for realizing the subscription and calling of cross-unit transaction.

6. An inter-unit service discovery apparatus under a unitized deployment architecture, comprising:

the monitoring unit is used for monitoring the starting action of the cross-unit service and registering the service provider information of the cross-unit service;

and the information sending unit is used for sending the registered service provider information to the cross-unit calling server so as to enable the cross-unit calling server to send the service provider information to the service consumer.

7. The device for discovering inter-unit services under the unitized deployment architecture of claim 6, further comprising:

and the information changing unit is used for monitoring the information changing action of the service provider, updating the service provider information of the cross-unit service and then pushing the updated service provider information to the cross-unit calling server.

8. An inter-unit service discovery apparatus under a unitized deployment architecture, comprising:

a receiving unit for receiving the service provider registration or change information sent by the cross-unit service manager and forwarding to the service consumer;

the analysis unit is used for analyzing a service calling request initiated by a service consumer to obtain an address of a service provider;

and the calling unit is used for initiating calling to the server of the service provider based on a soft load balancing algorithm according to the address of the service provider.

9. The device for discovering inter-unit services under the unitized deployment architecture of claim 8, further comprising:

and the standby calling unit is used for calling the servers of other service providers in the pre-stored address list of the local service provider in a point-to-point mode by RPC long connection when the calling to the service provider fails.

10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the program implements the steps of the inter-unit service discovery method under the unitized deployment architecture of any one of claims 1 to 4.

11. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the inter-unit service discovery method under a unitized deployment architecture according to any one of claims 1 to 4.

Images