CN113254227A - Method and system for remote method call across data centers - Google Patents

Method and system for remote method call across data centers Download PDF

Info

Publication number
CN113254227A
CN113254227A CN202010086877.2A CN202010086877A CN113254227A CN 113254227 A CN113254227 A CN 113254227A CN 202010086877 A CN202010086877 A CN 202010086877A CN 113254227 A CN113254227 A CN 113254227A
Authority
CN
China
Prior art keywords
data center
registration information
data
center
proxy server
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.)
Granted
Application number
CN202010086877.2A
Other languages
Chinese (zh)
Other versions
CN113254227B (en
Inventor
张华杰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Chihiro Location Network Co Ltd
Original Assignee
Chihiro Location Network Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Chihiro Location Network Co Ltd filed Critical Chihiro Location Network Co Ltd
Priority to CN202010086877.2A priority Critical patent/CN113254227B/en
Publication of CN113254227A publication Critical patent/CN113254227A/en
Application granted granted Critical
Publication of CN113254227B publication Critical patent/CN113254227B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/547Remote procedure calls [RPC]; Web services
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00Indexing scheme relating to G06F9/00
    • G06F2209/54Indexing scheme relating to G06F9/54
    • G06F2209/544Remote

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The application discloses a method and a system for remote method calling across data centers. The method comprises the following steps: each data center has a corresponding identifier, and the identifier of the data center is registered in the registration information of the registration center of the data center; deploying proxy servers in each data center, wherein each proxy server subscribes all registration information of the data center and synchronizes the registration information to the proxy servers of other data centers; after receiving the registration information of other synchronized data centers, each proxy server converts the intranet address in the registration information into the intranet address of the data center and reports the registration information to the registration center of the data center; the service caller of one data center obtains the converted internal network address of the service provider of the other data center from the registration center of the data center, and the remote method call is carried out on the service provider through the proxy server of the other data center.

Description

Method and system for remote method call across data centers
Technical Field
The present disclosure relates generally to the field of computer technology, and more particularly, to a method and system for remote method invocation across data centers.
Background
RPC (Remote Procedure Call) calls are common components for inter-service calls in a service-oriented architecture scenario, and developers develop many RPC frameworks for the convenience of RPC callers and servers. The well-known RPC frameworks are Google's gPC, Facebook's Thrift, and Ali's Dubbo et al. Although the frames vary in their specific implementation, the principles of operation are substantially identical. The flow of a complete RPC call is as follows: the service caller serializes the local method call and the input parameters into a data packet which can be transmitted by the network, then sends the data packet to the service provider through the network, the service provider receives the data and then deserializes the data into a memory model (input parameters) which can be understood by a program and realizes a call logic, and finally sends a call result to the caller through the network in the same way. A well-designed RPC framework aims to simplify the development work of service providers and callers, hide all details such as parameter conversion and network transmission, and enable developers to develop and call remote methods like local methods.
Disclosure of Invention
The specification provides a cross-data-center remote method calling method, so that a developer can develop and call RPC services deployed by other data centers like the RPC services developed and called by the data center.
The application discloses a remote method calling method across data centers, which comprises the following steps:
each data center has a corresponding identifier, and the identifier of the data center is registered in the registration information of the registration center of the data center;
deploying proxy servers in each data center, wherein each proxy server subscribes all registration information of the data center and synchronizes the registration information to the proxy servers of other data centers;
after receiving the registration information of other synchronized data centers, each proxy server converts the intranet address in the registration information into the intranet address of the data center and reports the registration information to the registration center of the data center;
the service caller of one data center obtains the converted internal network address of the service provider of the other data center from the registration center of the data center, and the remote method call is carried out on the service provider through the proxy server of the other data center.
In a preferred embodiment, each data center further deploys the registration center and a plurality of service providers, and registers the plurality of service providers with the registration center, where the registration includes the following registration information: service name, service group and intranet address in the data center.
In a preferred example, the proxy servers of each data center are connected through a dedicated network line, and the proxy server of each data center includes a token for verifying identity.
In a preferred embodiment, the proxy servers of each data center are connected with each other through a secure socket layer.
In a preferred embodiment, the proxy server of each data center includes a token for verifying identity.
In a preferred example, more than one proxy server is deployed in each data center, and all the proxy servers of each data center are connected with all the proxy servers of other data centers in a pairwise manner.
In a preferred embodiment, the step of each proxy server subscribing to all registration information of the data center and synchronizing the registration information to proxy servers of other data centers further includes: and adding a field which can be called by other data centers of each service provider in the registration information, and when the field shows that the service provider cannot be called by other data centers, not synchronizing the registration information of the service provider to the proxy servers of other data centers.
The application also discloses a remote method calling system across the data center, which comprises the following steps:
a plurality of data centers having respective identities;
a registry deployed in each of the data centers, the registry having the identity of the local data center registered therein;
the proxy servers are deployed in each data center, each proxy server subscribes all registration information of the data center and synchronizes the registration information to the proxy servers of other data centers, and after each proxy server receives the synchronized registration information of other data centers, each proxy server converts the intranet address in the registration information into the intranet address of the data center and reports the registration information to the registration center of the data center;
the service caller of one data center obtains the converted internal network address of the service provider of the other data center from the registration center of the data center, and the remote method call is carried out on the service provider through the proxy server of the other data center.
In a preferred embodiment, each data center further deploys the registration center and a plurality of service providers, and the plurality of service providers register with the registration center, wherein the registration includes the following registration information: service name, service group and intranet address in the data center.
In a preferred example, the proxy servers of each data center are connected through a dedicated network line, and the proxy server of each data center includes a token for verifying identity.
In a preferred embodiment, the proxy servers of each data center are connected with each other through a secure socket layer.
In a preferred embodiment, the proxy server of each data center includes a token for verifying identity.
In a preferred example, more than one proxy server is deployed in each data center, and all the proxy servers of each data center are connected with all the proxy servers of other data centers in a pairwise manner.
In a preferred embodiment, each of the proxy servers subscribes to all registration information of the data center and synchronizes the registration information to the proxy servers of other data centers further includes: the registration information comprises a field which indicates whether each service provider can be called by other data centers, and when the field indicates that the service provider cannot be called by other data centers, the registration information of the service provider is not synchronized to the proxy servers of other data centers.
The application also discloses a remote method calling system across the data center, which comprises the following steps:
a memory for storing computer executable instructions; and
a processor, coupled with the memory, for implementing the steps in the method as described above when executing the computer-executable instructions.
The present application also discloses a computer-readable storage medium having stored thereon computer-executable instructions which, when executed by a processor, implement the steps in the method as described above.
Compared with the prior art, the method has the following beneficial effects:
the proxy server is deployed in each data center and serves as a boundary gateway of RPC calls, so that implementation details of cross-data center network transmission during cross-data center RPC calls are shielded, and developers can use the cross-data center RPC calls conveniently.
A large number of technical features are described in the specification, and are distributed in various technical solutions, so that the specification is too long if all possible combinations of the technical features (namely, the technical solutions) in the application are listed. In order to avoid this problem, the respective technical features disclosed in the above summary of the invention of the present specification, the respective technical features disclosed in the following embodiments and examples, and the respective technical features disclosed in the drawings may be freely combined with each other to constitute various new technical solutions (which should be regarded as having been described in the present specification) unless such a combination of the technical features is technically impossible. For example, in one example, the feature a + B + C is disclosed, in another example, the feature a + B + D + E is disclosed, and the features C and D are equivalent technical means for the same purpose, and technically only one feature is used, but not simultaneously employed, and the feature E can be technically combined with the feature C, then the solution of a + B + C + D should not be considered as being described because the technology is not feasible, and the solution of a + B + C + E should be considered as being described.
Drawings
Non-limiting and non-exhaustive embodiments of the present application are described with reference to the following figures, wherein like reference numerals refer to like parts throughout the various views unless otherwise specified.
FIG. 1 is a flow diagram of a method for remote method invocation across data centers in accordance with an embodiment of the present description.
FIG. 2 is a schematic diagram of a remote method invocation system across data centers in accordance with an embodiment of the present description.
Detailed Description
In the following description, numerous technical details are set forth in order to provide a better understanding of the present application. However, it will be understood by those skilled in the art that the technical solutions claimed in the present application may be implemented without these technical details and with various changes and modifications based on the following embodiments.
In the prior art, in order to hide implementation details such as parameter conversion and network transmission, the RPC framework mainly solves the problem of service registration and discovery. Specifically, a service provider issues a service, how the callee perceives and obtains the service address of the service provider. In general, the RPC framework requires, in addition to the two roles of service provider and caller themselves, an intermediary that stores and manages registration information for all service providers, the intermediary being a so-called service registry. The service provider sends the registration information to the service registry, which records it, a process known as service registration. When a service caller needs to subscribe to a service, the service caller registers with a service registry, which synchronizes the service caller's subscribed service registration information in real time with the service caller, a process called service discovery. After the caller obtains the network address(s) of the service provider, a network connection is usually established with the service provider to ensure real-time data transmission efficiency during RPC call. In the application, the proxy server is deployed in each data center and serves as a boundary gateway for RPC calling, so that implementation details of cross-data center network transmission during cross-data center RPC calling are shielded, and developers can conveniently use the RPC calling of the data center when carrying out cross-data center calling.
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
A first embodiment of the present specification relates to a method for remote method invocation across data centers, a flowchart of which is shown with reference to fig. 1, the method comprising:
in step 101, each data center has a corresponding identifier, and the identifier of the data center is registered in the registration information of the registration center of the data center. In a preferred embodiment, each data center further deploys the registration center and a plurality of service providers, and registers the plurality of service providers with the registration center, where the registration includes the following registration information: service name, service packet, and intranet address (or local address) in the data center.
The Data Center in this embodiment is an Internet Data Center (IDC for short), and is a service platform that has perfect devices (including a high-speed Internet access bandwidth, a high-performance local area network, a safe and reliable computer room environment, and the like), specialized management, and perfect applications. On the basis of the platform, the IDC service provider provides Internet basic platform services (server hosting, virtual host, mail caching, virtual mail and the like) and various value-added services (site renting services, domain name system services, load balancing systems, database systems, data backup services and the like) for the client.
In step 102, a proxy server is deployed in each data center, and each proxy server subscribes all registration information of the data center and synchronizes the registration information to proxy servers of other data centers.
In the present application. The proxy server assumes bidirectional proxy roles: 1) implementing a provider agent of a service by synchronizing registration information between multiple data centers; 2) the caller proxy of the service is implemented by cross-datacenter invocation between proxy servers.
In a preferred embodiment, the proxy servers of each data center are connected through a Secure Socket Layer (SSL) to secure network transmission.
In a preferred example, the proxy servers of each data center are connected through a dedicated network line. In a preferred example, the proxy server of each data center includes a token (token) for verifying the identity, and when establishing the connection, the proxy servers exchange the tokens with each other to confirm the identity of the other proxy server.
In step 103, after receiving the registration information of the synchronized other data centers, each of the proxy servers converts the intranet address in the registration information into the intranet address of the data center and reports the registration information to the registration center of the data center.
In step 104, the service caller of one of the data centers obtains the converted intranet address of the service provider of the other data center from the registration center of the data center, and performs remote method call to the service provider through the proxy server of the other data center.
In another preferred example, more than one proxy server is deployed in each data center, and all the proxy servers of each data center are connected with all the proxy servers of other data centers in a pairwise manner. For example, each data center is provided with a plurality of proxy servers, for example, two or three proxy servers, and two proxy servers of each data center are connected in pairs, wherein any one proxy server is not a single point, and after the proxy server is hung up, other proxy servers can work, so that the availability is improved.
In another preferred example, the step of each proxy server subscribing to all registration information of the data center and synchronizing the registration information to proxy servers of other data centers further includes: and adding a field which can be called by other data centers of each service provider in the registration information, and when the field shows that the service provider cannot be called by other data centers, not synchronizing the registration information of the service provider to the proxy servers of other data centers, so that the transmission bandwidth among the proxies of the plurality of data centers is reduced.
In order to better understand the technical solutions of the present description, the following description is given with reference to a specific example, in which the listed details are mainly for the sake of understanding, and are not intended to limit the scope of the present application.
Referring to fig. 2, in the embodiment, the data center A, B, C is included, the data center A, B, C includes registration centers, and the proxy server a of the data center a subscribes to the registration information of the service providers S1 and S2 and synchronizes to the proxy server B of the data center B and the proxy server C of the data center C. After receiving the registration information synchronized by the proxy servers of other data centers, the proxy server A converts the local address of the service provider in the registration information into the local address of the proxy server, and then reports the registration information to the local registration center. For example, proxy B receives the registration information (DC1, S1- > local Address 1, local Address 2; DC1, S2- > local Address 3) of service providers S1 and S2, modifies the local Address of the service to the local Address of the proxy: local address 5(DC1, S1- > local address 5; DC1, S2- > local address 5), and then reported to the local registry. When a service caller (caller S1) in data center B looks up service provider S1, it finds the address of proxy server B (local address 5) from the registry, and then the service caller initiates a remote method call to proxy server B. The proxy server B knows that the service provider S1 was published in data center a (DC1), and therefore sends the invocation data to the proxy server a of data center a over the network. Proxy server a subscribes to the registration information of service provider S1, so proxy server a gets two local addresses of service provider S1: home address 1 and home address 2. Based on the routing of the call, proxy server a randomly picks a service instance, e.g., home address 2, and sends the call data to home address 2. After the service provider S1 completes the service call procedure, the return result is returned to the caller of the service provider S1 of the data center B, and the process of RPC call across the data center is completed locally.
A second embodiment of the present specification relates to a remote method invocation system across data centers, the system comprising:
a plurality of data centers having respective identities;
a registry deployed in each of the data centers, the registry having the identity of the local data center registered therein;
the proxy servers are deployed in each data center, each proxy server subscribes all registration information of the data center and synchronizes the registration information to the proxy servers of other data centers, and after each proxy server receives the synchronized registration information of other data centers, each proxy server converts the intranet address in the registration information into the intranet address of the data center and reports the registration information to the registration center of the data center;
the service caller of one data center obtains the converted internal network address of the service provider of the other data center from the registration center of the data center, and the remote method call is carried out on the service provider through the proxy server of the other data center.
In a preferred embodiment, each data center further deploys the registration center and a plurality of service providers, and the plurality of service providers register with the registration center, wherein the registration includes the following registration information: service name, service group and intranet address in the data center.
In a preferred example, the proxy servers of each data center are connected through a dedicated network line.
In a preferred embodiment, the proxy servers of each data center are connected with each other through a secure socket layer.
In a preferred embodiment, the proxy server of each data center includes a token for verifying identity.
In a preferred example, more than one proxy server is deployed in each data center, and all the proxy servers of each data center are connected with all the proxy servers of other data centers in a pairwise manner.
In a preferred embodiment, each of the proxy servers subscribes to all registration information of the data center and synchronizes the registration information to the proxy servers of other data centers further includes: the registration information comprises a field which indicates whether each service provider can be called by other data centers, and when the field indicates that the service provider cannot be called by other data centers, the registration information of the service provider is not synchronized to the proxy servers of other data centers.
The first embodiment is a system embodiment corresponding to the present embodiment, and the technical details in the first embodiment may be applied to the present embodiment, and the technical details in the present embodiment may also be applied to the first embodiment.
It should be noted that, as will be understood by those skilled in the art, the implementation functions of the modules shown in the embodiment of the cross-data center remote method invocation system can be understood by referring to the foregoing description of the cross-data center remote method invocation method. The functions of the modules shown in the embodiments of the remote method call system across data centers described above may be implemented by programs (executable instructions) running on a processor, and may also be implemented by specific logic circuits. The remote method invocation system across data centers in the embodiments of the present description may also be stored in a computer readable storage medium if it is implemented in the form of a software function module and sold or used as a stand-alone product. Based on such understanding, the technical solutions of the embodiments of the present specification may be essentially or partially implemented in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the methods described in the embodiments of the present specification. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read Only Memory (ROM), a magnetic disk, or an optical disk. Thus, embodiments of the present description are not limited to any specific combination of hardware and software.
Accordingly, the present specification embodiments also provide a computer-readable storage medium having stored therein computer-executable instructions that, when executed by a processor, implement the method embodiments of the present specification. Computer-readable storage media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable storage medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
In addition, the present specification embodiments also provide a system for remote method invocation across data centers, including a memory for storing computer-executable instructions, and a processor; the processor is configured to implement the steps of the method embodiments described above when executing the computer-executable instructions in the memory.
In one embodiment, the computer-executable instructions may be for:
each data center has a corresponding identifier, and the identifier of the data center is registered in the registration information of the registration center of the data center;
deploying proxy servers in each data center, wherein each proxy server subscribes all registration information of the data center and synchronizes the registration information to the proxy servers of other data centers;
after receiving the registration information of other synchronized data centers, each proxy server converts the intranet address in the registration information into the intranet address of the data center and reports the registration information to the registration center of the data center;
the service caller of one data center obtains the converted internal network address of the service provider of the other data center from the registration center of the data center, and the remote method call is carried out on the service provider through the proxy server of the other data center.
In one embodiment, the Processor may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), or the like. The aforementioned memory may be a read-only memory (ROM), a Random Access Memory (RAM), a Flash memory (Flash), a hard disk, or a solid state disk. The steps of the method disclosed in the embodiments of the present invention may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. In one embodiment, the system of surface monitoring systems further comprises a bus and a communication interface. The processor, memory and communication interface are all interconnected by a bus. The communication interface may be a wireless communication interface or a wired communication interface for enabling the processor to communicate with other systems.
It is noted that, in the present patent application, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, the use of the verb "comprise a" to define an element does not exclude the presence of another, same element in a process, method, article, or apparatus that comprises the element. In the present patent application, if it is mentioned that a certain action is executed according to a certain element, it means that the action is executed according to at least the element, and two cases are included: performing the action based only on the element, and performing the action based on the element and other elements. The expression of a plurality of, a plurality of and the like includes 2, 2 and more than 2, more than 2 and more than 2.
All documents mentioned in this specification are to be considered as being incorporated in their entirety into the disclosure of this specification so as to be subject to modification as necessary. It should be understood that the above description is only a preferred embodiment of the present disclosure, and is not intended to limit the scope of the present disclosure. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of the present disclosure should be included in the scope of protection of one or more embodiments of the present disclosure.
In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

