CN111240760A - Application publishing method, system, storage medium and equipment based on registry - Google Patents
Application publishing method, system, storage medium and equipment based on registry Download PDFInfo
- Publication number
- CN111240760A CN111240760A CN202010019387.0A CN202010019387A CN111240760A CN 111240760 A CN111240760 A CN 111240760A CN 202010019387 A CN202010019387 A CN 202010019387A CN 111240760 A CN111240760 A CN 111240760A
- Authority
- CN
- China
- Prior art keywords
- application
- server
- notification
- issuing system
- registry
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Hardware Redundancy (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides an application issuing method, a system, a storage medium and electronic equipment based on a registration center, wherein the application issuing method comprises the following steps: s110, the issuing system informs the server to start application; s130, when the application is in a first starting state, the issuing system informs the server to register the information of the application to a registration center; s150, when the application is in a second starting state, the issuing system sends a circulation flow notification to the server; s170, the issuing system judges whether the application is normally started according to a request result received by the server in a preset time period based on the circulation flow notification; if the application is normal, the application is started, and if the application is abnormal, the off-line process is started. According to the application release method based on the registration center, the service provider can realize the lossless release of the application only by keeping the heartbeat with the registration center, and the problem that the application generates abnormity in the release process is avoided.
Description
Technical Field
The invention relates to the technical field of computers, in particular to an application issuing method and system based on a registration center, a storage medium and electronic equipment.
Background
With the development of the technology, containerization technologies such as docker and kubernets provide great convenience for automatic packaging, continuous integration, continuous delivery and continuous deployment, and one application is released every day and becomes a normal state.
Currently, there are calls between applications using rpc (i.e., remote procedure call protocol) and calls using rest (i.e., representational state transfer) protocol. The calling protocols basically realize the registration and discovery of the applications based on the registries, and if the upper line and the lower line of the applications are not smooth between the registries, errors are easy to cause, and the calling protocols are not friendly to user experience. Further, the current mutual discovery between the applications inside the enterprise generally uses a unified registry, and either the applications and the registry keep heartbeat, or besides keeping heartbeat with the registry, the service invoker and the service invoker also need to keep heartbeat, and discover which machines have problems by the heartbeat, so as to remove the relevant machines from the service list.
However, simple heartbeat retention has the following disadvantages: 1) if the service invoker simply keeps the heartbeat with the registry, there is a delay. It is possible that the service provider has gone offline, but the service invoker has not received a corresponding offline message from the registry, causing it to send a request to the machine that has gone offline, resulting in a request error. 2) If the heartbeat is also kept between the service caller and the service provider, the more the service caller, the more the heartbeat needs to be kept, and a large amount of heartbeat messages exist in the network, which wastes resources. 3) In any heartbeat keeping mode, the service provider does not know whether the service caller receives the offline message of the service provider or not and does not know when the service provider can interrupt the service. 4) No service invoker may be taken offline at any time on behalf of the service provider, since it may have tasks running on its own, and taking offline may also create related problems.
Disclosure of Invention
In view of the problems in the prior art, an object of the present invention is to provide a method, a system, a storage medium, and an electronic device for publishing an application based on a registry, so as to implement lossless publishing of the application.
According to an aspect of the present invention, there is provided a registry-based application publishing method, comprising:
s110, the issuing system informs the server to start application;
s130, when the application is in a first starting state, the issuing system informs the server to register the information of the application to a registration center;
s150, when the application is in a second starting state, the issuing system sends a circulation flow notification to the server;
s170, the issuing system judges whether the application is normally started according to a request result received by the server in a preset time period based on the circulation flow notification; if the application is normal, the application is started, and if the application is abnormal, the off-line process is started.
In an embodiment of the present invention, the steps S110 and S130 further include:
and S120, after the issuing system obtains the notice that the application starts to be started and fed back by the server, circularly checking the starting state of the application.
In an embodiment of the present invention, the steps S130 and S150 further include:
s140, the issuing system circularly checks the starting state of the application after acquiring the notification of successful application registration fed back by the server.
In an embodiment of the present invention, the information of the application includes: name, type, function interface information, node address information including IP address and port number, and version information.
In one embodiment of the present invention, in step S150, the time interval for transmitting the circulation flow rate notification is 1S.
In an embodiment of the present invention, the step of starting the offline process includes:
s210, the issuing system informs the server to close the application.
S220, after the issuing system obtains the notice that the server starts to close the application, the issuing system informs the server to cancel the registration of the information of the application to the registration center.
S230, the release system circularly checks the closing state of the application after acquiring the notification that the registration center fed back by the server cancels the registration of the application;
s240, the issuing system circularly obtains the current flow value of the server after obtaining the notice that the application fed back by the server is completely closed.
And S250, when the release system does not obtain the current flow value of the server after exceeding the preset time, closing the application.
According to still another aspect of the present invention, there is provided a publishing system of an application, the publishing system including:
the first notification module is used for notifying the server to start the application;
the second notification module is used for notifying the server to register the information of the application to the registration center when the application is in the first starting state;
the third notification module is used for sending a circulation flow notification to the server when the application is in the second starting state;
the first checking module is used for circularly checking the starting state of the application;
the first judging module is used for judging whether the application is normally started according to a request result received by the server within a preset time period.
In an embodiment of the present invention, the publishing system further includes:
and the fourth notification module is used for notifying the server to close the application.
And the fifth notification module is used for notifying the server to cancel the registration of the information of the application to the registration center.
The second checking module is used for circularly checking the closing state of the application;
and the acquisition module is used for circularly acquiring the current flow value of the server.
And the second judgment module is used for judging whether the issuing system exceeds the preset time length and cannot acquire the current flow value of the server.
According to a further aspect of the present invention, there is provided a storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the registry-based application publication method as described above.
According to still another aspect of the present invention, there is provided an electronic apparatus including:
a processor;
a storage medium having stored thereon a computer program which, when executed by the processor, performs the steps in the registry-based application publication method as described above.
According to the application release method based on the registration center, the service provider can realize the lossless release of the application only by keeping the heartbeat with the registration center, and the problem that the application generates abnormity in the release process is avoided. In addition, the service provider does not need to keep heartbeat with the service caller, so that a large amount of heartbeat messages in the network are avoided, and resources can be effectively saved.
Drawings
Other features, objects and advantages of the present invention will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, with reference to the accompanying drawings.
Fig. 1 is a flowchart of a method for publishing an application based on a registry according to an embodiment of the present invention.
Fig. 2 is a flowchart of a registry-based application publishing method in another embodiment of the present invention.
FIG. 3 is a diagram illustrating steps of a process of initiating a logoff according to an embodiment of the present invention.
Fig. 4 is a schematic structural diagram of a publishing system in an embodiment of the present invention.
Fig. 5 is a schematic structural diagram of a distribution system in another embodiment of the present invention.
Fig. 6 is a schematic structural diagram of a computer-readable storage medium according to an embodiment of the present invention. And
fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the invention.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
In order to solve the defects of the prior art, the invention provides an application publishing method, an application publishing device, a storage medium and electronic equipment based on a registry. According to an aspect of the present invention, an application publishing method based on a registry is provided, and fig. 1 is a flowchart of an application publishing method based on a registry in an embodiment of the present invention. As shown in fig. 1, the issuing method includes the following steps:
s110, the issuing system informs the server to start the application.
Specifically, the issuing system issues an online notification to the server, and the server starts the application in response to the online notification. In the present application, the publishing system and the server may be understood as a service provider providing a service to a service invoker as a whole, and the publishing system itself is a platform for a client to publish an application (service).
S130, when the application is in the first starting state, the issuing system informs the server to register the information of the application to the registration center.
Specifically, the issuing system issues a registration notification to the server when the application component has completed its startup except for components that need to be bootable after registration. The server registers information of the application with a registry based on the registration notification. The information of the application typically includes: name, type, function interface information, node address information including IP address and port number, and version information. The registration center supports database persistence and service clustering, and all clients in the clustering should see the same data and can not have read-write data inconsistency; when the data of the registry is changed, the client needs to be informed in time. The working principle is as follows: 1) when the service provider is started, registering the service provided by the service provider to a registration center according to the service release message configured in the release file; 2) when the consumer starts, the consumer subscribes the service required by the consumer to the registration center, and the consumer refreshes the local cache routing table of the consumer. 3) The registry returns the address list of the service provider to the consumer, if the address list is changed, the registry pushes the changed data to the consumer, and the consumer updates the local cache list of the consumer 4) the service caller selects one of the servers to provide service for the consumer based on the load balancing algorithm according to the obtained address list of the service provider. The registry needs peer-to-peer clustering, and the phenomenon that the cluster function of the registry cannot be used when one or more processes of the registry are down is avoided. For the client, no matter how many processes are configured by the registry cluster, the client only needs to be connected with one process. After the client is connected to the registry, operations such as adding (publishing or subscribing to new services) and deleting (deregistering published services) and changing (modifying published service attributes and performing dynamic service administration) data of the registry (inquiring service messages of the current system and subscribed customer messages) and the like need to be performed.
S150, when the application is in the second starting state, the issuing system sends a circulation flow notification to the server.
Specifically, after acquiring the notification that the application has completed registration, the server feeds back the notification that registration has been completed to the publishing system. The publishing system then checks the launch status of the application based on this loop and sends an http request to the server at intervals when the application is fully launched. Optionally, the time interval for the distribution system to send the circular traffic notification to the server is 1 s. Of course, the time for sending the circular flow rate notification may be set according to actual needs, and the present invention is not limited to this.
S170, the issuing system judges whether the application is normally started according to the request result received by the server in a preset time period based on the circulation flow notification. If the application is normal, the application is started, and if the application is abnormal, the off-line process is started. Therefore, the service providing end can know the running state of the application in the server in real time and realize lossless online.
Specifically, the server counts http requests from the publishing system received in a preset time period, and feeds back the number of the requests received in the time period to the publishing system. The issuing system judges whether the application is normally started or not based on the request quantity, if the request quantity reaches an expected value, the application is normally started, and the application is started until the application is started; and if the number of the requests does not reach an expected value, the application is considered to be abnormally started, so that the offline process is started.
Optionally, fig. 2 is a flowchart of a registry-based application publishing method in another embodiment of the present invention. As shown in fig. 2, in another embodiment of the present invention, the steps S110 and S130 further include:
and S120, after the issuing system obtains the notice that the application starts to be started and fed back by the server, circularly checking the starting state of the application.
Specifically, the server starts to start the application after receiving the online notification of the publishing system, and feeds back the information that the server knows the online notification to the publishing system, and the publishing system can determine that the server starts to start the application accordingly.
Further, with reference to fig. 2, steps S130 and S150 may further include:
s140, the issuing system circularly checks the starting state of the application after acquiring the notification of successful application registration fed back by the server.
Specifically, the registry starts to register the information of the application after acquiring the registration notification from the server so that the service caller consumes the service provided by the application, and feeds back the information that the registration of the relevant application is completed to the server after the registration of the information of the application is completed, and the server further feeds back the information to the publishing system. The publishing system then starts a loop checking the start-up status of the application.
In conclusion, according to the application publishing method based on the registry provided by the invention, the service provider can realize the lossless publishing of the application only by keeping the heartbeat with the registry, thereby avoiding the problem of abnormity generated in the publishing process of the application. In addition, the service provider does not need to keep heartbeat with the service caller, so that a large amount of heartbeat messages in the network are avoided, and resources can be effectively saved.
FIG. 3 is a diagram illustrating steps of a process of initiating a logoff according to an embodiment of the present invention. As shown in fig. 3, the step of starting the offline process includes:
s210, the issuing system informs the server to close the application.
Specifically, the issuing system issues an offline notification to the server, and the server starts to close the application in response to the offline notification.
S220, after the issuing system obtains the notice that the server starts to close the application, the issuing system informs the server to cancel the registration of the information of the application to the registration center.
Specifically, after acquiring a notification of canceling the registration of an application, the registry deletes the information of the application from the registration list, so that the service provider cannot conveniently call the service provided by the application.
S230, the release system circularly checks the closing state of the application after acquiring the notification that the registration center fed back by the server cancels the registration of the application;
specifically, after deleting the information of the application from the registry, the registry feeds back the information that the relevant application has been unregistered to the server, and the server further feeds back the information to the publishing system. The publishing system then begins a loop to check the shutdown status of other components in the application component.
S240, the issuing system circularly obtains the current flow value of the server after obtaining the notice that the application fed back by the server is completely closed. Optionally, the time interval for the distribution system to send the circular traffic notification to the server is 1 s. Of course, the time for sending the circular flow rate notification may be set according to actual needs, and the present invention is not limited to this.
And S250, when the release system does not obtain the current flow value of the server after exceeding the preset time, closing the application. Therefore, the service providing end can know the running state of the application in the server in real time, and lossless offline is realized. The preset time may be 5s, and may also be set according to actual needs, which is not limited in the present invention.
According to the application release method based on the registration center, the service provider can realize the lossless release of the application only by keeping the heartbeat with the registration center, and the problem that the application generates abnormity in the release process is avoided. In addition, the service provider does not need to keep heartbeat with the service caller, so that a large amount of heartbeat messages in the network are avoided, and resources can be effectively saved.
According to another aspect of the present invention, an application publishing system is provided, and fig. 4 is a schematic structural diagram of the publishing system in an embodiment of the present invention. As shown in fig. 4, the distribution system 321 includes: a first notification module 301, a second notification module 302, a third notification module 303, a first checking module 304, and a first determination module 305. The first notification module 301 is used to notify the server to start the application. The second notification module 302 is configured to notify the server to register information of the application with the registry when the application is in the first startup state. The third notification module 303 is configured to send a circulation flow notification to the server when the application is in the second start state. The first checking module 304 is used to check the starting state of the application in a loop. The first determining module 305 is configured to determine whether the application is normally started according to a request result received by the server within a preset time period. If the application is normal, the application is started, and if the application is abnormal, the off-line process is started. According to the application publishing system 310 provided by the invention, the service provider can realize the lossless publishing of the application only by keeping the heartbeat with the registration center, so that the problem of abnormity generated in the publishing process of the application is avoided.
Fig. 5 is a schematic structural diagram of a distribution system in another embodiment of the present invention. As shown in fig. 5, the publishing system 322 includes a first notifying module 301, a second notifying module 302, a third notifying module 303, a first checking module 304, a first determining module 305, a fourth notifying module 306, a fifth notifying module 307, a second checking module 308, an obtaining module 309, and a second determining module 310. The first notification module 301 is used to notify the server to start the application. The second notification module 302 is configured to notify the server to register information of the application with the registry when the application is in the first startup state. The third notification module 303 is configured to send a circulation flow notification to the server when the application is in the second start state. The first checking module 304 is used to check the starting state of the application in a loop. The first determining module 305 is configured to determine whether the application is normally started according to a request result received by the server within a preset time period. If the application is normal, the application is started, and if the application is abnormal, the off-line process is started. The fourth notification module 306 is used to notify the server to close the application. The fifth notification module 307 is used to notify the server to unregister the information of the application with the registry. The second checking module 308 is used to check the closing status of the application in a loop; the obtaining module 309 is used to cyclically obtain the current traffic value of the server. The second determining module 310 is used to determine whether the issuing system fails to obtain the current traffic value of the server after exceeding the preset time. According to the application release method based on the registration center, provided by the invention, when the release system operates, the service provider only needs to keep heartbeat with the registration center to realize the lossless release of the application, so that the problem of abnormity generated in the release process of the application is avoided. In addition, the service provider does not need to keep heartbeat with the service caller, so that a large amount of heartbeat messages in the network are avoided, and resources can be effectively saved.
It should be understood by those skilled in the art that the modules in the distribution system are respectively configured to perform the corresponding steps in the distribution method. The above only lists some modules of the issuing system, and according to the issuing method disclosed by the present invention, the issuing system may further include some other modules for assisting in executing relevant steps in the issuing method, and specifically, reference may be made to the relevant description of the foregoing issuing method section, and details of this will not be described here. In addition, fig. 4 and 5 are only schematic illustrations of the distribution system provided by the present invention, and the splitting, merging and adding of modules are within the protection scope of the present invention without departing from the concept of the present invention. The distribution system provided by the present invention can be implemented by software, hardware, firmware, plug-in and any combination thereof, and the present invention is not limited thereto.
Fig. 6 is a schematic structural diagram of a computer-readable storage medium according to an embodiment of the present invention. Fig. 6 depicts a program product 600 for implementing the registry-based application publication method described above, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may run on a terminal device, such as a personal computer, according to an embodiment of the present invention. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product 600 may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable storage medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable storage medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider). According to the application release method based on the registration center, the service provider can realize the lossless release of the application only by keeping the heartbeat with the registration center, and the problem that the application generates abnormity in the release process is avoided. In addition, the service provider does not need to keep heartbeat with the service caller, so that a large amount of heartbeat messages in the network are avoided, and resources can be effectively saved.
In an exemplary embodiment of the invention, there is also provided an electronic device that may include a processor and a memory for storing executable instructions of the processor. Wherein the processor is configured to perform the registry-based application publication method of the above embodiments via execution of the executable instructions.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.
An electronic device 400 according to this embodiment of the invention is described below with reference to fig. 7. The electronic device 400 shown in fig. 7 is only an example and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 7, electronic device 400 is embodied in the form of a general purpose computing device. The components of electronic device 400 may include, but are not limited to: at least one processing unit 410, at least one memory unit 420, a bus 430 that connects the various system components (including the memory unit 420 and the processing unit 410), a display unit 440, and the like.
Wherein the storage unit stores program code, which can be executed by the processing unit 410, so that the processing unit 410 executes the steps according to various exemplary embodiments of the present invention described in the above-mentioned registry-based application publishing method of the present specification. For example, the processing unit 410 may perform the steps as shown in fig. 1.
The storage unit 420 may include readable media in the form of volatile storage units, such as a random access memory unit (RAM)4201 and/or a cache memory unit 4202, and may further include a read only memory unit (ROM) 4203.
The storage unit 420 may also include a program/utility 4204 having a set (at least one) of program modules 4205, such program modules 4205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
The electronic device 400 may also communicate with one or more external devices 500 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 400, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 400 to communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interfaces 450. Also, the electronic device 400 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 460. The network adapter 460 may communicate with other modules of the electronic device 400 via the bus 430. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with electronic device 400, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiment of the present invention can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, or a network device, etc.) to execute the application issuing method based on the registry according to the present invention. The service provider can realize the lossless release of the application only by keeping the heartbeat with the registration center, and the problem that the application generates abnormity in the release process is avoided. In addition, the service provider does not need to keep heartbeat with the service caller, so that a large amount of heartbeat messages in the network are avoided, and resources can be effectively saved.
The foregoing is a more detailed description of the invention in connection with specific preferred embodiments and it is not intended that the invention be limited to these specific details. For those skilled in the art to which the invention pertains, several simple deductions or substitutions can be made without departing from the spirit of the invention, and all shall be considered as belonging to the protection scope of the invention.
Claims (10)
1. An application issuing method based on a registration center is characterized by comprising the following steps:
s110, the issuing system informs the server to start application;
s130, when the application is in a first starting state, the issuing system informs the server to register the information of the application to a registration center;
s150, when the application is in a second starting state, the issuing system sends a circulation flow notification to the server;
s170, the issuing system judges whether the application is normally started according to a request result received by the server in a preset time period based on the circulation flow notification; if the application is normal, the application is started, and if the application is abnormal, the off-line process is started.
2. The method for publishing application based on the registry as claimed in claim 1, wherein between steps S110 and S130 further comprising:
and S120, after the issuing system obtains the notice that the application starts to be started and fed back by the server, circularly checking the starting state of the application.
3. The method for publishing application based on the registry as claimed in claim 1, wherein the steps S130 and S150 further comprise:
s140, the issuing system circularly checks the starting state of the application after acquiring the notification of successful application registration fed back by the server.
4. The registry-based application publishing method according to claim 1, wherein the information of the application comprises: name, type, function interface information, node address information including IP address and port number, and version information.
5. The registry-based application distribution method according to claim 1, wherein in step S150, the time interval for sending the circular flow notification is 1S.
6. The registry-based application publishing method according to claim 1, wherein the step of initiating a logoff process comprises:
s210, the issuing system informs the server to close the application.
S220, after the issuing system obtains the notice that the server starts to close the application, the issuing system informs the server to cancel the registration of the information of the application to the registration center.
S230, the release system circularly checks the closing state of the application after acquiring the notification that the registration center fed back by the server cancels the registration of the application;
s240, the issuing system circularly obtains the current flow value of the server after obtaining the notice that the application fed back by the server is completely closed.
And S250, when the release system does not obtain the current flow value of the server after exceeding the preset time, closing the application.
7. A publication system for an application, comprising:
the first notification module is used for notifying the server to start the application;
the second notification module is used for notifying the server to register the information of the application to the registration center when the application is in the first starting state;
the third notification module is used for sending a circulation flow notification to the server when the application is in the second starting state;
the first checking module is used for circularly checking the starting state of the application;
the first judging module is used for judging whether the application is normally started according to a request result received by the server within a preset time period.
8. The publication system of claim 7, further comprising:
and the fourth notification module is used for notifying the server to close the application.
And the fifth notification module is used for notifying the server to cancel the registration of the information of the application to the registration center.
The second checking module is used for circularly checking the closing state of the application;
and the acquisition module is used for circularly acquiring the current flow value of the server.
And the second judgment module is used for judging whether the issuing system exceeds the preset time length and cannot acquire the current flow value of the server.
9. A storage medium, having stored thereon a computer program which, when executed by a processor, performs the steps of any of claims 1 to 7.
10. An electronic device, characterized in that the electronic device comprises:
a processor;
a storage medium having stored thereon a computer program which, when executed by the processor, performs the steps of any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010019387.0A CN111240760B (en) | 2020-01-08 | 2020-01-08 | Application publishing method, system, storage medium and equipment based on registry |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010019387.0A CN111240760B (en) | 2020-01-08 | 2020-01-08 | Application publishing method, system, storage medium and equipment based on registry |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111240760A true CN111240760A (en) | 2020-06-05 |
| CN111240760B CN111240760B (en) | 2022-09-16 |
Family
ID=70870287
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010019387.0A Active CN111240760B (en) | 2020-01-08 | 2020-01-08 | Application publishing method, system, storage medium and equipment based on registry |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111240760B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113986316A (en) * | 2021-12-27 | 2022-01-28 | 北京结慧科技有限公司 | Automatic deployment method of micro-service |
| CN117155994A (en) * | 2023-10-27 | 2023-12-01 | 广州市千钧网络科技有限公司 | Service registration management method, device, equipment and readable storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108134766A (en) * | 2016-12-01 | 2018-06-08 | 阿里巴巴集团控股有限公司 | A kind of method, apparatus, system, server and client for servicing publication |
| CN108287764A (en) * | 2018-01-31 | 2018-07-17 | 上海携程商务有限公司 | Distributed task dispatching method and its system, storage medium, electronic equipment |
| CN110120961A (en) * | 2018-02-06 | 2019-08-13 | 北京京东尚科信息技术有限公司 | A kind of method of Distributed Services cluster and its route synchronization |
-
2020
- 2020-01-08 CN CN202010019387.0A patent/CN111240760B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108134766A (en) * | 2016-12-01 | 2018-06-08 | 阿里巴巴集团控股有限公司 | A kind of method, apparatus, system, server and client for servicing publication |
| CN108287764A (en) * | 2018-01-31 | 2018-07-17 | 上海携程商务有限公司 | Distributed task dispatching method and its system, storage medium, electronic equipment |
| CN110120961A (en) * | 2018-02-06 | 2019-08-13 | 北京京东尚科信息技术有限公司 | A kind of method of Distributed Services cluster and its route synchronization |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113986316A (en) * | 2021-12-27 | 2022-01-28 | 北京结慧科技有限公司 | Automatic deployment method of micro-service |
| CN117155994A (en) * | 2023-10-27 | 2023-12-01 | 广州市千钧网络科技有限公司 | Service registration management method, device, equipment and readable storage medium |
| CN117155994B (en) * | 2023-10-27 | 2024-02-02 | 广州市千钧网络科技有限公司 | Service registration management method, device, equipment and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111240760B (en) | 2022-09-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108737270B (en) | Resource management method and device for server cluster | |
| US11586697B2 (en) | Publishing rest API changes based on subscriber's customized request | |
| US8938510B2 (en) | On-demand mailbox synchronization and migration system | |
| US9253265B2 (en) | Hot pluggable extensions for access management system | |
| US20160150046A1 (en) | Re-establishing push notification channels via user identifiers | |
| CN110580305B (en) | Method, apparatus, system and medium for generating identifier | |
| CN111510330B (en) | Interface management device, method and storage medium | |
| CN111240760B (en) | Application publishing method, system, storage medium and equipment based on registry | |
| CN113220433B (en) | Agent program operation management method and system | |
| CN111324361A (en) | Application upgrading method and device | |
| US9026839B2 (en) | Client based high availability method for message delivery | |
| CN112433863A (en) | Micro-service calling method and device, terminal equipment and storage medium | |
| CN110730197B (en) | Service discovery method and system | |
| CN110275701B (en) | Data processing method, device, medium and computing equipment | |
| EP3721604B1 (en) | Automatic subscription management of computing services | |
| US9288178B2 (en) | Inventory updating of an internet protocol (IP) alias within a highly available computing cluster | |
| CN113535439B (en) | Service request processing method, device, equipment and storage medium | |
| CN114968636A (en) | Fault processing method and device | |
| US20220276901A1 (en) | Batch processing management | |
| CN114449040A (en) | Configuration issuing method and device based on cloud platform | |
| CN113542319A (en) | Service providing entity change notification method, device and system used in Dubbo framework | |
| CN112749042B (en) | Application running method and device | |
| US11314448B2 (en) | Registering storage hosts for use in automating software-defined storage deployments | |
| CN114827245A (en) | Equipment adding method, device, equipment and machine-readable storage medium | |
| US10951473B1 (en) | Asynchronous fleet configuration service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| EE01 | Entry into force of recordation of patent licensing contract |
Application publication date: 20200605 Assignee: Nanjing Manyun Cold Chain Technology Co.,Ltd. Assignor: JIANGSU MANYUN SOFTWARE TECHNOLOGY Co.,Ltd. Contract record no.: X2023980038397 Denomination of invention: Application publishing methods, systems, storage media, and devices based on registration centers Granted publication date: 20220916 License type: Common License Record date: 20230724 |
|
| EE01 | Entry into force of recordation of patent licensing contract |