Cross-domain service registration method and system
By deploying designated components in the cloud computing platform and using the central service platform to realize cross-cluster communication and service automatic registration, the problems of low cross-cluster communication security and non-interconnection of service data are solved, the interoperability process of service data is simplified, and the service is improved The ability to provide external data.
Patent Information
- Application Number
- CN202410123568.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-01-30
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2044-01-30
AI Technical Summary
In the prior art, cross-cluster communication is not very secure, and the complex cross-domain service registration process leads to incommunication of service data, which affects the ability of service data to provide externally.
By deploying designated components in the first service platform, the center service platform and the second service platform, the center service platform is used to establish communication between the first service platform and the second service platform, and automatic acquisition and registration of service data is realized, and multiple uses The central architecture automatically discovers and registers services on off-site platforms, avoiding the manual cross-domain synchronization process.
It realizes the security improvement of cross-cluster communication and automatic service discovery, simplifies the interoperability process of service data, reduces resource waste, and improves the ability to provide service data to the outside world.
Smart Images

Figure CN117651045B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of cloud computing technology, and in particular to a cross-domain service registration method and system. Background Art
[0002] A cluster is a group of independent computers connected by a high-speed network. They form a group and are managed in a single system mode. In the early stage of cloud platform construction, a single cluster can basically meet the business needs of enterprises or governments. However, with the increasing demand for cloud computing, problems such as the limited carrying capacity and disaster recovery capacity of a single cluster have become increasingly prominent. A single cluster can no longer meet the current needs. Therefore, a multi-center and multi-cluster solution has emerged. Multi-center refers to multiple public affairs handling entities in multiple different environments or systems.
[0003] The multi-center service automatic discovery technology, which is based on a multi-center and multi-cluster solution, provides a new problem-solving approach for the currently popular service registration mechanism.
[0004] In related technologies, the demand for cross-cluster communication of services is mainly solved by the following two technical solutions: First, based on star network technology, different clusters (similar to the concept of sub-nodes in network topology) need to first expose their respective business services to the central cluster (similar to the concept of central nodes in network topology). Each cluster exposes and pushes business services to the central cluster, and then the central cluster forwards and routes data to obtain communication with other cluster services. Second, based on the mesh network topology, cross-cluster communication is achieved for clusters that need to communicate by opening firewalls and pulling one-to-one dedicated communication lines (interconnecting all nodes in the network topology).
[0005] However, the cross-cluster communication security of the above two services is not high; the business service data exposed on the central cluster can theoretically be accessed by all applications accessing the central cluster, which invisibly increases the risk of data leakage; there is a lack of unified management and control, and services with similar or identical functions may exist in multiple systems. Such duplication of construction greatly wastes existing resources.
[0006] In addition, in the actual application scenario, the service data between multiple centers is not interoperable due to complex cross-domain service registration. If you want to interact with service data, you need to apply for the service first, obtain relevant interface data after approval, and then consider cross-domain issues (different centers have different network segments, and data in different network segments are not interoperable, which needs to be connected through technology). After dealing with cross-domain issues, the obtained services are re-registered on the new platform. This process is complicated and cumbersome, and seriously affects the basic demand for the ability to provide service data to the outside world. Summary of the invention
[0007] In order to solve the above technical problems or at least partially solve the above technical problems, an embodiment of the present disclosure provides a cross-domain service registration method and system.
[0008] In a first aspect, an embodiment of the present disclosure provides a cross-domain service registration method, the method comprising:
[0009] Deploy designated components in the first service platform, the central service platform, and the second service platform respectively, and establish communication between the first service platform and the second service platform through the central service platform, wherein both the first service platform and the second service platform are connected to the central service platform, both the first service platform and the second service platform are data sharing platforms, and the networks between the first service platform and the second service platform are different;
[0010] The first service platform sends a service data acquisition request to the central service platform for the second service platform;
[0011] The central service platform pulls the target service data from the second service platform according to the service data acquisition request and sends it to the first service platform;
[0012] The first service platform registers the target service locally according to the target service data.
[0013] In a possible implementation manner, the central service platform pulls the target service data from the second service platform according to the service data acquisition request and sends the target service data to the first service platform, including:
[0014] The central service platform receives and parses the service data acquisition request, obtains each type of target service data required by the request and each second service platform corresponding to each type of target service data, and sends a corresponding target service data acquisition request to each second service platform;
[0015] Each second service platform sends corresponding target service data to the central service platform according to the target service data acquisition request;
[0016] The central service platform receives the target service data and sends it to the first service platform.
[0017] In a possible implementation manner, the target service data includes a target service and a service registration parameter, and the first service platform registers the target service locally according to the target service data, including:
[0018] The first service platform writes the target service into a local database to store the target service;
[0019] Register the stored target service locally according to the service registration parameters.
[0020] In a possible implementation manner, the number of target service data exceeds one, and the first service platform writes the target service into the local database, including:
[0021] Sort the target service data according to the timestamp when the first service platform receives the target service data, and determine the order of the target service data;
[0022] Write the target services into the local database in sequence according to the order of the target service data.
[0023] In a possible implementation manner, storing the target service includes:
[0024] Monitor and collect the storage status of the first service platform in real time, and use bottleneck identification technology to collect and obtain migration bottleneck status data information, and in terms of cache settings, detect cache adjustment status data information in real time to establish a software performance data set;
[0025] The migration bottleneck status data information and cache adjustment status data information are transferred to the software performance data set, and the data is cleaned and feature extracted, and the processed data information is standardized according to the dimensionless processing technology;
[0026] Cloud computing technology is used to comprehensively analyze and learn the migration bottleneck status data information after data cleaning to obtain the bottleneck factor, and the migration status coefficient is generated by combining the number of interruptions during data migration;
[0027] Obtain block size and cache hit rate through cache adjustment status data information after feature extraction, and associate the block size with the cache hit rate to obtain a cache adjustment coefficient, conduct a comprehensive analysis on the cache adjustment coefficient and the migration state coefficient, and generate a software storage performance prediction model by combining with a neural network model and training, and obtain a performance status evaluation index after dimensionless processing;
[0028] An evaluation threshold is set in advance, and the evaluation threshold is compared and analyzed with the performance situation evaluation index to obtain a prediction result, and a corresponding level improvement strategy is obtained based on the prediction result.
[0029] In a possible implementation, the performance status evaluation index is obtained by the following formula:
[0030] ;
[0031] TSzs is the performance status evaluation index, Ttlz is the throughput, F1, F2 and F3 are the proportional coefficients of cache control coefficient Tkxs, migration state coefficient Pyxs and throughput Ttlz, respectively, where 0.10≤F 1≤0.22, 0.15≤F 2 ≤0.36, 0.20≤F 3 ≤0.42, and 0.55≤F 1 +F 2 +F 3 ≤1.0, C is represented by the first correction constant.
[0032] In a possible implementation manner, the migration state coefficient is obtained by the following formula:
[0033] ;
[0034] Among them, Pyxs represents the migration status coefficient, Ysjz represents the amount of migrated data, and Both are expressed as proportionality coefficients, M 1 Expressed as the third correction constant.
[0035] In a possible implementation manner, the cache control coefficient Tkxs is obtained by the following formula:
[0036] ;
[0037] Among them, RLz represents the cache capacity, Kds represents the block size, Hcmz represents the cache hit rate, and a 1 and a 2 Both are expressed as proportionality coefficients, M 2 Expressed as the fourth correction constant.
[0038] In a possible implementation, respectively deploying designated components in the first service platform, the central service platform, and the second service platform, and establishing communication between the first service platform and the second service platform through the central service platform includes:
[0039] Deploy a preset server component in the central service platform, deploy an access component in the first service platform, and deploy an agent component in the second service platform, wherein the deployment file of the agent component includes the service address and business ID of the server component connected to the agent component, and the deployment file of the access component includes the service address and business ID of the server component connected to the access component, and the mapped virtual agent business service address corresponding to each business ID;
[0040] After the server component is deployed, the TCP service address of the server component is exposed externally, where the server component is used to provide a cross-domain network connection channel;
[0041] After the deployment of the proxy component is completed, the business metadata information bound to the proxy component is registered in the metadata database of the server component through the server component service address in the deployment file of the proxy component, wherein the business metadata information includes the business ID;
[0042] The server component receives the access request from the access component, and based on the metadata database, builds a channel between the access component and the proxy component corresponding to the same business ID through the server component deployed in the central service platform to realize data transmission between different network platforms.
[0043] In a second aspect, an embodiment of the present disclosure provides a cross-domain service registration system, the system comprising at least one first service platform, a central service platform and at least one second service platform, wherein:
[0044] In the system, designated components are deployed in the first service platform, the central service platform, and the second service platform respectively, and communication between the first service platform and the second service platform is established through the central service platform, wherein both the first service platform and the second service platform are connected to the central service platform, and the networks between the first service platform and the second service platform are different;
[0045] The first service platform is used to send a service data acquisition request to the central service platform for the second service platform; and is used to register the target service locally according to the target service data;
[0046] The central service platform is used to pull service data from the second service platform according to the service data acquisition request and send it to the first service platform.
[0047] In a third aspect, an embodiment of the present disclosure provides an electronic device, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus;
[0048] Memory, used to store computer programs;
[0049] The processor is used to implement the above-mentioned cross-domain service registration method when executing the program stored in the memory.
[0050] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium having a computer program stored thereon, characterized in that the computer program implements the above-mentioned cross-domain service registration method when executed by a processor.
[0051] The above technical solution provided by the embodiment of the present disclosure has at least some or all of the following advantages compared with the prior art:
[0052] The cross-domain service registration method described in the embodiment of the present disclosure deploys designated components in the first service platform, the central service platform, and the second service platform respectively, and establishes communication between the first service platform and the second service platform through the central service platform, wherein the first service platform and the second service platform are both connected to the central service platform, the first service platform and the second service platform are both data sharing platforms, and the networks between the first service platform and the second service platform are different; the first service platform sends a service data acquisition request for the second service platform to the central service platform; the central service platform pulls the target service data from the second service platform according to the service data acquisition request, and sends it to the first service platform; the first service platform registers the target service locally according to the target service data, and based on the multi-center architecture, enables remote platforms to complete automatic service discovery and registration through cross-cluster communication, without the need to synchronize service data through manual cross-domain methods. BRIEF DESCRIPTION OF THE DRAWINGS
[0053] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.
[0054] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or related technical descriptions are briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0055] Figure 1 The following schematically shows a flow chart of a cross-domain service registration method according to an embodiment of the present disclosure;
[0056] Figure 2 The structure block diagram of the cross-domain service registration system according to the embodiment of the present disclosure is schematically shown;
[0057] Figure 3 The working principle diagram of the cross-domain service registration system according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION
[0058] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present disclosure.
[0059] See also Figure 1, an embodiment of the present disclosure provides a cross-domain service registration method, the method comprising:
[0060] S1, deploy designated components in the first service platform, the central service platform and the second service platform respectively, and establish communication between the first service platform and the second service platform through the central service platform, wherein the first service platform and the second service platform are both connected to the central service platform, the first service platform and the second service platform are both data sharing platforms, and the networks between the first service platform and the second service platform are different.
[0061] In this embodiment, the first service platform and the second service platform can be the same aPaaS platform, deployed to different network segments. The aPaaS platform can be a data open sharing platform for managing and controlling big data service operations, providing service registration and service release, and helping users to achieve integrated management and control of services. It is mainly used in the digital transformation of large enterprises or government agencies, and provides a new service discovery mechanism. The central service platform can be named aPaaS-MCN.
[0062] S2, the first service platform sends a request to the central service platform for obtaining service data of the second service platform.
[0063] S3, the central service platform pulls the target service data from the second service platform according to the service data acquisition request, and sends it to the first service platform.
[0064] S4, the first service platform registers the target service locally according to the target service data.
[0065] In this embodiment, the first service platform registers the target service locally according to the target service data, including:
[0066] The first service platform receives the target service data, stores the target service data locally, and registers the stored target service data locally.
[0067] The cross-domain service registration method disclosed in the present invention pulls the target service data from the second service platform to the first service platform, automatically registers the target service, and automatically identifies and obtains the registered services without manual registration.
[0068] In this embodiment, in step S3, the central service platform pulls the target service data from the second service platform according to the service data acquisition request and sends it to the first service platform, including:
[0069] The central service platform receives and parses the service data acquisition request, obtains each type of target service data required by the request and each second service platform corresponding to each type of target service data, and sends a corresponding target service data acquisition request to each second service platform;
[0070] Each second service platform sends corresponding target service data to the central service platform according to the target service data acquisition request;
[0071] The central service platform receives the target service data and sends it to the first service platform.
[0072] In this embodiment, in step S4, the target service data includes the target service and service registration parameters, and the first service platform registers the target service locally according to the target service data, including:
[0073] The first service platform writes the target service into a local database to store the target service;
[0074] Register the stored target service locally according to the service registration parameters.
[0075] In this embodiment, the number of target service data exceeds one, and the first service platform writes the target service into the local database, including:
[0076] Sort the target service data according to the timestamp when the first service platform receives the target service data, and determine the order of the target service data;
[0077] Write the target services into the local database in sequence according to the order of the target service data.
[0078] In this embodiment, storing the target service includes:
[0079] Monitor and collect the storage status of the first service platform in real time, and use bottleneck identification technology to collect and obtain migration bottleneck status data information, and in terms of cache settings, detect cache adjustment status data information in real time to establish a software performance data set;
[0080] The migration bottleneck status data information and cache adjustment status data information are transferred to the software performance data set, and the data is cleaned and feature extracted, and the processed data information is standardized according to the dimensionless processing technology;
[0081] Cloud computing technology is used to comprehensively analyze and learn the migration bottleneck status data information after data cleaning to obtain the bottleneck factor, and the migration status coefficient is generated by combining the number of interruptions during data migration;
[0082] Obtain block size and cache hit rate through cache adjustment status data information after feature extraction, and associate the block size with the cache hit rate to obtain a cache adjustment coefficient, conduct a comprehensive analysis on the cache adjustment coefficient and the migration state coefficient, and generate a software storage performance prediction model by combining with a neural network model and training, and obtain a performance status evaluation index after dimensionless processing;
[0083] An evaluation threshold is set in advance, and the evaluation threshold is compared and analyzed with the performance situation evaluation index to obtain a prediction result, and a corresponding level improvement strategy is obtained based on the prediction result.
[0084] In this embodiment, the performance status evaluation index is obtained by the following formula:
[0085] ;
[0086] TSzs is the performance status evaluation index, Ttlz is the throughput, F1, F2 and F3 are the proportional coefficients of cache control coefficient Tkxs, migration state coefficient Pyxs and throughput Ttlz, respectively, where 0.10≤F 1 ≤0.22, 0.15≤F 2 ≤0.36, 0.20≤F 3 ≤0.42, and 0.55≤F 1 +F 2 +F 3 ≤1.0, C is represented by the first correction constant.
[0087] In this embodiment, the migration state coefficient is obtained by the following formula:
[0088] ;
[0089] Among them, Pyxs represents the migration status coefficient, Ysjz represents the amount of migrated data, and Both are expressed as proportionality coefficients, M 1 Expressed as the third correction constant.
[0090] In this embodiment, the cache control coefficient Tkxs is obtained by the following formula:
[0091] ;
[0092] Among them, RLz represents the cache capacity, Kds represents the block size, Hcmz represents the cache hit rate, and a 1 and a 2 Both are expressed as proportionality coefficients, M 2 Expressed as the fourth correction constant.
[0093] In this embodiment, the bottleneck factor is obtained by the following formula:
[0094] ;
[0095] Among them, Pjyz represents the bottleneck factor, Wlkd represents the network bandwidth, Dssd represents the read and write speed, Bflj represents the number of concurrent connections, j, h and i represent the proportional coefficients of the network bandwidth Wlkd, the read and write speed Dssd and the concurrent connection number Bflj respectively, among which, 0.05≤j≤0.20, 0.15≤h≤0.30, 0.33≤i≤0.50, and 0.60≤j+h+i+≤1.0, and P represents the second correction constant.
[0096] In this embodiment, in step S1, the designated components are deployed in the first service platform, the central service platform, and the second service platform respectively, and communication between the first service platform and the second service platform is established through the central service platform, including:
[0097] Deploy a preset server component in the central service platform, deploy an access component in the first service platform, and deploy an agent component in the second service platform, wherein the deployment file of the agent component includes the service address and business ID of the server component connected to the agent component, and the deployment file of the access component includes the service address and business ID of the server component connected to the access component, and the mapped virtual agent business service address corresponding to each business ID;
[0098] After the server component is deployed, the TCP service address of the server component is exposed externally, where the server component is used to provide a cross-domain network connection channel;
[0099] After the deployment of the proxy component is completed, the business metadata information bound to the proxy component is registered in the metadata database of the server component through the server component service address in the deployment file of the proxy component, wherein the business metadata information includes the business ID;
[0100] The server component receives the access request from the access component, and based on the metadata database, builds a channel between the access component and the proxy component corresponding to the same business ID through the server component deployed in the central service platform to realize data transmission between different network platforms.
[0101] In this embodiment, the server component is used to provide a cross-cluster network connection channel to ensure that the access component and the proxy component are automatically connected; the proxy component is used to deploy corresponding to the aPaaS platform or k8s cluster data packaged separately in business units, and an agent component contains at least one business to realize the need to push the aPaaS platform or k8s cluster service data to the remote end (other aPaaS platforms or k8s clusters). The proxy component deployment file includes the server address selected for connection (referring to the TCP service address exposed to the outside after the server component is successfully deployed), business ID (one or more), and the access address corresponding to each business ID, key and other configuration parameter information; the access component is used to realize the need to pull service data from the remote end (other aPaaS platforms or k8s clusters), wherein the access component deployment file includes the server address to be connected, business ID, and the virtual proxy access address mapped to each business ID (by mapping the virtual proxy address to solve the problem of inaccessibility between clusters), key and other configuration parameter information. A server component can establish channels for multiple proxy components and access components, and clusters that need to communicate can deploy proxy components and access components according to actual needs.
[0102] In actual application scenarios, if the aPaaS platform or k8s cluster only needs to pull remote data, only the access component needs to be deployed; if only the data needs to be pushed to the remote end, only the proxy component needs to be deployed.
[0103] In this embodiment, after the server component, access component, and proxy component are deployed successfully, the following steps are performed to achieve cross-cluster network communication between the cluster where the access component is located and the cluster where the proxy component is located:
[0104] After the server component is successfully deployed, a TCP service address is exposed to the outside world;
[0105] After the proxy component is successfully deployed, it will actively register the bound business metadata information into the metadata database of the server component;
[0106] After receiving the registration information of the proxy component, the server component verifies whether the registered business metadata is accurate, that is, whether the information is missing or the format is correct. If the metadata verification passes, the bound business connectivity is tested.
[0107] After the access component is successfully deployed, when business service B accesses the access component to query data, the access component uses the STCP protocol to establish a connection access channel based on the server address in its deployment file. The access component can connect to the server component through the access channel. After connecting to the server component, the server component first queries the metadata database to verify whether the business ID carried by the access component exists. If it exists, it then verifies whether the key corresponds. After both the business ID and the key are successfully verified, the connection between the access component and the proxy component is realized. The server component proxies the access channel to the proxy address corresponding to the business ID, and then the proxy component accesses the business service A corresponding to the business ID. After business service A responds, the corresponding response data is returned to business service B through the access channel.
[0108] The cross-domain service registration method disclosed in the present invention realizes point-to-point connection through a central component, deploys multiple groups of such connections on different aPaaS platforms, opens up multiple data transmission tunnels, and pulls business services from multiple centers in parallel. After obtaining the services, the service registration operation is automatically performed to ensure that the business service data of each single center is not in an isolated state. Any center that has demand can obtain the existing service data of other centers through the transmission tunnel, forming multi-center data aggregation and completing automatic service registration. Moreover, each aPaaS platform can obtain the service data of any other platform in the multi-center without the need for cumbersome service application procedures and omitting complex cross-domain issues, so that the service data of each aPaaS platform in the multi-center can be interconnected and interoperable simply and conveniently.
[0109] See also Figure 2 , an embodiment of the present disclosure provides a cross-domain service registration system, the system comprising at least one first service platform, a central service platform and at least one second service platform, wherein,
[0110] In the system, designated components are deployed in the first service platform, the central service platform, and the second service platform respectively, and communication between the first service platform and the second service platform is established through the central service platform, wherein both the first service platform and the second service platform are connected to the central service platform, and the networks between the first service platform and the second service platform are different;
[0111] The first service platform is used to send a service data acquisition request to the central service platform for the second service platform; and is used to register the target service locally according to the target service data;
[0112] The central service platform is used to pull service data from the second service platform according to the service data acquisition request and send it to the first service platform.
[0113] The following takes the example of a first service platform requiring a first data service and a second data service of a second service platform to illustrate the process of automatically registering the first data service and the second data service on the first service platform:
[0114] When the first data service and the second data service are on the same second service platform, the first service platform finds that the existing data service cannot provide the first data service and the second data service to the outside world, and the first service platform initiates a data acquisition demand, targeting the first data service and the second data service of the second service platform. The central service platform opens two data tunnels, pointing to the second service platforms of the first data service and the second data service respectively to complete the data pulling operation. After pulling the relevant data, no human operation is required, and the pulled data is directly written into the database of the first service platform in order of timestamps, and the data is stored and the service is automatically registered directly by the program. After the data is written, the first data service and the second data service can be directly viewed and applied for in the first service platform. The first data service and the second data service, which originally belonged to the second service platform, are transmitted to the first service platform through the data tunnel opened by the central service platform, and the service is automatically registered;
[0115] See also Figure 3 In the case where the first data service and the second data service are on two different second service platforms, the first service platform finds that the existing data service cannot provide the first data service and the second data service to the outside world. The first service platform initiates a data acquisition demand, with the targets pointing to the first data service and the second data service of two different second service platforms respectively. The central service platform opens two data tunnels, pointing to the two different second service platforms of the first data service and the second data service respectively to complete the data pulling operation. After pulling the relevant data, no human operation is required. The pulled data is directly written into the database of the first service platform in sequence according to the timestamp, and the data is stored and the service is automatically registered directly by the program. After the data is written, the first data service and the second data service can be directly viewed and applied for in the first service platform. The first data service and the second data service, which originally belonged to two different second service platforms, are transmitted to the first service platform through the data tunnel opened by the central service platform, and the service is automatically registered.
[0116] In the cross-domain service registration system disclosed in the present invention, two components, deployment agent component and access component, are added to the aPaaS platform deployed in multiple locations. Point-to-point connection is achieved through the server component, data transmission tunnel is opened, the function of pulling and pushing new services across clusters is realized, and automatic registration of remote services is realized according to business needs.
[0117] The cross-domain service registration system disclosed in the present invention realizes cross-cluster communication of multiple aPaaS platforms and interconnection of service data, including service pulling and service pushing, through a multi-center service automatic discovery method, providing a new solution and specific plan for the multi-center service registration synchronization problem.
[0118] The cross-domain service registration system disclosed in the present invention solves the problem that services in multiple clusters are not interoperable and cannot be automatically discovered and registered.
[0119] The implementation process of the functions and effects of each platform in the above system is specifically described in the implementation process of the corresponding steps in the above method, which will not be repeated here.
[0120] As for the system embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The system embodiment described above is only schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of the present invention. Ordinary technicians in this field can understand and implement it without paying creative work.
[0121] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.
[0122] The foregoing is merely a specific embodiment of the present disclosure, which enables those skilled in the art to understand or implement the present disclosure. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features applied herein.
Claims
1. A cross-domain service registration method, characterized in that: The method comprises: Deploy designated components in the first service platform, the central service platform, and the second service platform respectively, and establish communication between the first service platform and the second service platform through the central service platform, wherein both the first service platform and the second service platform are connected to the central service platform, both the first service platform and the second service platform are data sharing platforms, and the networks between the first service platform and the second service platform are different; The first service platform sends a service data acquisition request to the central service platform for the second service platform; The central service platform pulls the target service data from the second service platform according to the service data acquisition request and sends it to the first service platform; The first service platform registers the target service locally based on the target service data. The target service data includes a target service and service registration parameters, and the first service platform registers the target service locally according to the target service data, including: The first service platform writes the target service into a local database to store the target service; Register the stored target service locally according to the service registration parameters. Wherein, the number of the target service data exceeds one, and the first service platform writes the target service into the local database, including: Sort the target service data according to the timestamp when the first service platform receives the target service data, and determine the order of the target service data; Write the target services into the local database in the order of the target service data. When the first data service and the second data service are on the same second service platform, the first service platform finds that the existing data service cannot provide the first data service and the second data service to the outside world. The first service platform initiates a data acquisition demand, and the target is the first data service and the second data service of the second service platform. The central service platform opens two data tunnels, which are respectively directed to the second service platforms of the first data service and the second data service to complete the data pulling operation. After pulling the relevant data, the pulled data is directly written into the database of the first service platform in order of timestamps, and the data is stored and the service is automatically registered directly by the program. After the data is written, the first data service and the second data service are directly viewed and applied for in the first service platform. In the case where the first data service and the second data service are respectively on two different second service platforms, the first service platform finds that the existing data service cannot provide the first data service and the second data service to the outside world, and the first service platform initiates a data acquisition demand, with the targets pointing to the first data service and the second data service of the two different second service platforms respectively. The central service platform opens two data tunnels, pointing to the two different second service platforms of the first data service and the second data service respectively to complete the data pulling operation. After pulling the relevant data, the pulled data is directly written into the database of the first service platform in order of timestamps, and the data is stored and the service is automatically registered directly by the program. After the data is written, the first data service and the second data service are directly viewed and applied for in the first service platform. The central service platform pulls the target service data from the second service platform according to the service data acquisition request and sends it to the first service platform, including: The central service platform receives and parses the service data acquisition request, obtains each type of target service data required by the request and each second service platform corresponding to each type of target service data, and sends a corresponding target service data acquisition request to each second service platform; Each second service platform sends corresponding target service data to the central service platform according to the target service data acquisition request; The central service platform receives the target service data and sends it to the first service platform. The storing of the target service comprises: Monitor and collect the storage status of the first service platform in real time, and use bottleneck identification technology to collect and obtain migration bottleneck status data information, and in terms of cache settings, detect cache adjustment status data information in real time to establish a software performance data set; The migration bottleneck status data information and cache adjustment status data information are transferred to the software performance data set, and the data is cleaned and feature extracted, and the processed data information is standardized according to the dimensionless processing technology; Cloud computing technology is used to comprehensively analyze and learn the migration bottleneck status data information after data cleaning to obtain the bottleneck factor, and the migration status coefficient is generated by combining the number of interruptions during data migration; Obtain block size and cache hit rate through cache adjustment status data information after feature extraction, and associate the block size with the cache hit rate to obtain a cache adjustment coefficient, conduct a comprehensive analysis on the cache adjustment coefficient and the migration state coefficient, and generate a software storage performance prediction model by combining with a neural network model and training, and obtain a performance status evaluation index after dimensionless processing; An evaluation threshold is set in advance, and the evaluation threshold is compared and analyzed with the performance situation evaluation index to obtain a prediction result, and a corresponding level improvement strategy is obtained based on the prediction result.
2. The method according to claim 1, characterized in that The performance status evaluation index is obtained by the following formula: ; Among them, TSzs represents the performance situation evaluation index, Ttlz represents the throughput, F1, F2 and F3 represent the proportional coefficients of the cache control coefficient Tkxs, the migration state coefficient Pyxs and the throughput Ttlz respectively, among which, 0.10≤F1≤0.22, 0.15≤F2≤0.36, 0.20≤F3≤0.42, and 0.55≤F1+F2+F3≤1.0, and C represents the first correction constant.
3. The method according to claim 1, characterized in that The migration state coefficient is obtained by the following formula: ; Among them, Pyxs represents the migration state coefficient, Ysjz represents the amount of migrated data, α and β both represent proportional coefficients, M1 represents the third correction constant, Pjyz represents the bottleneck factor, and Zdcs represents the number of interruptions.
4. The method according to claim 1, characterized in that The cache control coefficient Tkxs is obtained by the following formula: ; Wherein, RLz represents the cache capacity, Kds represents the block size, Hcmz represents the cache hit rate, a1 and a2 both represent proportional coefficients, and M2 represents the fourth correction constant.
5. The method according to claim 1, characterized in that The step of respectively deploying designated components in the first service platform, the central service platform, and the second service platform, and establishing communication between the first service platform and the second service platform through the central service platform includes: Deploy a preset server component in the central service platform, deploy an access component in the first service platform, and deploy an agent component in the second service platform, wherein the deployment file of the agent component includes the service address and business ID of the server component connected to the agent component, and the deployment file of the access component includes the service address and business ID of the server component connected to the access component, and the mapped virtual agent business service address corresponding to each business ID; After the server component is deployed, the TCP service address of the server component is exposed externally, where the server component is used to provide a cross-domain network connection channel; After the deployment of the proxy component is completed, the business metadata information bound to the proxy component is registered in the metadata database of the server component through the server component service address in the deployment file of the proxy component, wherein the business metadata information includes the business ID; The server component receives the access request from the access component, and based on the metadata database, builds a channel between the access component and the proxy component corresponding to the same business ID through the server component deployed in the central service platform to realize data transmission between different network platforms.
6. A cross-domain service registration system, characterized in that: The system includes at least one first service platform, a central service platform and at least one second service platform, wherein: In the system, designated components are deployed in the first service platform, the central service platform, and the second service platform respectively, and communication between the first service platform and the second service platform is established through the central service platform, wherein both the first service platform and the second service platform are connected to the central service platform, and the networks between the first service platform and the second service platform are different; The first service platform is used to send a service data acquisition request to the second service platform to the central service platform; and is used to register the target service locally according to the target service data; The central service platform is used to pull service data from the second service platform according to the service data acquisition request and send it to the first service platform. The target service data includes a target service and service registration parameters, and the first service platform registers the target service locally according to the target service data, including: The first service platform writes the target service into a local database to store the target service; Register the stored target service locally according to the service registration parameters. Wherein, the number of the target service data exceeds one, and the first service platform writes the target service into the local database, including: Sort the target service data according to the timestamp when the first service platform receives the target service data, and determine the order of the target service data; Write the target services into the local database in the order of the target service data. When the first data service and the second data service are on the same second service platform, the first service platform finds that the existing data service cannot provide the first data service and the second data service to the outside world. The first service platform initiates a data acquisition demand, and the target is the first data service and the second data service of the second service platform. The central service platform opens two data tunnels, which are respectively directed to the second service platforms of the first data service and the second data service to complete the data pulling operation. After pulling the relevant data, the pulled data is directly written into the database of the first service platform in order of timestamps, and the data is stored and the service is automatically registered directly by the program. After the data is written, the first data service and the second data service are directly viewed and applied for in the first service platform. In the case where the first data service and the second data service are respectively on two different second service platforms, the first service platform finds that the existing data service cannot provide the first data service and the second data service to the outside world, and the first service platform initiates a data acquisition demand, with the targets pointing to the first data service and the second data service of the two different second service platforms respectively. The central service platform opens two data tunnels, pointing to the two different second service platforms of the first data service and the second data service respectively to complete the data pulling operation. After pulling the relevant data, the pulled data is directly written into the database of the first service platform in order of timestamps, and the data is stored and the service is automatically registered directly by the program. After the data is written, the first data service and the second data service are directly viewed and applied for in the first service platform. The central service platform pulls the target service data from the second service platform according to the service data acquisition request and sends it to the first service platform, including: The central service platform receives and parses the service data acquisition request, obtains each type of target service data required by the request and each second service platform corresponding to each type of target service data, and sends a corresponding target service data acquisition request to each second service platform; Each second service platform sends corresponding target service data to the central service platform according to the target service data acquisition request; The central service platform receives the target service data and sends it to the first service platform. The storing of the target service comprises: Monitor and collect the storage status of the first service platform in real time, and use bottleneck identification technology to collect and obtain migration bottleneck status data information, and in terms of cache settings, detect cache adjustment status data information in real time to establish a software performance data set; The migration bottleneck status data information and cache adjustment status data information are transferred to the software performance data set, and the data is cleaned and feature extracted, and the processed data information is standardized according to the dimensionless processing technology; Cloud computing technology is used to comprehensively analyze and learn the migration bottleneck status data information after data cleaning to obtain the bottleneck factor, and the migration status coefficient is generated by combining the number of interruptions during data migration; Obtain block size and cache hit rate through cache adjustment status data information after feature extraction, and associate the block size with the cache hit rate to obtain a cache adjustment coefficient, conduct a comprehensive analysis on the cache adjustment coefficient and the migration state coefficient, and generate a software storage performance prediction model by combining with a neural network model and training, and obtain a performance status evaluation index after dimensionless processing; An evaluation threshold is set in advance, and the evaluation threshold is compared and analyzed with the performance situation evaluation index to obtain a prediction result, and a corresponding level improvement strategy is obtained based on the prediction result.
Citation Information
Patent Citations
Cross-cluster communication method and device, equipment and storage medium
CN117155934A
Method for realizing cross-cluster resource scheduling
CN117155939A
Software acquisition data storage performance improvement method and system
CN117420967A
Extensible framework for managing multiple Hadoop clusters
US10922284B1