Claims (16)

1. A method for remote method invocation across data centers, comprising:
each data center has a corresponding identifier, and the identifier of the data center is registered in the registration information of the registration center of the data center;
deploying proxy servers in each data center, wherein each proxy server subscribes all registration information of the data center and synchronizes the registration information to the proxy servers of other data centers;
after receiving the registration information of other synchronized data centers, each proxy server converts the intranet address in the registration information into the intranet address of the data center and reports the registration information to the registration center of the data center;
the service caller of one data center obtains the converted internal network address of the service provider of the other data center from the registration center of the data center, and the remote method call is carried out on the service provider through the proxy server of the other data center.
2. The method of claim 1, wherein each data center further deploys the registry and a plurality of service providers, and registers the plurality of service providers with the registry, the registration including registration information comprising: service name, service group and intranet address in the data center.
3. The method for remote method invocation across data centers according to claim 1, wherein the proxy server of each data center is connected through a dedicated network line, and the proxy server of each data center includes a token for verifying identity.
4. The method for remote method invocation across data centers according to claim 1, wherein the proxy servers of each data center are connected through a secure socket layer.
5. The cross-data center remote method invocation method according to claim 4, wherein the proxy server of each data center includes a token for verifying identity.
6. The method for remote method invocation across data centers according to claim 1, wherein more than one proxy server is deployed in each data center, all proxy servers of each data center are interconnected with all proxy servers of other data centers.
7. The method of remote method invocation across data centers according to claim 1, wherein the step of each of said proxy servers subscribing to all registration information of the data center and synchronizing said registration information to proxy servers of other data centers further comprises: and adding a field which can be called by other data centers of each service provider in the registration information, and when the field shows that the service provider cannot be called by other data centers, not synchronizing the registration information of the service provider to the proxy servers of other data centers.
8. A remote method invocation system across data centers, comprising:
a plurality of data centers having respective identities;
a registry deployed in each of the data centers, the registry having the identity of the local data center registered therein;
the proxy servers are deployed in each data center, each proxy server subscribes all registration information of the data center and synchronizes the registration information to the proxy servers of other data centers, and after each proxy server receives the synchronized registration information of other data centers, each proxy server converts the intranet address in the registration information into the intranet address of the data center and reports the registration information to the registration center of the data center;
the service caller of one data center obtains the converted internal network address of the service provider of the other data center from the registration center of the data center, and the remote method call is carried out on the service provider through the proxy server of the other data center.
9. The cross-datacenter remote method invocation system according to claim 8, wherein each datacenter further deploys the registry and a number of service providers, the number of service providers register with the registry, the registration including registration information: service name, service group and intranet address in the data center.
10. The cross-data center remote method invocation system according to claim 8, wherein the proxy server of each data center is connected through a dedicated network line, and the proxy server of each data center includes a token for verifying identity.
11. The cross-data center remote method invocation system according to claim 8, wherein the proxy servers of each data center are connected through a secure socket layer.
12. The cross-data center remote method invocation system according to claim 11, wherein the proxy server of each data center includes a token for verifying identity.
13. The system for remote method invocation across data centers according to claim 8, wherein more than one proxy server is deployed in each data center, all proxy servers of each data center being interconnected with all proxy servers of other data centers.
14. The cross-datacenter remote method invocation system according to claim 8, wherein each of the proxy servers subscribes to all registration information for the datacenter and synchronizes the registration information to proxy servers of other datacenters further comprises: the registration information comprises a field which indicates whether each service provider can be called by other data centers, and when the field indicates that the service provider cannot be called by other data centers, the registration information of the service provider is not synchronized to the proxy servers of other data centers.
15. A remote method invocation system across data centers, comprising:
a memory for storing computer executable instructions; and
a processor, coupled with the memory, for implementing the steps in the method of any of claims 1-7 when executing the computer-executable instructions.
16. A computer-readable storage medium having stored thereon computer-executable instructions which, when executed by a processor, implement the steps of the method of any one of claims 1 to 7.
CN202010086877.2A 2020-02-11 2020-02-11 Method and system for remote method call across data centers Active CN113254227B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010086877.2A CN113254227B (en) 2020-02-11 2020-02-11 Method and system for remote method call across data centers

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010086877.2A CN113254227B (en) 2020-02-11 2020-02-11 Method and system for remote method call across data centers

