CN113687841A - Hazelcast-based system deployment method and related equipment - Google Patents
Hazelcast-based system deployment method and related equipment Download PDFInfo
- Publication number
- CN113687841A CN113687841A CN202111062349.4A CN202111062349A CN113687841A CN 113687841 A CN113687841 A CN 113687841A CN 202111062349 A CN202111062349 A CN 202111062349A CN 113687841 A CN113687841 A CN 113687841A
- Authority
- CN
- China
- Prior art keywords
- hazelcast
- message queue
- based system
- system deployment
- cache
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a Hazelcast-based system deployment method and related equipment, the Hazelcast is embedded and integrated into an application system by utilizing the message queue and cache functions of the Hazelcast, so that the simultaneous deployment of the application system function, the distributed cache function and the message queue function can be realized when the application system is deployed, the deployment efficiency is improved, and the technical problems that the system depends on external components such as a database, a cache, a message queue and the like, the external components need to be installed and debugged independently in each deployment, the workload of operation and maintenance is increased, the difficulty of system deployment is improved, and the system deployment efficiency is reduced are solved.
Description
Technical Field
The application relates to the technical field of system deployment, in particular to system deployment based on Hazelcast and related equipment.
Background
In an enterprise providing system services for an industry, the system services are often required to be deployed on a server of a demand side for local deployment.
The system depends on external components such as a database, a cache, a message queue and the like, and the external components need to be independently installed and debugged in each deployment, so that the technical problems of increasing the workload of operation and maintenance implementation, improving the difficulty of system deployment and reducing the efficiency of system deployment exist.
Disclosure of Invention
The application provides a system deployment method and related equipment based on Hazelcast, and solves the technical problems that because the system depends on external components such as a database, a cache, a message queue and the like, the external components need to be independently installed and debugged in each deployment, the workload of operation and maintenance implementation is increased, the difficulty of system deployment is improved, and the efficiency of system deployment is reduced.
In view of the above, the present application provides, in a first aspect, a method for deploying a Hazelcast-based system, the method including:
declaring in Hazelcast the name of a Hazelcast message queue and the name of a Hazelcast cache;
embedding the Hazelcast into a dependency package of an application system;
and starting an installation program of the application system, so that the Hazelcast completes the loading of the Hazelcast message queue and the Hazelcast cache in the memory.
Optionally, the embedding the Hazelcast into the dependency package of the application system specifically includes:
embedding the Hazelcast into a pom file of an application system through engineering management software maven;
the Hazelcast was declared a dependency in the pom file.
Optionally, after the starting the installation program of the application system, the method further includes:
and monitoring the Hazelcast message queue for the Hazelcast message queue starting thread.
Optionally, if names of two or more Hazelcast message queues are declared in the Hazelcast, starting a thread for listening to the Hazelcast message queues for the two or more Hazelcast message queues, respectively.
A second aspect of the present application provides a Hazelcast-based system deployment apparatus, the apparatus comprising:
a declaring unit for declaring in Hazelcast the name of a Hazelcast message queue and the name of a Hazelcast cache;
the embedding unit is used for embedding the Hazelcast into a dependency package of an application system;
and the starting unit is used for starting the installation program of the application system so that the Hazelcast completes the loading of the Hazelcast message queue and the Hazelcast cache in the memory.
Optionally, the embedding unit is specifically configured to:
embedding the Hazelcast into a pom file of an application system through engineering management software maven;
the Hazelcast was declared a dependency in the pom file.
Optionally, the method further comprises:
and the monitoring unit is used for starting a thread for the Hazelcast message queue to monitor the Hazelcast message queue.
Optionally, if names of two or more Hazelcast message queues are declared in the Hazelcast, the monitoring unit starts a thread for the two or more Hazelcast message queues to monitor the Hazelcast message queues respectively.
A third aspect of the present application provides a Hazelcast-based system deployment apparatus, the apparatus comprising a processor and a memory:
the memory is used for storing program codes and transmitting the program codes to the processor;
the processor is configured to perform the steps of the method for Hazelcast-based system deployment according to the first aspect as described above, according to instructions in the program code.
A fourth aspect of the present application provides a computer-readable storage medium for storing program code for executing the method for Hazelcast-based system deployment of the first aspect.
According to the technical scheme, the embodiment of the application has the following advantages:
the application provides a system deployment method and related equipment based on Hazelcast, the Hazelcast is embedded and integrated into an application system by utilizing the message queue and cache functions of the Hazelcast, so that the application system functions, the distributed cache functions and the message queue functions can be deployed simultaneously when the application system is deployed, the deployment efficiency is improved, and the technical problems that the system depends on external components such as a database, a cache, a message queue and the like, the external components need to be installed and debugged independently during each deployment, the workload of operation and maintenance is increased, the system deployment difficulty is improved, and the system deployment efficiency is reduced are solved.
Drawings
FIG. 1 is a flow chart of a method for Hazelcast-based system deployment in an embodiment of the present application;
FIG. 2 is a schematic structural diagram of a Hazelcast-based system deployment device in an embodiment of the present application;
fig. 3 is a schematic structural diagram of a system deployment module based on Hazelcast in an embodiment of the present application.
Detailed Description
In order to make the technical solutions of the present application better understood, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The application designs a system deployment method and related equipment based on Hazelcast, and solves the technical problems that because the system depends on external components such as a database, a cache, a message queue and the like, the external components need to be independently installed and debugged in each deployment, the workload of operation and maintenance implementation is increased, the difficulty of system deployment is improved, and the efficiency of system deployment is reduced.
For ease of understanding, referring to fig. 1, fig. 1 is a flowchart of a method for deploying a system based on Hazelcast according to an embodiment of the present application, as shown in fig. 1, specifically:
101. declaring in Hazelcast the name of a Hazelcast message queue and the name of a Hazelcast cache;
it should be noted that Hazelcast has its own Hazelcast message queue and Hazelcast cache, and its Hazelcast cache is a distributed cache, and it is stated in Hazelcast that the names of the Hazelcast message queue and the Hazelcast cache can use these two functions of Hazelcast.
102. Embedding Hazelcast into a dependency package of an application system;
it should be noted that Hazelcast can be embedded into the dependent package of the application system, i.e. integrated with the application system, and does not need to be separately installed and debugged.
103. And starting an installation program of the application system, so that the Hazelcast completes the loading of the Hazelcast message queue and the Hazelcast cache in the memory.
It should be noted that, in the installation phase, the installer of the application system is started, and besides the installation of the body function of the application system is completed, the Hazelcast will complete the loading of the Hazelcast message queue and the Hazelcast cache in the memory by itself,
further, embedding the Hazelcast into the dependency package of the application system specifically includes:
embedding Hazelcast into a pom file of an application system through engineering management software maven;
hazelcast was declared a dependency in the pom file.
It should be noted that the pom file is a declaration file in the engineering management software maven, the source code of the Hazelcast is embedded in the pom file of the application system, and the dependency of the Hazelcast is declared in the pom file, so that the dependency of the Hazelcast can be directly used when the application program runs.
Further, after the starting of the installation program of the application system, the method further comprises:
and carrying out listening on the Hazelcast message queue for the Hazelcast message queue starting thread.
It should be noted that, when the application system is started, the thread is started for the Hazelcast message queue to monitor, and the messages in the Hazelcast message queue are monitored and consumed.
Further, if names of two or more Hazelcast message queues are declared in the Hazelcast, one thread is started for the two or more Hazelcast message queues to monitor the Hazelcast message queues respectively.
It should be noted that, in Hazelcast, names of two or more Hazelcast message queues may be declared, that is, two or more Hazelcast message queues are enabled, and in the stage of application system startup, a thread is started up for each queue defined in the Hazelcast message queue to listen and consume respectively.
Fig. 2 is a schematic structural diagram of a system deployment device based on Hazelcast in an embodiment of the present application, as shown in fig. 2, specifically including:
declaring unit 201, configured to declare, in Hazelcast, a name of a Hazelcast message queue and a name of a Hazelcast cache;
an embedding unit 202, configured to embed Hazelcast into a dependency package of an application system;
the starting unit 203 is configured to start an installer of the application system, so that the Hazelcast completes loading of the Hazelcast message queue and the Hazelcast cache in the memory.
Further, the embedding unit 202 is specifically configured to:
embedding Hazelcast into a pom file of an application system through engineering management software maven;
hazelcast was declared a dependency in the pom file.
Further, still include:
and the monitoring unit 204 is configured to monitor the Hazelcast message queue for the Hazelcast message queue start thread.
Further, if names of two or more Hazelcast message queues are declared in the Hazelcast, the monitoring unit starts a thread for the two or more Hazelcast message queues to monitor the Hazelcast message queues respectively.
The application provides a system deployment method and related equipment based on Hazelcast, the Hazelcast is embedded and integrated into an application system by utilizing the message queue and cache functions of the Hazelcast, so that the application system functions, the distributed cache functions and the message queue functions can be deployed simultaneously when the application system is deployed, the deployment efficiency is improved, and the technical problems that the system depends on external components such as a database, a cache, a message queue and the like, the external components need to be installed and debugged independently during each deployment, the workload of operation and maintenance is increased, the system deployment difficulty is improved, and the system deployment efficiency is reduced are solved.
Fig. 3 is a schematic structural diagram of a Hazelcast-based system deployment module 900, which may have a relatively large difference due to different configurations or performances, according to an embodiment of the present application, and may include one or more Central Processing Units (CPUs) 922 (e.g., one or more processors) and a memory 932, and one or more storage media 930 (e.g., one or more mass storage devices) storing an application 942 or data 944. Memory 932 and storage media 930 can be, among other things, transient storage or persistent storage. The program stored on the storage medium 930 may include one or more modules (not shown), each of which may include a series of instruction operations for the server. Still further, central processor 922 may be configured to communicate with storage medium 930 to execute a series of instruction operations in storage medium 930 on Hazelcast-based system deployment module 900.
Hazelcast-based system deployment module 900 may also include one or more power supplies 926, one or more wired or wireless network interfaces 950, one or more input-output interfaces 958, and/or one or more operating systems 941, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
The steps performed by the server in the above embodiments may be based on the server structure shown in fig. 3.
The CPU 922 is configured to execute the following steps:
declaring in Hazelcast the name of a Hazelcast message queue and the name of a Hazelcast cache;
embedding Hazelcast into a dependency package of an application system;
and starting an installation program of the application system, so that the Hazelcast completes the loading of the Hazelcast message queue and the Hazelcast cache in the memory.
The embodiment of the application also provides another Hazelcast-based system deployment device, which comprises a processor and a memory, wherein the processor comprises:
the memory is used for storing the program codes and transmitting the program codes to the processor;
the processor is used for executing any one of the implementation modes of the Hazelcast-based system deployment method of the previous embodiments according to instructions in the program code.
The present application further provides a computer-readable storage medium for storing a program code for executing any implementation of a Hazelcast-based system deployment method described in the foregoing embodiments.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
The terms "first," "second," "third," "fourth," and the like in the description of the application and the above-described figures, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
It should be understood that in the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" for describing an association relationship of associated objects, indicating that there may be three relationships, e.g., "a and/or B" may indicate: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of single item(s) or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.
Claims (10)
1. A Hazelcast-based system deployment method, comprising:
declaring in Hazelcast the name of a Hazelcast message queue and the name of a Hazelcast cache;
embedding the Hazelcast into a dependency package of an application system;
and starting an installation program of the application system, so that the Hazelcast completes the loading of the Hazelcast message queue and the Hazelcast cache in the memory.
2. The Hazelcast-based system deployment method as claimed in claim 1, wherein the embedding the Hazelcast into the application dependent package specifically comprises:
embedding the Hazelcast into a pom file of an application system through engineering management software maven;
the Hazelcast was declared a dependency in the pom file.
3. The Hazelcast-based system deployment method as claimed in claim 1, wherein the initiating the installer of the application system further comprises:
and monitoring the Hazelcast message queue for the Hazelcast message queue starting thread.
4. The Hazelcast-based system deployment method of claim 3 wherein if two or more Hazelcast message queues are declared as being named in the Hazelcast, then initiating a thread for two or more of the Hazelcast message queues to listen for the Hazelcast message queues, respectively.
5. A Hazelcast-based system deployment device, comprising:
a declaring unit for declaring in Hazelcast the name of a Hazelcast message queue and the name of a Hazelcast cache;
the embedding unit is used for embedding the Hazelcast into a dependency package of an application system;
and the starting unit is used for starting the installation program of the application system so that the Hazelcast completes the loading of the Hazelcast message queue and the Hazelcast cache in the memory.
6. The Hazelcast-based system deployment device of claim 5 wherein the embedding unit is specifically configured to:
embedding the Hazelcast into a pom file of an application system through engineering management software maven;
the Hazelcast was declared a dependency in the pom file.
7. The Hazelcast-based system deployment device of claim 5, further comprising:
and the monitoring unit is used for starting a thread for the Hazelcast message queue to monitor the Hazelcast message queue.
8. The Hazelcast-based system deployment device of claim 7, wherein if two or more Hazelcast message queues are declared in the Hazelcast, the listening unit starts one thread for the two or more Hazelcast message queues respectively for listening.
9. A Hazelcast-based system deployment device, the device comprising a processor and a memory:
the memory is used for storing program codes and transmitting the program codes to the processor;
the processor is configured to execute the method for Hazelcast-based system deployment of any of claims 1-4 according to instructions in the program code.
10. A computer-readable storage medium for storing program code for performing the method for Hazelcast-based system deployment of any of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111062349.4A CN113687841A (en) | 2021-09-10 | 2021-09-10 | Hazelcast-based system deployment method and related equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111062349.4A CN113687841A (en) | 2021-09-10 | 2021-09-10 | Hazelcast-based system deployment method and related equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113687841A true CN113687841A (en) | 2021-11-23 |
Family
ID=78586050
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111062349.4A Pending CN113687841A (en) | 2021-09-10 | 2021-09-10 | Hazelcast-based system deployment method and related equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113687841A (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20200409669A1 (en) * | 2019-06-26 | 2020-12-31 | Sap Se | Technique for transforming a standard messaging component to a customized component |
-
2021
- 2021-09-10 CN CN202111062349.4A patent/CN113687841A/en active Pending
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20200409669A1 (en) * | 2019-06-26 | 2020-12-31 | Sap Se | Technique for transforming a standard messaging component to a customized component |
Non-Patent Citations (1)
| Title |
|---|
| 随风溜达的向日葵: "Hazelcast集群服务(1)——Hazelcast介绍", pages 1 - 10, Retrieved from the Internet <URL:https://cloud.tencent.co, /developer/article/1185863> * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112416415A (en) | Front-end micro-service implementation method and related components | |
| CN107016480B (en) | Task scheduling method, device and system | |
| CN113422692A (en) | Method, device and storage medium for detecting and processing node faults in K8s cluster | |
| CN110858158B (en) | Distributed task scheduling method and device, electronic equipment and storage medium | |
| CN113051134B (en) | Application system monitoring management method, device, equipment and storage medium | |
| CN107678782B (en) | Process protection method, device, equipment and computer readable storage medium | |
| US20110197193A1 (en) | Device and method for controlling communication between bios and bmc | |
| CN112463561B (en) | Fault positioning method, device, equipment and storage medium | |
| CN108809683B (en) | Method and device for deploying cloud application system | |
| CN112486502B (en) | Distributed task deployment method, distributed task deployment device, computer equipment and storage medium | |
| CN114328098A (en) | Slow node detection method and device, electronic equipment and storage medium | |
| CN111176806A (en) | Service processing method, device and computer readable storage medium | |
| CN111506430A (en) | Method and device for data processing under multitasking and electronic equipment | |
| CN102420709A (en) | Task scheduling management method and device based on task framework | |
| CN113157569A (en) | Automatic testing method and device, computer equipment and storage medium | |
| CN110874263B (en) | Method and device for monitoring instances of docker container | |
| CN113656239A (en) | Monitoring method and device for middleware and computer program product | |
| CN115080199A (en) | Task scheduling method, system, device, storage medium and program product | |
| CN112988422A (en) | Asynchronous message processing method and device, electronic equipment and storage medium | |
| CN113687841A (en) | Hazelcast-based system deployment method and related equipment | |
| CN114327673B (en) | Task starting method and device, electronic equipment and storage medium | |
| CN105787359A (en) | Course guarding method and device | |
| JP2018538632A (en) | Method and device for processing data after node restart | |
| CN114691241B (en) | Task execution method, device, electronic equipment and storage medium | |
| CN117149413A (en) | Cloud service integrated deployment system and method for universal AI algorithm model |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20211123 |