CN111245901B - Distributed service registration discovery method and system supporting service parameter issuing - Google Patents
Distributed service registration discovery method and system supporting service parameter issuing Download PDFInfo
- Publication number
- CN111245901B CN111245901B CN201911413776.5A CN201911413776A CN111245901B CN 111245901 B CN111245901 B CN 111245901B CN 201911413776 A CN201911413776 A CN 201911413776A CN 111245901 B CN111245901 B CN 111245901B
- Authority
- CN
- China
- Prior art keywords
- service
- instance
- upstream
- management platform
- distributed
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
Abstract
The invention discloses a distributed service registration discovery method and a system supporting service parameter issuing, which comprises the following steps of registering service information of all service instances in a distributed service cluster into a service registration center and establishing an information exchange channel; the upstream service instance inquires an address list of the downstream service instance where the required service is located from the service registration center through the service management platform according to the service processing requirement of the upstream service instance and calls the service; the operation and maintenance personnel configure service calling parameters through the service management platform and issue the service calling parameters to the service registration center; and the service registry sends the service calling parameters to the corresponding upstream service instance for use through the information exchange channel. The method provided by the invention can expand the existing distributed service registration discovery scenes, and improve the service availability and the service flexibility.
Description
Technical Field
The present invention relates to the field of technologies, and in particular, to a distributed service registration discovery method and system supporting service parameter delivery.
Background
In recent years, cloud computing and containerization technologies have evolved into a fire and heat, and for micro-service architectures, service registration and discovery components are essential. The service registration and discovery component mainly solves two problems: service registration and service discovery. In addition, in micro-service applications, services are in a dynamic state, and a certain mechanism is needed to process invalid service instances. Generally speaking, a service instance is in contact with a registry in a heartbeat mode after registration, and once the heartbeat is absent, the corresponding service instance is removed by the registry, that is, basic health check is performed on the service instance.
The existing service registration discovery scheme does not support the issue of service calling parameters in the service operation process to regulate and control service calling. For example, in the distributed service system, the service S1 and the service S2 are deployed in a distributed cluster, and their relationship is: and S1 calls an interface of S2 to realize a certain service function. In this scenario, S1 is an upstream service and S2 is a downstream service. A server of the S1 cluster obtains a server cluster address list of the S2 service through an existing service discovery scheme. And calling a certain server of the S2 cluster by a certain server of the S1 cluster based on a certain existing load balancing algorithm. Because the existing service registration discovery scheme cannot dynamically regulate and control a service calling mode, the requirements of the following two scenes cannot be met:
in one scenario, if the server of S2 is abnormal, the request delay for processing S1 is increased, and further the processing delay of the whole service function is increased, and in addition, if the server of S2 meets the health degree check requirement of the load balancing algorithm, the server of the upstream service S1 will always call the abnormal server of S2, and finally the user experience is degraded or even unavailable, in this scenario, the server of S1 needs to not call the service instance of the abnormal server of S2 by a certain method, but the prior art cannot realize the scenario;
the other scenario is that if a server in the S2 service cluster performs algorithm optimization and needs to perform existing network testing, that is, the upstream service S1 server is required to invoke an interface of the server based on a certain configuration policy, but the existing service registration discovery scheme cannot meet the scenario.
Disclosure of Invention
This section is for the purpose of summarizing some aspects of embodiments of the invention and to briefly introduce some preferred embodiments. In this section, as well as in the abstract and the title of the invention of this application, simplifications or omissions may be made to avoid obscuring the purpose of the section, the abstract and the title, and such simplifications or omissions are not intended to limit the scope of the invention.
The present invention has been made in view of the above-mentioned conventional problems.
Therefore, one of the technical problems solved by the present invention is: the distributed service registration discovery method supporting service parameter issuing is provided, so that a service registration discovery system can issue service calling parameters to each server instance, and distributed services can be adjusted based on dynamic parameters in the calling process.
In order to solve the technical problems, the invention provides the following technical scheme: a distributed service registration discovery method supporting service parameter issue comprises the following steps of registering service information of all service instances in a distributed service cluster into a service registration center and establishing an information exchange channel; after the upstream service instance is started, inquiring an address list of the downstream service instance where the required service is located from a service registration center through a service management platform according to the service processing requirement of the upstream service instance, and calling the service according to a load balancing scheduling strategy; the operation and maintenance personnel configure service calling parameters through the service management platform and send the parameters to the service registration center through the service management platform; and the service registry sends the service calling parameters to the corresponding upstream service instance for use through the information exchange channel.
As a preferred solution of the distributed service registration discovery method supporting service parameter issue described in the present invention, wherein: the service instance comprises an upstream service instance and a downstream service instance, distributed cluster deployment is adopted, the service instance calls a registration interface of a service registration center to register by adopting an HTTP (hyper text transport protocol), and registered service information comprises a service name, an IP (Internet protocol) address and a port for providing the service and a communication protocol adopted by the service.
As an optimized scheme of the distributed service registration discovery method supporting service parameter issue described in the present invention, wherein: after the service instances are successfully registered, the service registration center and each service instance establish an information exchange channel, and a websocket protocol is adopted for information exchange.
As an optimized scheme of the distributed service registration discovery method supporting service parameter issue described in the present invention, wherein: the query also comprises the following steps that the upstream service instance initiates a service discovery request to the service management platform, wherein the request carries request parameters including a service name and a service protocol; the service management platform receives the service discovery request and then analyzes the request parameters; when the local storage of the service management platform does not have a record corresponding to the service name, the service management platform initiates a query request to a service registration center; the service registry returns a list of addresses of downstream service instances to the service management platform.
As a preferred solution of the distributed service registration discovery method supporting service parameter issue described in the present invention, wherein: the service calling method comprises the following steps that after receiving a result returned by a service registration center, a service management platform stores a service name, a service protocol and an address list of a downstream service instance as a record in a local storage; the service management platform returns the address list result of the downstream service instance to the upstream service instance; and the upstream service instance initiates a service calling request to the downstream service instance according to the load balancing scheduling strategy.
As an optimized scheme of the distributed service registration discovery method supporting service parameter issue described in the present invention, wherein: the service calling parameters comprise an upstream service name, a downstream service name and service data, the service data comprise a user name set and an address set, and the address set comprises an IP address and a service interface.
As an optimized scheme of the distributed service registration discovery method supporting service parameter issue described in the present invention, wherein: the configuration of the service calling parameter comprises the following steps that an operation and maintenance administrator calls an interface of the service management platform to issue the service calling parameter; the service management platform transmits the service calling parameters to the service registration center through an interface of the service registration center.
As an optimized scheme of the distributed service registration discovery method supporting service parameter issue described in the present invention, wherein: the service registration center inquires each upstream service instance establishing an information exchange channel with the upstream service instance according to the name of the upstream service; the service registration center sends the service calling parameters to each upstream service instance through the information exchange channel; and the upstream service instance after receiving the service calling parameter adjusts the mode of calling the downstream service instance.
Therefore, another technical problem solved by the present invention is: the distributed service registration discovery system supporting service parameter issuing is provided, and the method can be realized by depending on the system.
In order to solve the technical problems, the invention provides the following technical scheme: a distributed service registration discovery system supporting service parameter issue comprises a service instance, wherein the service instance can perform service processing; a service registry to which the service instance can register service information; an information exchange channel for information exchange between the service instance and the service registry; and the service management platform can inquire and call the service and configure service calling parameters.
As an optimized scheme of the distributed service registration discovery system supporting service parameter issue described in the present invention, wherein: the service instances also include upstream service instances and downstream service instances, which are deployed in distributed clusters.
The invention has the beneficial effects that: the existing distributed service registration discovery scene is expanded, so that the service calling is more flexible and easy to expand, almost any service-related service calling scene can be met, and the availability and flexibility of the distributed service are increased.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise. Wherein:
fig. 1 is a schematic view of an overall flow structure of a distributed service registration discovery method supporting service parameter delivery according to a first embodiment of the present invention;
fig. 2 is a schematic view of a flow structure for configuring a service invocation parameter in a distributed service registration discovery method supporting service parameter issue according to a first embodiment of the present invention;
fig. 3 is a schematic diagram of an arrangement structure of a distributed service registration discovery system supporting service parameter delivery according to a second embodiment of the present invention.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present invention comprehensible, specific embodiments accompanied with figures are described in detail below, and it is apparent that the described embodiments are a part of the embodiments of the present invention, not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making creative efforts based on the embodiments of the present invention, shall fall within the protection scope of the present invention.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention, but the present invention may be practiced in other ways than those specifically described and will be readily apparent to those of ordinary skill in the art without departing from the spirit of the present invention, and therefore the present invention is not limited to the specific embodiments disclosed below.
Furthermore, reference herein to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one implementation of the invention. The appearances of the phrase "in one embodiment" in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments.
The present invention will be described in detail with reference to the drawings, wherein the cross-sectional views illustrating the structure of the device are not enlarged partially in general scale for convenience of illustration, and the drawings are only exemplary and should not be construed as limiting the scope of the present invention. In addition, the three-dimensional dimensions of length, width and depth should be included in the actual fabrication.
Also in the description of the present invention, it should be noted that the terms "upper, lower, inner and outer" and the like indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, which are only for convenience of description and simplification of description, but do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and thus, should not be construed as limiting the present invention. Furthermore, the terms first, second, or third are used for descriptive purposes only and are not to be construed as indicating or implying relative importance.
The terms "mounted, connected and connected" in the present invention are to be understood broadly, unless otherwise explicitly specified or limited, for example: can be fixedly connected, detachably connected or integrally connected; they may be mechanically, electrically, or directly connected, or indirectly connected through intervening media, or may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood in specific cases to those skilled in the art.
Example 1
The service registration and discovery component in the microservice architecture mainly solves two problems, namely service registration and service discovery, wherein service registration is that a service instance registers self service information to a registry. The part of service information comprises the IP address of the host where the service is located, the interface for providing the service, the self state of the exposed service, the access protocol and other information. And service discovery is the process by which a service instance requests the registry to obtain information about the services that are relied upon. The service instances acquire the information of the service instances registered therein through the registration center, and the service provided by the service instances is requested through the information.
Referring to fig. 1 to 2, to solve the problem that the existing service registration discovery scheme cannot dynamically regulate and control a service invocation manner, the embodiment provides a distributed service registration discovery method supporting service parameter issue, which improves the existing service registration discovery system, so that the service registration discovery system can issue service invocation parameters to each server instance, and the distributed service can be adjusted based on dynamic parameters in a invocation process.
Specifically, the method comprises the following steps of,
s1: registering service information of all service instances 100 in the distributed service cluster into a service registration center 200 and establishing an information exchange channel 300; specifically, all the server instances 100 in the distributed service cluster need to register service information to the service registration center 200, and the service registration center is not limited to a physical machine or a virtual machine, and in this embodiment, the server instances 100 include an upstream service instance 101 and a downstream service instance 102, and are deployed by using the distributed cluster.
The service registration center 200 adopts an HTTP protocol and a websocket protocol, wherein the HTTP protocol provides a service registration and query interface, the server instance 100 calls the registration interface of the service registration center 200 to perform registration by using the HTTP protocol, and service information including a service name, an IP address and a port for providing a service, and a communication protocol used by the service itself needs to be carried during registration.
After the service instances 100 are successfully registered, the service registration center 200 and each successfully registered service instance 100 establish an information exchange channel 300, and exchange information by using a websocket protocol. The service instances 100 need to establish a long connection with the service registry 200 or support the service registry to perform long polling for information exchange, and the service registry 200 uses the websocket protocol to push information to each service instance 100.
S2: after the upstream service instance 101 is started, according to the service processing requirement of the upstream service instance, the service management platform 400 inquires the service registration center 200 about the address list of the downstream service instance 102 where the required service is located, and calls the service according to the load balancing scheduling strategy; in particular, the query further comprises the steps of,
the upstream service instance 101 initiates a service discovery request to the service management platform 400, where the request carries request parameters including a service name and a service protocol; specifically, after each upstream service instance 101 is started, according to the service processing requirement of the upstream service instance, a server address list of the service is queried according to the service name, and the service discovery request carries the service name and the service protocol, where the service name is in the service information and the service protocol is the HTTP protocol.
The service management platform 400 receives the service discovery request and then analyzes the request parameters; the service management platform 400 parses the service name and the service agreement in the parameter, and queries the corresponding service name record in the local storage, which may be implemented by a MySql database in this embodiment.
When there is no record corresponding to the service name in the local storage of the service management platform 400, the service management platform 400 initiates a query request to the service registry 200; the service management platform 400 initiates a query request to the service registry 200 using the HTTP protocol, and the service registry 200 obtains the IP address and port of each downstream service instance 102 providing the service according to the service name.
The service registry 200 returns a list of addresses of downstream service instances 102 to the service management platform 400.
In addition, invoking the service further comprises the steps of,
after receiving the result returned by the service registration center 200, the service management platform 400 stores the service name, the service agreement, and the address list of the downstream service instance 102 as a record in the local storage; that is, the IP address and port of the downstream service instance 102 are stored in the service management platform 400, and at this time, if the same query request is received again next time, the result can be directly returned from the local storage.
The service management platform 400 returns the address list result of the downstream service instance 102 to the upstream service instance 101;
the upstream service instance 101 initiates a service invocation request to the downstream service instance 102 according to the load balancing scheduling policy. Those skilled in the art will appreciate that load balancing scheduling strategies are state of the art, such as round robin algorithms.
S3: the operation and maintenance personnel configure the service calling parameters through the service management platform 400 and send the parameters to the service registration center 200 through the service management platform 400; when the operation and maintenance personnel need to adjust the call of the upstream service instance 101 to the downstream service instance 102, the policy information is configured through the service provided by the service management platform 400, and the service provided by the service management platform 400 may be a Web service based on HTTP. Specifically, the configuration of the service invocation parameter includes the following steps,
the operation and maintenance administrator calls an interface of the service management platform 400 to issue service calling parameters; the service calling parameters include an upstream service name, a downstream service name and service data, the service data includes a user name set and an address set, the address set includes an IP address and a service interface, and the service data can be described by json, as follows:
the usernames represents a user name set, the upstream service instance 101 needs to transmit a user name parameter when calling an interface of the downstream service instance 102, and the upstream service instance 101 can call a service interface provided in an address set only when the user name transmitted by the downstream service instance 102 is in the user name set of the service data.
S4: the service registry 200 sends the service invocation parameters to the corresponding upstream service instance 101 for its use through the information exchange channel 300.
And sends the service invocation parameters to the corresponding upstream service instances 101 through the information exchange channel 300, and the upstream service instances 101 after receiving the service invocation parameters adjust the manner of invoking the downstream service instances 102.
Specifically, the process further comprises the following steps,
the service registration center 200 inquires each upstream service instance 101 with which the information exchange channel 300 is established according to the upstream service name; wherein, each upstream service instance 101 of the information exchange channel 300 established with the service invocation parameter in step S1 can be found according to the service name in the service invocation parameter.
The service registry 200 sends the service invocation parameters to each upstream service instance 101 through the information exchange channel 300;
the upstream service instance 101, having received the service invocation parameter, adjusts the manner in which the downstream service instance 102 is invoked. Specifically, after the upstream service instance 101 receives the service invocation parameter, when the downstream service instance 102 is subsequently invoked, the upstream service instance 101 determines whether the user name of the invocation request parameter is in the user name set of the service field of the service invocation parameter, and if so, directly invokes the service interface of the service data in the service invocation parameter.
It should be recognized that embodiments of the present invention can be realized and implemented by computer hardware, a combination of hardware and software, or by computer instructions stored in a non-transitory computer readable memory. The methods may be implemented in a computer program using standard programming techniques, including a non-transitory computer-readable storage medium configured with the computer program, where the storage medium so configured causes a computer to operate in a specific and predefined manner, according to the methods and figures described in the detailed description. Each program may be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language. Furthermore, the program can be run on a programmed application specific integrated circuit for this purpose.
Further, the operations of processes described herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The processes described herein (or variations and/or combinations thereof) may be performed under the control of one or more computer systems configured with executable instructions, and may be implemented as code (e.g., executable instructions, one or more computer programs, or one or more applications) collectively executed on one or more processors, by hardware, or combinations thereof. The computer program includes a plurality of instructions executable by one or more processors.
Further, the method may be implemented in any type of computing platform operatively connected to a suitable connection, including but not limited to a personal computer, mini computer, mainframe, workstation, networked or distributed computing environment, separate or integrated computer platform, or in communication with a charged particle tool or other imaging device, or the like. Aspects of the invention may be embodied in machine-readable code stored on a non-transitory storage medium or device, whether removable or integrated into a computing platform, such as a hard disk, optically read and/or write storage medium, RAM, ROM, or the like, such that it may be read by a programmable computer, which when read by the storage medium or device, is operative to configure and operate the computer to perform the procedures described herein. Further, the machine-readable code, or portions thereof, may be transmitted over a wired or wireless network. The invention described herein includes these and other different types of non-transitory computer-readable storage media when such media include instructions or programs that implement the steps described above in conjunction with a microprocessor or other data processor. The invention also includes the computer itself when programmed according to the methods and techniques described herein. A computer program can be applied to input data to perform the functions described herein to transform the input data to generate output data that is stored to non-volatile memory. The output information may also be applied to one or more output devices, such as a display. In a preferred embodiment of the invention, the transformed data represents physical and tangible objects, including particular visual depictions of physical and tangible objects produced on a display.
Example 2
Referring to the schematic illustration of fig. 3, in order to implement the above-mentioned distributed service registration discovery method for supporting service parameter issue, a distributed service registration discovery system for supporting service parameter issue is provided in this embodiment. Specifically, the system includes a service instance 100, a service registry 200, an information exchange channel 300, and a service management platform 400. Wherein, the service instance 100 can perform business processing; the service instance 100 can register the service information into the service registry 200; the information exchange channel 300 is used for information exchange between the service instance 100 and the service registration center 200; service management platform 400 is capable of querying and invoking services, as well as configuration of service invocation parameters.
Specifically, the service instance 100 further includes an upstream service instance 101 and a downstream service instance 102, and the upstream service instance 101 and the downstream service instance 102 are deployed in a distributed cluster.
The service instance 100, the service registry 200, and the service management platform 400 are in the same level, and are all server software implemented by using a programming language, for example, JAVA may be used for programming in this embodiment, and the software may run and work depending on a common computer.
The information exchange channel 300 is a bidirectional communication channel established by the service instance 100 and the service registration center 200 through the WebSocket protocol.
The server instance 100 accesses the service registry 200 through the HTTP protocol and receives information actively pushed by the service registry 200 by establishing a WebSocket connection with the service registry 200. The server instance 100 is able to access the service management platform 400 via the HTTP protocol.
The service management platform 400 can access the service registry 200 through the HTTP protocol.
As used in this application, the terms "component," "module," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being: a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of example, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the internet with other systems by way of the signal).
It should be noted that the above-mentioned embodiments are only for illustrating the technical solutions of the present invention and not for limiting, and although the present invention has been described in detail with reference to the preferred embodiments, it should be understood by those skilled in the art that modifications or equivalent substitutions may be made on the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, which should be covered by the claims of the present invention.
Claims (9)
1. A distributed service registration discovery method supporting service parameter issue is characterized in that: comprises the following steps of (a) carrying out,
registering service information of all service instances (100) in the distributed service cluster in a service registration center (200) and establishing an information exchange channel (300);
after the upstream service instance (101) is started, according to the self service processing requirement, the address list of the downstream service instance (102) where the required service is located is inquired from the service registration center (200) through the service management platform (400), and the service is called according to the load balancing scheduling strategy;
the operation and maintenance personnel configure the service calling parameters through the service management platform (400), and the service calling parameters are issued to the service registration center (200) by the service management platform (400);
the service registry (200) sends the service invocation parameters to the corresponding upstream service instance (101) for use by the service registry through the information exchange channel (300).
2. The method for registering and discovering distributed services supporting service parameter issue according to claim 1, wherein: the service instance (100) comprises an upstream service instance (101) and a downstream service instance (102), distributed cluster deployment is adopted, the service instance (100) calls a registration interface of the service registration center (200) to register by adopting an HTTP protocol, and registered service information comprises a service name, an IP address and a port for providing the service and a communication protocol adopted by the service.
3. The method for registering and discovering distributed services supporting service parameter issue according to claim 1 or 2, wherein: after the service instances (100) are successfully registered, the service registration center (200) and each service instance (100) establish an information exchange channel (300) and adopt a websocket protocol for information exchange.
4. The distributed service registration discovery method supporting service parameter delivery according to claim 3, wherein: the querying may further comprise the step of,
an upstream service instance (101) initiates a service discovery request to a service management platform (400), wherein the request carries request parameters including a service name and a service protocol;
the service management platform (400) receives the service discovery request and then analyzes the request parameters;
when the local storage of the service management platform (400) does not have a record corresponding to the service name, the service management platform (400) initiates a query request to the service registration center (200);
the service registry (200) returns a list of addresses of downstream service instances (102) to the service management platform (400).
5. The distributed service registration discovery method supporting service parameter delivery according to claim 4, wherein: the invoking service further comprises the step of,
after receiving the result returned by the service registration center (200), the service management platform (400) stores the service name, the service agreement and the address list of the downstream service instance (102) as a record in a local storage;
the service management platform (400) returns the address list result of the downstream service instance (102) to the upstream service instance (101);
the upstream service instance (101) initiates a service invocation request to the downstream service instance (102) according to the load balancing scheduling policy.
6. The method for registering and discovering distributed services supporting service parameter issue according to claim 4 or 5, wherein: the service calling parameters comprise an upstream service name, a downstream service name and service data, the service data comprise a user name set and an address set, and the address set comprises an IP address and a service interface.
7. The method for registering and discovering distributed services supporting service parameter issue according to claim 6, wherein: the configuration of the service invocation parameters includes the following steps,
the operation and maintenance administrator calls an interface of the service management platform (400) to issue service calling parameters;
the service management platform (400) passes service invocation parameters into the service registry (200) through an interface of the invocation service registry (200).
8. The method for registering and discovering distributed services supporting service parameter issue according to claim 7, wherein: the sending and using of the service invocation parameters further comprises the steps of,
the service registration center (200) inquires each upstream service instance (101) with which an information exchange channel (300) is established according to the upstream service name;
the service registration center (200) sends the service calling parameters to each upstream service instance (101) through the information exchange channel (300);
the upstream service instance (101) having received the service invocation parameter adjusts the manner in which the downstream service instance (102) is invoked.
9. A distributed service registration discovery system supporting service parameter issue is characterized in that: comprises the steps of (a) preparing a mixture of a plurality of raw materials,
a service instance (100), the service instance (100) capable of business processing;
a service registry (200), the service instance (100) being capable of registering service information to the service registry (200);
an information exchange channel (300), the information exchange channel (300) being used for information exchange between the service instance (100) and the service registry (200);
a service management platform (400), wherein the service management platform (400) can inquire and call services and configure service call parameters;
the service instance (100) further comprises an upstream service instance (101) and a downstream service instance (102), the upstream service instance (101) and the downstream service instance (102) being deployed in a distributed cluster;
after the upstream service instance (101) is started, the address list of the downstream service instance (102) where the required service is located is inquired from the service registration center (200) through the service management platform (400) according to the service processing requirement of the upstream service instance, and the service is called according to the load balancing scheduling strategy.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911413776.5A CN111245901B (en) | 2019-12-31 | 2019-12-31 | Distributed service registration discovery method and system supporting service parameter issuing |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911413776.5A CN111245901B (en) | 2019-12-31 | 2019-12-31 | Distributed service registration discovery method and system supporting service parameter issuing |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111245901A CN111245901A (en) | 2020-06-05 |
| CN111245901B true CN111245901B (en) | 2023-04-07 |
Family
ID=70876041
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911413776.5A Active CN111245901B (en) | 2019-12-31 | 2019-12-31 | Distributed service registration discovery method and system supporting service parameter issuing |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111245901B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111711569A (en) * | 2020-06-16 | 2020-09-25 | 普元信息技术股份有限公司 | System and method for realizing request dynamic routing in enterprise distributed application |
| CN111984289A (en) * | 2020-07-31 | 2020-11-24 | 广州市百果园信息技术有限公司 | Service updating method, device, equipment and storage medium |
| CN113515608A (en) * | 2021-06-15 | 2021-10-19 | 微梦创科网络科技（中国）有限公司 | Intelligent working method and system |
| CN113556251A (en) * | 2021-07-22 | 2021-10-26 | 浙江百应科技有限公司 | Anti-fraud decision engine business service registration method and system |
| CN113742105B (en) * | 2021-09-01 | 2024-03-12 | 欧电云信息科技(江苏)有限公司 | Method, device and medium for adapting micro-service framework |
| CN114363403A (en) * | 2021-12-28 | 2022-04-15 | 金蝶医疗软件科技有限公司 | Service access method, system, computer device and storage medium |
| CN115344327B (en) * | 2022-08-19 | 2023-07-28 | 中电金信软件有限公司 | Application module switching method and device, electronic equipment and readable storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106972975A (en) * | 2017-04-27 | 2017-07-21 | 上海斐讯数据通信技术有限公司 | A kind of server management method and system |
| CN108366102A (en) * | 2018-01-26 | 2018-08-03 | 北京奇艺世纪科技有限公司 | A kind of service discovery method, device and electronic equipment based on Consul |
| CN110543368A (en) * | 2019-09-06 | 2019-12-06 | 西藏宁算科技集团有限公司 | Distributed service health examination method and system |
-
2019
- 2019-12-31 CN CN201911413776.5A patent/CN111245901B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106972975A (en) * | 2017-04-27 | 2017-07-21 | 上海斐讯数据通信技术有限公司 | A kind of server management method and system |
| CN108366102A (en) * | 2018-01-26 | 2018-08-03 | 北京奇艺世纪科技有限公司 | A kind of service discovery method, device and electronic equipment based on Consul |
| CN110543368A (en) * | 2019-09-06 | 2019-12-06 | 西藏宁算科技集团有限公司 | Distributed service health examination method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111245901A (en) | 2020-06-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111245901B (en) | Distributed service registration discovery method and system supporting service parameter issuing | |
| US11363105B2 (en) | Determining a target service based on a service discovery request | |
| US11750702B2 (en) | Subscription and notification service | |
| US7548969B2 (en) | Computer system polling with adjustable intervals based on rules and server states | |
| CN110958281B (en) | Data transmission method and communication device based on Internet of things | |
| JP2018511843A (en) | Method and device for displaying content on the same screen and terminal device | |
| CN112867988A (en) | Implementing compliance settings by a mobile device to follow a configuration scenario | |
| CN110557357A (en) | remote procedure call protocol self-adaption method, related device and server | |
| US20150304404A1 (en) | System architecture, subsystem, and method for opening telecommunications network capability | |
| WO2019223099A1 (en) | Application program calling method and system | |
| US11700301B2 (en) | Service registration based on service capabilities requirements and preferences | |
| EP3738294B1 (en) | Mechanisms for the adaptive control of service layer operations | |
| CN111615128A (en) | Multi-access edge computing method, platform and system | |
| WO2019034091A1 (en) | Distribution method for distributed data computing, device, server and storage medium | |
| KR101251630B1 (en) | System and method for providing push service | |
| US20130138768A1 (en) | Method and System for Dynamic Service Creation on Sensor Gateways | |
| CN107592229B (en) | Service calling method, device and system | |
| CN116633765A (en) | Service processing method, device, equipment and storage medium | |
| CN112565340A (en) | Service scheduling method, device, computer system and medium for distributed application | |
| JP2017130934A (en) | Distributed controllers |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20210220 Address after: 11 / F, Liuwu building, Liuwu New District, Lhasa City, Tibet Autonomous Region, 850000 Applicant after: Tibet ningsuan Technology Group Co.,Ltd. Address before: Building C4, No.55 Liyuan South Road, moling street, Nanjing, Jiangsu Province Applicant before: DILU TECHNOLOGY Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |