CN118175195A - Micro-service expansion method, system, equipment and storage medium based on service grid - Google Patents
Micro-service expansion method, system, equipment and storage medium based on service grid Download PDFInfo
- Publication number
- CN118175195A CN118175195A CN202410122023.3A CN202410122023A CN118175195A CN 118175195 A CN118175195 A CN 118175195A CN 202410122023 A CN202410122023 A CN 202410122023A CN 118175195 A CN118175195 A CN 118175195A
- Authority
- CN
- China
- Prior art keywords
- service
- grid
- request
- micro
- established
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 41
- 238000006243 chemical reaction Methods 0.000 claims description 8
- 238000012545 processing Methods 0.000 abstract description 10
- 238000004891 communication Methods 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 9
- 238000004590 computer program Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 4
- CDAMQYCTVBEQLQ-HBHTWFHGSA-N 4-[4-[bis(2-chloroethyl)amino]phenyl]butanoic acid;1,4-dihydroxy-5,8-bis[2-(2-hydroxyethylamino)ethylamino]anthracene-9,10-dione;(8s,9s,10r,11s,13s,14s,17r)-11,17-dihydroxy-17-(2-hydroxyacetyl)-10,13-dimethyl-7,8,9,11,12,14,15,16-octahydro-6h-cyclopenta[a Chemical compound OC(=O)CCCC1=CC=C(N(CCCl)CCCl)C=C1.O=C1C=C[C@]2(C)[C@H]3[C@@H](O)C[C@](C)([C@@](CC4)(O)C(=O)CO)[C@@H]4[C@@H]3CCC2=C1.O=C1C2=C(O)C=CC(O)=C2C(=O)C2=C1C(NCCNCCO)=CC=C2NCCNCCO CDAMQYCTVBEQLQ-HBHTWFHGSA-N 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000004927 fusion Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000005067 remediation Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Landscapes
- Stored Programmes (AREA)
Abstract
The embodiment of the invention provides a service grid-based micro-service extension method, a system, equipment and a storage medium, and belongs to the technical field of communication. The micro-service expansion method based on the service grid is executed by a micro-service container and specifically comprises the following steps: determining to acquire service information uploaded by a service end, and transmitting the service information to a service grid so that the service grid performs service registration according to the service information; wherein the service grid is deployed in a micro-service container; and determining that a request for accessing the server sent by the client is received, and sending the request to the service grid so that the service grid manages the request. The invention has the advantages of completely decoupling the business and the treatment and improving the efficiency of micro-service data processing.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a service grid-based micro-service extension method, a service grid-based micro-service extension system, an electronic device, and a readable storage medium.
Background
Aiming at large-scale business application, business rules are changeable, business scenes are complex and complicated, manual operation workload is huge, and challenges are provided for building a power transaction system in particular to the current newly-emerging power transaction market. In order to adapt to the changeable business scene, keep up with the market changing footsteps, an information system is urgently needed for assistance.
In order to quickly influence market demands and timely grasp market trends, all home barrel components of a SpringCloud technology system in a JDK (Java Development Kit Java language software development kit) form are often adopted at the initial stage of system construction to construct various business micro services, and the micro services are finally deployed in a k8s (kubernetes) container arrangement system to construct an information system on the basis. SpringCloud provides a development tool set for building distributed applications, which is a standard for micro-service remediation over a long period of time. However, in a single language environment, the problems of service registration, untimely service discovery and the like occur in the running process of the system, and the diversified demands of clients cannot be met.
Disclosure of Invention
The embodiment of the invention aims to provide a service grid-based micro-service extension method, a system, equipment and a storage medium, so as to solve the problem of low service data processing efficiency of the existing micro-service architecture.
To achieve the above object, an embodiment of the present invention provides a service grid-based micro service extension method, which is executed by a micro service container, the method including:
Determining to acquire service information uploaded by a service end, and transmitting the service information to a service grid so that the service grid performs service registration according to the service information; wherein the service grid is deployed in the micro-service container;
And determining that a request for accessing the server sent by the client is received, and sending the request to the service grid so that the service grid manages the request.
Optionally, the service grid includes a control panel and a data panel; the service information comprises service information of an established service end and service information of a newly-built service end;
the step of issuing the service information to the service grid so that the service grid performs service registration according to the service information comprises the following steps:
Nesting the established service end into the service grid, so that the data panel obtains the service information of the established service end, and uploading the service information of the established service end to the control panel for service registration;
The established service end is the established service end in the micro service container before the current service registration is carried out.
Optionally, the issuing the service information to the service grid, so that the service grid performs service registration according to the service information, further includes:
The service information of the newly built service end is sent to the network interface of the service grid by utilizing the data panel, so that the network interface uploads the service information of the newly built service end to the control panel for service registration;
the newly-built server is a server containing new services.
Optionally, the request for accessing the server includes: a request for accessing an established server and a request for accessing a newly built server;
The method further comprises the steps of:
After receiving a request for accessing the established service end sent by the client, nesting the established gateway into the service grid by utilizing a preset service conversion strategy;
The sending the request to the service grid, so that the service grid manages the request, includes:
And sending the request for accessing the established service end to the service grid, so that the service grid manages the request for accessing the established service end.
Optionally, the sending the request to the service grid, so that the service grid manages the request, further includes:
and sending the request for accessing the newly-built service end to a flow management component of the service grid, so that the flow management component manages the request for accessing the newly-built service end.
Optionally, the method further comprises:
Judging whether the built registration center supports a preset configuration synchronization protocol or not; wherein the established registry is a registry contained in the micro-service container;
if yes, service information of the established registration center is issued to a control panel of the service grid for service registration.
Optionally, if the established registry does not support the preset configuration synchronization protocol, sending the service information of the established registry to the network interface of the service grid by using a preset service synchronization policy, so that the network interface sends the service information of the established registry to the control panel for service registration.
In a second aspect of the embodiments of the present invention, there is provided a service grid-based micro service extension system, including:
The micro-service container is used for transmitting service information uploaded by a service end to the service grid so that the service grid performs service registration according to the service information; the server is also used for sending the request of accessing the server sent by the client to the service grid so that the service grid manages the request;
The server is used for bearing service information and uploading the service information to the micro-service container;
And the client is used for receiving a request of accessing the server, which is input by a user, and sending the request of accessing the server to the micro-service container.
In a third aspect of the embodiments of the present invention, there is provided an electronic apparatus, including: a processor and a memory storing machine-readable instructions executable by the processor to perform steps recited in any one of the possible implementations of the first aspect when executed by the processor.
In a fourth aspect of the embodiments of the present invention, there is provided a computer-readable storage medium having stored thereon instructions for causing a machine to perform the steps described in any one of the possible implementations of the first aspect.
According to the embodiment of the invention, the service grid is introduced into the micro-service container, the service information uploaded by the service end is determined, the service information is sent to the service grid for registration, and then the request of the service grid for the client to access the service end is determined based on the registered service information and is sent to the service grid for management. In the embodiment of the invention, the service grids are deployed in the originally built micro-service container, so that the management among the services is introduced into the service grids for management, the micro-service container only needs to pay attention to the services, the complete decoupling of the services and the management is realized, and the efficiency of micro-service data processing is improved.
Additional features and advantages of embodiments of the invention will be set forth in the detailed description which follows.
Drawings
The accompanying drawings are included to provide a further understanding of embodiments of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain, without limitation, the embodiments of the invention. In the drawings:
FIG. 1 is a flow chart of a first embodiment of a service grid-based micro-service extension method of the present invention;
FIG. 2 is a schematic diagram of registration service interworking between a micro service container and a service grid;
FIG. 3 is a schematic diagram of gateway fusion between a micro-service container and a service grid;
fig. 4 is a schematic architecture diagram of a service grid-based micro-service extension system according to the present application.
Detailed Description
The following describes the detailed implementation of the embodiments of the present invention with reference to the drawings. It should be understood that the detailed description and specific examples, while indicating and illustrating the invention, are not intended to limit the invention.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application.
In the description of embodiments of the present application, the technical terms "first," "second," and the like are used merely to distinguish between different objects and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated, a particular order or a primary or secondary relationship. In the description of the embodiments of the present application, the meaning of "plurality" is two or more unless explicitly defined otherwise.
Example 1
Referring to fig. 1, fig. 1 is a flowchart of a service grid-based micro service extension method according to the present embodiment.
Step S100: determining to acquire service information uploaded by a service end, and transmitting the service information to a service grid so that the service grid performs service registration according to the service information; wherein the service grid is deployed in a micro-service container.
It is to be understood that the present embodiment acts on micro-service containers, and that a service grid is deployed in each micro-service container for brokering service governance work of the micro-service container. The micro-service container can be a micro-service container constructed by a SpringCloud technical system of JDK form deployed in a system with k8s as a container; the service grid may be a grid modality of Istio.
The server is used for storing the service content provided by the micro service.
The service information may be address information of each server.
The service grid comprises a data panel and a control panel, wherein the data panel consists of a group of intelligent agents (envoys), and the agents are deployed as side vehicles and mediate and control all network communication among the micro services; the control panel (Pilot) is responsible for managing and configuring agents to route traffic and enforcing policies at runtime.
It should be understood that before the service grid is embedded, the registry, the service gateway and the service end are already built in the micro service container, so after the service grid is accessed, the service grid is used as a service registry and configuration center, the information in the built registry needs to be issued to the registry of the service grid, or the built service end is embedded into the service grid, so that the service information of the service end built by the registry of the service grid can be registered, thereby supporting the configuration and management of each service end by the service grid.
In one embodiment, step S100 includes:
Step S101: nesting the established service end into a service grid, so that a data panel obtains service information of the established service end, and uploading the service information of the established service end to a control panel for service registration; the established service end is the established service end in the micro service container before the current service registration is carried out.
Specifically, as shown in fig. 2, the established service end is introduced to the control panel and the data panel of Istio by means of sidecar-injector, and then the established service is introduced to Pilot by using Istio and kubernetes tight sets to realize service registration, i.e. service discovery.
Step S102: the service information of the newly built service end is sent to a network interface of the service grid by utilizing the data panel, so that the network interface uploads the service information of the newly built service end to the control panel for service registration; the newly-built server is a server containing new services.
It can be understood that after the service grid is introduced, the newly-built service end is directly nested in the service grid, as shown in fig. 2, and service information of the newly-built service end can be directly introduced into the Pilot through kube-apiserver of kubernetes to complete service registration.
According to the embodiment, different registration means are adopted for the established service end and the newly-built service end respectively, the established service end registers the service information of the established service end through the control panel which supports the service grid by nesting the service end in the grid, and the service information of the newly-built service end is directly introduced by using an interface for the newly-built service end so as to realize service discovery of the newly-built service by the control panel, so that the original micro-service system is expanded under the condition of not changing codes of the existing service end, and the practicability of a micro-service architecture is improved.
In another specific embodiment, step S100 further includes:
Step S103: judging whether the built registration center supports a preset configuration synchronization protocol or not; wherein the established registry is a registry contained in the micro-service container.
Step S104: if yes, service information in the built registration center is issued to the control panel for service registration.
Step S105: if not, the service information of the built registration center is sent to the network interface of the service grid by utilizing the preset service synchronization strategy, so that the network interface sends the service information of the built registration center to the control panel for service registration.
The preset configuration synchronization protocol may be an MCP protocol.
The preset service synchronization policy is a self-defined service synchronization mode, and can be set according to the actual micro-service requirement and the requirement of registration service.
It will be appreciated that the established registry in this embodiment may include Nacos, eureka, zookeeper registration services. Wherein Nacos already supports the MCP protocol, and service information can be directly issued to Istio; and Eureka, zookeeper does not support MCP protocol, and needs to customize and develop 'custom service synchronization', connect and monitor Istio external service registration system to obtain the latest service information; istio external service information is converted to SERVICEENTRY by "custom service synchronization" and resources are published into kubernetes by MCP.
In the embodiment, the registration services in the established registration centers are classified, the established registration centers supporting the preset configuration synchronization protocol can directly send the service information to the service grid, the preset configuration synchronization protocol is not supported, the service data in the registration centers are sent to the control panel of the service grid through the network interface of the server to complete service registration through the preset service synchronization strategy, the registration centers of multiple types are supported, and the practicability of the micro service is improved.
Step S200: and determining that a request for accessing the server sent by the client is received, and sending the request to the service grid so that the service grid manages the request.
The client is a user end using the micro service, and can be a computer or a tablet computer.
It should be understood that before the service grid is embedded, the service gateway and the service end are already built in the micro service container, so after the service grid is accessed, the service grid is used as a center for monitoring and controlling the flow, the built gateway is integrated into the service grid, and the service grid is utilized to monitor and manage the flow for accessing the micro service, so that the flow monitoring, the link tracking, the disconnection and the like are performed on the built service end under the condition that the codes of the micro service and the built gateway are not modified.
In one embodiment, step S200 includes:
It can be understood that the request for accessing the server includes a request for accessing an established server and a request for accessing a newly built server, and the present embodiment performs different gateway management for different access requests.
It can be understood that before sending the access request of the client to the service grid, the built gateway originally set by the micro service container needs to be nested into the service grid by using a preset custom service conversion policy, so as to support the management of the request of the client to access the built service on the premise of not modifying the micro service code after the service grid is deployed beside the micro service container.
Step S201: after receiving a request for accessing the established service end sent by the client, the established gateway is nested into the service grid by utilizing a preset service conversion strategy.
Step S202: and sending the request for accessing the established service end to the service grid, so that the service grid manages the request for accessing the established service end.
The preset service conversion strategy can be a custom conversion strategy and can be determined by the current micro-service requirement.
Specifically, as shown in fig. 3, the established gateway sends the service request of the gateway to the downstream service through the custom service conversion policy. Under the condition that the established micro-service does not need to modify codes, the Envoy and Pilot-agent processes are automatically introduced through Sidecar-injector components, the established micro-service and the business service are deployed in the same pod, and meanwhile, the access flow of the service is introduced into a Istio control panel and a data plane through routing rule configuration and target rule configuration, so that flow monitoring, fuse breaking, link tracking and the like of the established micro-service are realized.
Step S203: and sending the request for accessing the newly-built server to a flow management component of the service grid, so that the flow management component manages the request for accessing the newly-built server.
Specifically, as shown in fig. 3, for a request of a client to access a newly-built service, since the newly-built service is originally nested in a service grid, the client access flow can be directly managed by using INGRESSGATEWAY components in Istio.
According to the embodiment, the built gateway is subjected to grid nesting, so that the monitoring and management of the access flow of the client to the built server are realized on the premise that the codes of the existing micro-services are not modified. And the access request of the client to the newly-built server is managed by directly utilizing the flow management component of the service grid, and the expansion of the micro-service gateway is realized on the basis of not modifying the original micro-service code.
In this embodiment, service information uploaded by a service end is sent to a service grid to register, and then a request of a client for accessing the service end is managed by using the service grid based on the registered service information. In the embodiment of the invention, the service grids are deployed in the originally built micro-service container, so that the management among the services is introduced into the service grids for management, the micro-service container only needs to pay attention to the services, the complete decoupling of the services and the management is realized, and the efficiency of micro-service data processing is improved.
Example two
Referring to fig. 4, fig. 4 is a schematic architecture diagram of a micro service extension system based on a service grid according to an embodiment of the present application.
As shown in fig. 4, a service grid-based micro service extension system includes: micro-service container 10, service grid 20, client 30, old service system 40.
The micro service container 10 may be a micro service container constructed by the SpringCloud technical architecture of JDK modality in the micro service container of the k8s system, and the service grid 20 is deployed in the micro service container 10. The micro service container 10 includes an old service system 40 and a service grid 20, and in the running process, the micro service container 10 introduces service information into the service grid 20 in a down-sending or nested manner so as to support the service grid 20 to realize service discovery of an established service end or a newly-built service end; based on the service discovery of the established service end, the received access request is issued to the service grid for processing, so as to support the management of the access request of the client 30 to the established service end by the service grid 20.
The service grid 20 can be Istio in grid form, the service grid 20 is deployed in the micro service container 10 for realizing the management of the micro service, the service grid 20 comprises a control panel and a data panel, the data panel consists of a group of intelligent agents (envoys), and the agents are deployed as side vehicles for mediating and controlling all network communication among the micro services; the control panel (Pilot) is responsible for managing and configuring agents to route traffic and enforcing policies at runtime. In the operation process, the service grid 20 registers the received service information, completes service discovery, receives the client 30 access request sent by the micro service container 10 based on the service discovery of each service end, and manages the request for accessing the service end; and returns the response service to the client 30 when the response service is obtained according to the user access request.
The client 30 may be a computer configured to send a request for accessing a corresponding service to the micro service container 10 based on a service request input by a client at the client 30, and receive response service information returned by the micro service container 10.
The old service system 40 comprises a built registration center, a built service end and a built gateway, the old service system is contained in the micro service container 10 and is connected with the service grid 20, and in the operation process, service information of the built registration center and the built service end is introduced into the service grid 20 in a down-sending or nested mode so as to support the service grid 20 to realize service discovery of the built service end; based on the service discovery of the established service end, the established gateway is introduced into the service grid 20 according to the self-defined service conversion mode, and the received access request is issued into the service grid 20 for processing, so as to support the management of the access request of the service grid 20 to the client 30 to the established service end.
It should be understood that the system corresponds to the service grid-based micro service extension method embodiment, and is capable of executing the steps involved in the method embodiment, and specific functions of the apparatus may be referred to the above description, and detailed descriptions are omitted herein as appropriate to avoid repetition. The device includes at least one software functional module that can be stored in memory in the form of software or firmware (firmware) or cured in an Operating System (OS) of the device.
Example III
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, etc., such as Read Only Memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
Example IV
Embodiments of the present invention also provide a computer readable storage medium having instructions stored thereon for, when executed by a processor, adapting to execute a program having service grid based micro-service extension method steps.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In addition, the specific features described in the above embodiments may be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, various possible combinations of embodiments of the present invention are not described in detail.
In addition, the functional modules in the embodiments of the present application may be integrated together to form a single part, or each module may exist alone, or two or more modules may be integrated to form a single part.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and variations of the present application will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. which come within the spirit and principles of the application are to be included in the scope of the claims of the present application.
Claims (10)
1. A method of service grid-based micro-service extension performed by a micro-service container, the method comprising:
Determining to acquire service information uploaded by a service end, and transmitting the service information to a service grid so that the service grid performs service registration according to the service information; wherein the service grid is deployed in the micro-service container;
And determining that a request for accessing the server sent by the client is received, and sending the request to the service grid so that the service grid manages the request.
2. The service grid-based micro service extension method of claim 1, wherein the service grid comprises a control panel and a data panel; the service information includes: service information of the established service end and service information of the newly-built service end;
the step of issuing the service information to the service grid so that the service grid performs service registration according to the service information comprises the following steps:
Nesting the established service end into the service grid, so that the data panel obtains the service information of the established service end, and uploading the service information of the established service end to the control panel for service registration;
The established service end is the established service end in the micro service container before the current service registration is carried out.
3. The service grid-based micro service extension method according to claim 2, wherein the delivering the service information to the service grid, so that the service grid performs service registration according to the service information, further comprises:
The service information of the newly built service end is sent to the network interface of the service grid by utilizing the data panel, so that the network interface uploads the service information of the newly built service end to the control panel for service registration;
the newly-built server is a server containing new services.
4. The service grid based micro service extension method according to claim 3, wherein the request for accessing the server comprises: a request for accessing an established server and a request for accessing a newly built server;
The method further comprises the steps of:
After receiving a request for accessing the established service end sent by the client, nesting the established gateway into the service grid by utilizing a preset service conversion strategy;
The sending the request to the service grid, so that the service grid manages the request, includes:
And sending the request for accessing the established service end to the service grid, so that the service grid manages the request for accessing the established service end.
5. The service grid based micro service extension method of claim 4, wherein the sending the request into the service grid so that the service grid manages the request further comprises:
and sending the request for accessing the newly-built service end to a flow management component of the service grid, so that the flow management component manages the request for accessing the newly-built service end.
6. The service grid-based micro-service extension method of claim 2, further comprising:
Judging whether the built registration center supports a preset configuration synchronization protocol or not; wherein the established registry is a registry contained in the micro-service container;
if yes, service information of the established registration center is issued to a control panel of the service grid for service registration.
7. The service grid-based micro service extension method according to claim 6, wherein if the established registry does not support a preset configuration synchronization protocol, service information of the established registry is sent to a network interface of the service grid by using a preset service synchronization policy, so that the network interface sends the service information of the established registry to the control panel for service registration.
8. A service grid based micro-service extension system, comprising:
The micro-service container is used for transmitting service information uploaded by a service end to the service grid so that the service grid performs service registration according to the service information; the server is also used for sending the request of accessing the server sent by the client to the service grid so that the service grid manages the request;
The server is used for bearing service information and uploading the service information to the micro-service container;
And the client is used for receiving a request of accessing the server, which is input by a user, and sending the request of accessing the server to the micro-service container.
9. An electronic device, comprising: a processor and a memory storing machine-readable instructions executable by the processor to perform the service grid-based micro-service extension method of any one of claims 1-7.
10. A computer readable storage medium having instructions stored thereon for causing a machine to perform the service grid based micro service extension method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410122023.3A CN118175195A (en) | 2024-01-29 | 2024-01-29 | Micro-service expansion method, system, equipment and storage medium based on service grid |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410122023.3A CN118175195A (en) | 2024-01-29 | 2024-01-29 | Micro-service expansion method, system, equipment and storage medium based on service grid |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN118175195A true CN118175195A (en) | 2024-06-11 |
Family
ID=91351841
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410122023.3A Pending CN118175195A (en) | 2024-01-29 | 2024-01-29 | Micro-service expansion method, system, equipment and storage medium based on service grid |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN118175195A (en) |
-
2024
- 2024-01-29 CN CN202410122023.3A patent/CN118175195A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20240204978A1 (en) | Interface for digital operator platform including response caching | |
| JP7130142B2 (en) | Communication method, apparatus, entity and computer readable storage medium | |
| CN109561171B (en) | Configuration method and device of virtual private cloud service | |
| US7167861B2 (en) | Mobile application service container | |
| US11646939B2 (en) | Network function NF management method and NF management device | |
| CN102868935A (en) | Scheduling method for responding multiple sources in content distribution network (CDN) | |
| CN104243301A (en) | Method, device and system for generating service path | |
| CN113765816A (en) | Flow control method, system, equipment and medium based on service grid | |
| CN114301914B (en) | Cloud edge cooperation method, cloud edge cooperation device and storage medium | |
| CN112637037B (en) | Cross-region container communication system, method, storage medium and computer equipment | |
| EP3712768B1 (en) | Management of services in an edge computing system | |
| CN118175195A (en) | Micro-service expansion method, system, equipment and storage medium based on service grid | |
| JP2024518946A (en) | Operation maintenance method, device, system, server, electronic device, and medium | |
| CN111061723A (en) | Workflow implementation method and device | |
| US20230275974A1 (en) | Network functionality (nf) aware service provision based on service communication proxy (scp) | |
| CN115225645A (en) | Service updating method, device, system and storage medium | |
| CN114844788A (en) | Network data analysis method, system, device and storage medium | |
| CN113873052B (en) | Domain name resolution method, device and equipment of Kubernetes cluster | |
| CN111601303A (en) | Method and device for processing protocol data unit session and electronic equipment | |
| WO2023078234A1 (en) | Method for controlling code execution on basis of distributed cloud network, and device and system | |
| CN103442258A (en) | Method, device and system for achieving flow resource management | |
| CN102811463B (en) | Method and device for load sharing of MME (mobile management entity) network element | |
| CN111314457B (en) | Method and device for setting virtual private cloud | |
| CN115604333B (en) | Distributed big data analysis service scheduling method and system based on dubbo | |
| US20240179210A1 (en) | Service Execution Handling |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination |