CN115643306B - Dynamic issuing method for grid service instance and configuration - Google Patents
Dynamic issuing method for grid service instance and configuration Download PDFInfo
- Publication number
- CN115643306B CN115643306B CN202211089369.5A CN202211089369A CN115643306B CN 115643306 B CN115643306 B CN 115643306B CN 202211089369 A CN202211089369 A CN 202211089369A CN 115643306 B CN115643306 B CN 115643306B
- Authority
- CN
- China
- Prior art keywords
- service
- examples
- configuration
- grid
- instance
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 41
- 238000012216 screening Methods 0.000 claims abstract description 59
- 238000006243 chemical reaction Methods 0.000 claims abstract description 12
- 238000001914 filtration Methods 0.000 claims 1
- 238000004891 communication Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 239000002071 nanotube Substances 0.000 description 3
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Landscapes
- Computer And Data Communications (AREA)
Abstract
The invention relates to a dynamic issuing method of grid service instance and configuration, which comprises the following steps: service instance issuing: the side car initiates a service registration request to a unified registration center; the grid control plane subscribes to service instances from the unified registry; the unified registration center performs assembly grouping of service instances and issues the service instances to the grid control surface; according to CR configuration of the side car, grid control filters service examples and sends the service examples down to the side car; and (3) configuration issuing: the management plane calls a grid configuration conversion service to issue configuration; the grid configuration conversion service stores the issued configuration into a database; the grid control plane monitors the configuration change of the grid configuration conversion service and acquires the corresponding current configuration; and according to CR configuration of the side car, the grid control surface performs configuration screening and then issues the screened configuration to the side car. Compared with the prior art, the method and the system can realize centralized allocation and dynamic issuing, avoid that all service instances and configurations are issued to each side car, effectively save the consumption of resources and improve the service access efficiency.
Description
Technical Field
The present invention relates to a dynamic issuing method for grid service instance and configuration.
Background
With the rapid development of micro-service technology, many problems are inevitably encountered when introducing a micro-service architecture and enjoying the numerous benefits it brings. These problems can be largely generalized as communication problems between micro-service applications, and it is with respect to these problems that the service grid has created a solution for managing communication between individual micro-services in a micro-service application.
In order for a microservice application to run successfully, the development team of each microservice needs to process the business logic of each microservice, add numerous other logic for each microservice that is not related to the actual business, and possibly configure something extra in the cluster, which is a problem. The need to handle numerous additional logics means that the developer of the micro-services cannot be attentive to handle the actual service logic, but rather is busy adding logic for secure, communication for each micro-service. This adds significantly to the complexity of each micro-service, and when the number of micro-services reaches a certain number, configuring these logic one by one for numerous micro-services becomes almost impossible task. To this end, the service grid gives a solution of: rather than adding a plurality of logics to each micro-service separately, it is more reasonable to separate the logics irrelevant to the actual business logic from the micro-service, put the logics into an agent program of the micro-service and intensively process the logics. In addition, the developer does not have to add proxy configuration to the deployment file of the micro-service, because the service grid has a control plane that automatically adds this proxy in each micro-service. The micro services can now communicate with each other through these agents, which are the service grid, to enable service-to-service communication consisting of control planes.
The Service grid is mainly based on k8s Service as a Service instance source at present, configuration nano tube native is based on etcd in k8s, namely different clusters are managed, service registration discovery in the grid is completed depending on k8s, and a grid control plane directly acquires Service instances and configuration through k8s-apiserver, so that the defects are that cross-cluster Service discovery and configuration issuing cannot be carried out, and instances and configuration issuing cannot be screened but the full-scale issuing is carried out. Because centralized dispatch cannot be performed, if service nanotubes of multiple clusters are to be performed, there is a lot of effort, and in practical application, when all service instances and configurations are issued to each side car (agents deployed in a data plane in a service grid), resource consumption will increase, and meanwhile, service access efficiency is reduced.
Disclosure of Invention
The invention aims to overcome the defects of the prior art and provide a dynamic issuing method of grid service examples and configurations, which can realize centralized allocation and dynamic issuing, and avoid issuing all service examples and configurations to each side car, thereby effectively saving the consumption of resources and improving the efficiency of service access.
The aim of the invention can be achieved by the following technical scheme: the dynamic issuing method of the grid service instance and the configuration comprises a service instance issuing process and a configuration issuing process, wherein the service instance issuing process comprises the following steps:
a1, a service side vehicle initiates a service registration request to a unified registration center to finish service registration;
A2, subscribing service instances from a unified registry by the grid control plane;
A3, the unified registry groups the service instances and sends the service instances to the grid control plane;
A4, according to CR configuration of the side car, grid control performs service instance screening and then issues the service instance screening to the side car;
the configuration issuing process comprises the following steps:
b1, the management plane calls the grid configuration conversion service to issue configuration;
b2, the grid configuration conversion service stores the issued configuration into a database;
b3, the grid control plane monitors the configuration change of the grid configuration conversion service according to the network area cluster of the grid control plane, and obtains the configuration of the current computer room network area cluster;
and B4, according to CR configuration of the side car, the grid control surface performs configuration screening and then issues the screened configuration to the side car.
Further, the step A1 specifically includes that the service side car obtains the labels of the machine room, the network area and the cluster environment where the current service is located, and then the side car initiates registration and registers the labels as metadata.
Further, grpc connection is established between the grid control plane and the unified registry in the step A2, and the grid control plane subscribes registration information with the same label from the unified registry by using the labels according to the machine room, the network area and the cluster environment where the grid control plane is located.
Further, in the step A3, the unified registry specifically performs the assembly grouping of the service instances according to the labels.
Further, in step A3, if the service needs cross-cluster access or cross-project access, the unified registry pulls the service F5 information and the black-and-white list configuration from the management plane control platform to screen out the F5 configuration corresponding to the service instance of other clusters, and then issues the service configuration, and the cross-project access pushes the service instance designated to be accessed to the service access party.
Further, in step A3, the unified registry performs an on-demand instance push instance screening process, including peer-project instance screening and whitelist instance screening.
Further, the same item instance screening means that the unified registry screens all the instances according to the item ID of the side car, compares all the instances of the same item with the machine room, the network area and the cluster of the side car, screens the instances according to the set item priority rule, and adds the screened instances into the list.
Further, the white list instance screening refers to inquiring the white list service name according to the service name of the side car and all unshielded instances of the white list service, and the unified registry compares all instances of the white list service with the machine room, the network area and the cluster of the side car, screens out the instances according to the set white list priority rule, and adds the instances into the list.
Further, the item priority rule specifically includes:
1) Screening out the examples with the same machine room, the same network area and the same cluster, if the number of the examples is greater than 0, directly adding the examples into a push list, and interrupting screening;
2) If the number of the screened examples in the step 1) is equal to 0, continuing to screen out examples with the same machine room, different network areas and matched clusters, if the number of the examples is greater than 0, adding the examples into an example list A, and interrupting screening;
3) If the number of the screened examples in the step 2) is equal to 0, continuing to screen out the examples with the same machine room, the same network area and unmatched clusters, if the number of the examples is greater than 0, adding the examples into an example list A, and interrupting screening;
4) If the number of the screened examples in the step 3) is equal to 0, continuing to screen out different examples matched with the clusters in the machine room, if the number of the examples is greater than 0, adding the examples into an example list A, and interrupting screening;
5) Traversing the instance list A, sequentially inquiring the IP and the port of the machine room, the network area and the F5 of the cluster where each instance is located, replacing the IP and the port of the current instance, and adding the IP and the port into the push list.
Further, the white list priority rule specifically includes:
1) Screening out the examples with the same machine room, the same network area and the same cluster, if the number of the examples is greater than 0, directly adding the examples into a push list, and interrupting screening;
2) If the number of the screened examples in the step 1) is equal to 0, continuing to screen out examples with the same machine room, different network areas and matched clusters, if the number of the examples is greater than 0, adding the examples into an example list A, and interrupting screening;
3) If the number of the screened examples in the step 2) is equal to 0, continuing to screen out the examples with the same machine room, the same network area and unmatched clusters, if the number of the examples is greater than 0, adding the examples into an example list A, and interrupting screening;
4) If the number of the screened examples in the step 3) is equal to 0, continuing to screen out different examples matched with the clusters in the machine room, if the number of the examples is greater than 0, adding the examples into an example list A, and interrupting screening;
5) Traversing the instance list A, sequentially inquiring the IP and the port of the machine room, the network area and the F5 of the cluster where each instance is located, replacing the IP and the port of the current instance, and adding the IP and the port into the push list.
Compared with the prior art, the method adopts a unified registry, utilizes the unified registry to nano-tube service instances of all clusters, dynamically distributes the service instances to different service grid clusters according to different service tags through the unified registry, and intensively stores the configuration in a database, so that the capacity of k8s-apiserver can be abstracted, and when the management plane distributes the configuration, the abstracted service is called to store the configuration in the database and distributed to the corresponding grid control plane according to a specific tag, thereby realizing the dynamic distribution of the service instances and the configuration. All service instances and configurations can be effectively prevented from being issued to each side car, so that the consumption of resources is greatly reduced, and the service access efficiency is improved.
In the invention, the service registration is completed by initiating a registration request to the unified registration center by the labels such as the network area clusters of the machine room carried by the side vehicles, thereby being capable of setting the self-defined labels to carry out data aggregation and arrangement, the side vehicles can carry out the detection activity of the service container, and if the service container has no problem, the service registration can be carried out, and the service availability can be effectively ensured.
Drawings
FIG. 1 is a schematic flow chart of a method for issuing a service instance in the present invention;
FIG. 2 is a flow chart of a method for configuration issuing in the present invention;
FIG. 3 is a schematic diagram of an application component architecture of a service grid scheme in an embodiment;
FIG. 4 is a schematic diagram of a service instance issuing process in an embodiment;
Fig. 5 is a schematic diagram of a configuration issuing process in an embodiment.
Detailed Description
The invention will now be described in detail with reference to the drawings and specific examples.
Examples
As shown in fig. 1 and fig. 2, a dynamic service instance and configuration issuing method includes a service instance issuing process and a configuration issuing process, where the service instance issuing process includes the following steps:
a1, a service side vehicle initiates a service registration request to a unified registration center to finish service registration;
A2, subscribing service instances from a unified registry by the grid control plane;
A3, the unified registry groups the service instances and sends the service instances to the grid control plane;
A4, according to CR configuration of the side car, grid control performs service instance screening and then issues the service instance screening to the side car;
The configuration issuing process comprises the following steps:
b1, the management plane calls the grid configuration conversion service to issue configuration;
b2, the grid configuration conversion service stores the issued configuration into a database;
b3, the grid control plane monitors the configuration change of the grid configuration conversion service according to the network area cluster of the grid control plane, and obtains the configuration of the current computer room network area cluster;
and B4, according to CR configuration of the side car, the grid control surface performs configuration screening and then issues the screened configuration to the side car.
In this embodiment, as shown in fig. 3, a Nacos registry is adopted as a unified registry to unify service instances of all clusters, and dynamically issue the instances to different service grid clusters according to different service labels through Nacos, and the configuration is stored in a database in a centralized manner, and then issued to corresponding grid control planes according to specific labels.
The embodiment applies the above technical solution, where the example issuing process is shown in fig. 4, and mainly includes:
1. the service side car acquires the labels of the machine room, the network area and the cluster environment where the current service is located, and the side car initiates registration and registers the labels as metadata.
2. The grid control surface establishes grpc connection with the unified registry, and uses the labels to subscribe the registry with registration information of the same label according to the cluster environment of the computer room network area where the grid control surface is located.
3. The unified registry groups the service instances according to the labels and issues them to the grid control plane at once.
4. The grid control surface screens service examples according to the CR configuration of Sidecar (side car) and issues the service examples to the side car.
In step 3, if the service needs cross-cluster access or cross-project access, the registry screens out the F5 configuration corresponding to the service instance of other clusters according to the configuration of the management plane and issues the F5 configuration, and the cross-project access pushes the service instance designated to be accessed to the service access party.
In step 3, nacos also executes on-demand instance push instance screening logic, including peer instance screening and whitelist instance screening.
Same item instance screening:
Nacos screening out all the examples according to the item ID of Sidecar, comparing all the examples of the same item with the machine room, network area and cluster of sidecar, screening out the examples according to the following priority, and adding the examples into a list.
1) Screening out the examples with the same machine room, the same network area and the same cluster, if the number of the examples is more than 0, directly adding the examples into a push list, and interrupting screening.
2) If the number of the screened examples in the step 1) is equal to 0, continuing to screen out the examples with the same machine room, different network areas and matched clusters, if the number of the examples is greater than 0, adding the examples into an example list A, and interrupting screening.
3) If the number of the screened examples in the step 2) is equal to 0, continuing to screen out the examples with the same machine room, the same network area and the unmatched clusters, if the number of the examples is greater than 0, adding the examples into an example list A, and interrupting screening.
4) If the number of the screened examples in the step 3) is equal to 0, continuing to screen out different examples matched with the clusters in the machine room, if the number of the examples is greater than 0, adding the examples into the example list A, and interrupting screening.
Traversing the instance list A to sequentially query the IP and the port of the machine room, the network area and the F5 of the cluster where each instance is located, replacing the IP and the port of the current instance, and adding the IP and the port into the push list.
White list instance screening:
And inquiring the service name of the white list according to the service name Sidecar, and comparing all the unmasked examples of the white list service with a machine room, a network area and a cluster of Sidecar, screening out the examples according to the following priority, and adding the examples into a list.
1) Screening out the examples with the same machine room, the same network area and the same cluster, if the number of the examples is more than 0, directly adding the examples into a push list, and interrupting screening.
2) If the number of the screened examples in the step 1) is equal to 0, continuing to screen out the examples with the same machine room, different network areas and matched clusters, if the number of the examples is greater than 0, adding the examples into an example list A, and interrupting screening.
3) If the number of the screened examples in the step 2) is equal to 0, continuing to screen out the examples with the same machine room, the same network area and the unmatched clusters, if the number of the examples is greater than 0, adding the examples into an example list A, and interrupting screening.
4) If the number of the screened examples in the step 3) is equal to 0, continuing to screen out different examples matched with the clusters in the machine room, if the number of the examples is greater than 0, adding the examples into the example list A, and interrupting screening.
Traversing the instance list A to sequentially query the IP and the port of the machine room, the network area and the F5 of the cluster where each instance is located, replacing the IP and the port of the current instance, and adding the IP and the port into the push list.
The configuration issuing process is shown in fig. 5, and mainly includes:
1. the management plane invokes Nacos-apiserver to issue a configuration.
2. Nacos-apiserver store the configuration issued in a database.
3. The grid control plane monitors Nacos-apiserver configuration changes according to the network area cluster of the grid control plane, and obtains the configuration of the current computer room network area cluster.
4. The grid control plane performs configuration screening according to the CR configuration of Sidecar and issues the configuration screening to the side car.
In summary, according to the technical scheme, the fact that service registration discovery in the existing grid is completed depending on k8s is considered, and the grid control plane directly acquires service examples and configuration through k8s-apiserver, so that cross-cluster service discovery and configuration issuing cannot be performed in the mode, and the examples and configuration issuing cannot be screened but is performed in a full quantity. According to the technical scheme, the service instance and the configuration are separated from k8s and managed by the unified registry and the database, the instance is managed to the unified registry to be capable of conditionally issuing the instance, and resource waste is reduced, so that the robustness of the system is effectively improved, the service configuration is uniformly stored in one database cluster, and the configuration can be issued in multiple clusters.
In the technical scheme, the service instance in the registry is unified to distribute the service instance according to the computer room network area cluster, so that the problem of total distribution of the service instance is solved, and the memory use of the grid control surface is greatly saved.
The grid configuration is stored and distributed through nacos-apiserver and can be completely separated from k8s-apiserver for configuration, so that the problem that a plurality of k8s clusters cannot be uniformly managed in configuration can be solved.
The service registration is completed by the side car (carrying labels such as a computer room network area cluster, and the like), the original capability in the prior art is based on k8s service, and the custom labels can not be set for data aggregation and arrangement.
Claims (10)
1. The grid service instance and configuration dynamic issuing method is characterized by comprising a service instance issuing process and a configuration issuing process, wherein the service instance issuing process comprises the following steps of:
a1, a service side vehicle initiates a service registration request to a unified registration center to finish service registration;
A2, subscribing service instances from a unified registry by the grid control plane;
A3, the unified registry groups the service instances and sends the service instances to the grid control plane;
A4, according to CR configuration of the side car, grid control performs service instance screening and then issues the service instance screening to the side car;
the configuration issuing process comprises the following steps:
b1, the management plane calls the grid configuration conversion service to issue configuration;
b2, the grid configuration conversion service stores the issued configuration into a database;
b3, the grid control plane monitors the configuration change of the grid configuration conversion service according to the network area cluster of the grid control plane, and obtains the configuration of the current computer room network area cluster;
and B4, according to CR configuration of the side car, the grid control surface performs configuration screening and then issues the screened configuration to the side car.
2. The method for dynamically issuing grid service instances and configurations according to claim 1, wherein step A1 is specifically that a service side car obtains labels of a machine room, a network area and a cluster environment where a current service is located, and then the side car initiates registration and registers the labels as metadata.
3. The method for dynamically issuing grid service instances and configurations according to claim 2, wherein a grpc connection is established between the grid control plane and the unified registry in step A2, and the grid control plane subscribes to registration information with the same label from the unified registry by using the labels according to a machine room, a network area and a cluster environment where the grid control plane is located.
4. A method for dynamically delivering grid services instances and configurations according to claim 3, wherein said unified registry in step A3 performs service instance assembly grouping according to labels.
5. The method for dynamically issuing grid service instances and configurations according to claim 4, wherein in the step A3, if the service needs cross-cluster access or cross-project access, the unified registry pulls service F5 information and black-and-white list configuration from the management plane control platform to screen out F5 configurations corresponding to service instances of other clusters, and issues the service instances, and the cross-project access pushes the service instances designated to be accessed to the service access party.
6. The method according to claim 4, wherein the unified registry in step A3 performs an on-demand instance push instance screening process including peer instance screening and whitelist instance screening.
7. The method for dynamically issuing grid service instances and configurations according to claim 6, wherein the same-project instance screening means that a unified registry screens all instances according to project IDs of side vehicles, compares all instances of the same project with machine rooms, network areas and clusters of the side vehicles, screens the instances according to set project priority rules, and adds the screened instances to the list.
8. The method for dynamically issuing grid service instances and configurations according to claim 6, wherein the filtering of the whitelist instance refers to querying a whitelist service name according to a service name of a side car and all unmasked instances of the whitelist service, and the unified registry compares all instances of the whitelist service with a machine room, a network area and a cluster of the side car, and filters the instances according to a set whitelist priority rule and adds the filtered instances to the list.
9. The method for dynamically issuing grid service instances and configurations according to claim 7, wherein the item priority rule is specifically:
1) Screening out the examples with the same machine room, the same network area and the same cluster, if the number of the examples is greater than 0, directly adding the examples into a push list, and interrupting screening;
2) If the number of the screened examples in the step 1) is equal to 0, continuing to screen out examples with the same machine room, different network areas and matched clusters, if the number of the examples is greater than 0, adding the examples into an example list A, and interrupting screening;
3) If the number of the screened examples in the step 2) is equal to 0, continuing to screen out the examples with the same machine room, the same network area and unmatched clusters, if the number of the examples is greater than 0, adding the examples into an example list A, and interrupting screening;
4) If the number of the screened examples in the step 3) is equal to 0, continuing to screen out different examples matched with the clusters in the machine room, if the number of the examples is greater than 0, adding the examples into an example list A, and interrupting screening;
5) Traversing the instance list A, sequentially inquiring the IP and the port of the machine room, the network area and the F5 of the cluster where each instance is located, replacing the IP and the port of the current instance, and adding the IP and the port into the push list.
10. The method for dynamically issuing grid service instances and configurations according to claim 8, wherein the rule of white list priority is specifically:
1) Screening out the examples with the same machine room, the same network area and the same cluster, if the number of the examples is greater than 0, directly adding the examples into a push list, and interrupting screening;
2) If the number of the screened examples in the step 1) is equal to 0, continuing to screen out examples with the same machine room, different network areas and matched clusters, if the number of the examples is greater than 0, adding the examples into an example list A, and interrupting screening;
3) If the number of the screened examples in the step 2) is equal to 0, continuing to screen out the examples with the same machine room, the same network area and unmatched clusters, if the number of the examples is greater than 0, adding the examples into an example list A, and interrupting screening;
4) If the number of the screened examples in the step 3) is equal to 0, continuing to screen out different examples matched with the clusters in the machine room, if the number of the examples is greater than 0, adding the examples into an example list A, and interrupting screening;
5) Traversing the instance list A, sequentially inquiring the IP and the port of the machine room, the network area and the F5 of the cluster where each instance is located, replacing the IP and the port of the current instance, and adding the IP and the port into the push list.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211089369.5A CN115643306B (en) | 2022-09-07 | 2022-09-07 | Dynamic issuing method for grid service instance and configuration |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211089369.5A CN115643306B (en) | 2022-09-07 | 2022-09-07 | Dynamic issuing method for grid service instance and configuration |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115643306A CN115643306A (en) | 2023-01-24 |
| CN115643306B true CN115643306B (en) | 2024-07-23 |
Family
ID=84940277
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211089369.5A Active CN115643306B (en) | 2022-09-07 | 2022-09-07 | Dynamic issuing method for grid service instance and configuration |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115643306B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112311786A (en) * | 2020-10-28 | 2021-02-02 | 北京健康之家科技有限公司 | Service request processing method and device, storage medium and computing equipment |
| CN113296927A (en) * | 2020-06-09 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Construction method of service grid instance, service grid system and multi-cluster system |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113315820B (en) * | 2021-05-20 | 2022-11-08 | 西安华讯科技有限责任公司 | Method and device for constructing entity grid network |
| CN114237704B (en) * | 2021-11-15 | 2023-06-09 | 贵州大学 | Method for integrating Istio by spring-closed-alibaba sacos framework |
| CN114884959A (en) * | 2022-03-23 | 2022-08-09 | 中国人寿保险股份有限公司 | Deployment method of multi-cloud and multi-activity architecture and related equipment |
-
2022
- 2022-09-07 CN CN202211089369.5A patent/CN115643306B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113296927A (en) * | 2020-06-09 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Construction method of service grid instance, service grid system and multi-cluster system |
| CN112311786A (en) * | 2020-10-28 | 2021-02-02 | 北京健康之家科技有限公司 | Service request processing method and device, storage medium and computing equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115643306A (en) | 2023-01-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109240821B (en) | Distributed cross-domain collaborative computing and service system and method based on edge computing | |
| CN102682052B (en) | The data query that filtering data stores | |
| CN101645022B (en) | Work scheduling management system and method for a plurality of colonies | |
| US9461877B1 (en) | Aggregating network resource allocation information and network resource configuration information | |
| CN101207550A (en) | Load balancing system and method for multi business to implement load balancing | |
| WO2019083841A1 (en) | Network slice management | |
| CN105786603B (en) | Distributed high-concurrency service processing system and method | |
| US20080155038A1 (en) | Method and apparatus for aggregating change subscriptions and change notifications | |
| CN105354076A (en) | Application deployment method and device | |
| CN101562804B (en) | Region management server system based on mobile P2P and deploying method thereof | |
| CN103716408A (en) | Enterprise application integration method and system based on enterprise service bus (ESB) | |
| CN110297867B (en) | Database cluster operation method and system based on domestic CPU and distributed container cluster | |
| CN101741905A (en) | Rapid deployment method for cluster | |
| CN110519354A (en) | Distributed object storage system and service processing method and storage medium thereof | |
| CN111831362A (en) | Method for automatic discovery, classification, deployment and management of K8s environment monitoring | |
| CN115643306B (en) | Dynamic issuing method for grid service instance and configuration | |
| CN107479870A (en) | A kind of third party's class libraries call method, device, mobile terminal and storage medium | |
| CN108259605B (en) | Data calling system and method based on multiple data centers | |
| CN113791799A (en) | System upgrading method and device, computer readable storage medium and electronic equipment | |
| CN108810107B (en) | Cloud management platform and service method of two-state IT (information technology) business | |
| CN115037757B (en) | Multi-cluster service management system | |
| CN103647712B (en) | The method and system of distributed route processing business | |
| CN103677994B (en) | Distributed data processing system, device and method | |
| CN114024976B (en) | Big data service architecture based on 5G and method for constructing big data service | |
| CN114328587A (en) | NDC message distributed analysis system architecture integration method and device |
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 |