Publications (2)

Publication Number Publication Date
CN113254227A true CN113254227A (en) 2021-08-13
CN113254227B CN113254227B (en) 2022-07-26

Family

ID=77219567

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010086877.2A Active CN113254227B (en) 2020-02-11 2020-02-11 Method and system for remote method call across data centers

Country Status (1)

Country Link
CN (1) CN113254227B (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115022325A (en) * 2022-06-07 2022-09-06 深圳市和讯华谷信息技术有限公司 Kafka inter-cluster data transmission method and related equipment
WO2023083038A1 (en) * 2021-11-15 2023-05-19 百果园技术(新加坡)有限公司 Multi-registration center data processing method and apparatus, device, and storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106375493A (en) * 2016-10-10 2017-02-01 腾讯科技(深圳)有限公司 Cross-network communication method and proxy servers
CN107635022A (en) * 2016-07-18 2018-01-26 华为软件技术有限公司 Across intranet and extranet service access methods and device
CN109618005A (en) * 2019-01-18 2019-04-12 华为终端有限公司 Method for calling server and proxy server

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107635022A (en) * 2016-07-18 2018-01-26 华为软件技术有限公司 Across intranet and extranet service access methods and device
CN106375493A (en) * 2016-10-10 2017-02-01 腾讯科技(深圳)有限公司 Cross-network communication method and proxy servers
CN109618005A (en) * 2019-01-18 2019-04-12 华为终端有限公司 Method for calling server and proxy server

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023083038A1 (en) * 2021-11-15 2023-05-19 百果园技术(新加坡)有限公司 Multi-registration center data processing method and apparatus, device, and storage medium
CN115022325A (en) * 2022-06-07 2022-09-06 深圳市和讯华谷信息技术有限公司 Kafka inter-cluster data transmission method and related equipment

Also Published As

Publication number Publication date
CN113254227B (en) 2022-07-26

Similar Documents

Publication Publication Date Title
CN106663033B (en) System and method for supporting a wraparound domain and proxy model and updating service information for cross-domain messaging in a transactional middleware machine environment
CN111290865A (en) Service calling method and device, electronic equipment and storage medium
US11716264B2 (en) In situ triggered function as a service within a service mesh
US10116642B2 (en) Identity management over multiple identity providers
CN108512821B (en) Data transmission method, device and system, network gate and transaction data storage method
JP2018536935A (en) Access request conversion method and apparatus
CN114025021B (en) Communication method, system, medium and electronic equipment crossing Kubernetes cluster
CN111124589B (en) Service discovery system, method, device and equipment
CN113254227B (en) Method and system for remote method call across data centers
CN113612686A (en) Traffic scheduling method and device and electronic equipment
CN113746928A (en) Cross-cloud service calling method, device and system
CN113938520A (en) Service registration method, device and storage medium
CN114040032A (en) Protocol conversion method, system, storage medium and electronic equipment
US10785056B1 (en) Sharing a subnet of a logically isolated network between client accounts of a provider network
CN112751935B (en) Request processing method and device, electronic equipment and storage medium
CN115065686B (en) Configuration method, device and system of distributed load balancing system
CN110022332B (en) Hypertext transfer security protocol proxy method, device, equipment and medium
CN114615285B (en) Physical machine deployment method and device, electronic equipment and storage medium
Wei et al. An agent-based services framework with adaptive monitoring in cloud environments
CN112165529A (en) Method, device, equipment and medium for low-cost cross-network data exchange
CN116389252B (en) Method, device, system, electronic equipment and storage medium for updating container network
US11936748B1 (en) Continuous scanning engine with automatic protocol detection
CN113010337B (en) Fault detection method, master control node, working node and distributed system
CN117879955A (en) Micro-service communication method, micro-service communication device, computer equipment and storage medium
CN116582511A (en) ICMP message processing method under distributed NAT gateway

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