CN114185644A - Container-based multi-application integrated deployment method and device and computer equipment - Google Patents
Container-based multi-application integrated deployment method and device and computer equipment Download PDFInfo
- Publication number
- CN114185644A CN114185644A CN202111501477.4A CN202111501477A CN114185644A CN 114185644 A CN114185644 A CN 114185644A CN 202111501477 A CN202111501477 A CN 202111501477A CN 114185644 A CN114185644 A CN 114185644A
- Authority
- CN
- China
- Prior art keywords
- application
- container
- applications
- function
- package
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 102
- 238000004590 computer program Methods 0.000 claims abstract description 41
- 230000006870 function Effects 0.000 claims description 197
- 238000004891 communication Methods 0.000 claims description 39
- 230000004044 response Effects 0.000 claims description 30
- 238000001514 detection method Methods 0.000 claims description 11
- 238000012545 processing Methods 0.000 claims description 9
- 230000010354 integration Effects 0.000 claims description 2
- 230000003993 interaction Effects 0.000 abstract description 48
- 230000008569 process Effects 0.000 description 17
- 238000010586 diagram Methods 0.000 description 5
- 238000002955 isolation Methods 0.000 description 4
- 238000013500 data storage Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
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/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- 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/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application relates to a container-based multi-application integrated deployment method, a container-based multi-application integrated deployment apparatus, a computer device, a storage medium, and a computer program product. The method comprises the following steps: acquiring at least one application to be deployed, and merging and deploying the application to be deployed into the same directory in the same container; classifying the types of the applications in the container into a function package and a tool package; the function package is a package which can be called by all applications in the container; the toolkit is a kit used only in the current application; respectively setting the function packages of the applications in the container, so that the function packages can be called by all the applications in the container; the tool packages of all applications in the container are respectively set, so that the tool packages are only used in the current application to which the tool packages belong. By adopting the method, hardware resources of the computer can be saved, original network interaction can be replaced by in-process interaction, and interaction efficiency and interaction stability among applications are improved.
Description
Technical Field
The present application relates to the field of internet design technologies, and in particular, to a container-based multi-application integrated deployment method, apparatus, computer device, storage medium, and computer program product.
Background
With the development of enterprise business, various applications supporting the operation of the internal business of the enterprise will be more and more, and when one application is added, corresponding operations and maintenance personnel are required to be correspondingly added for supporting the deployment, online and other processes of the application, and corresponding computer resources are also required to be provided for the enterprise.
In addition, because each application is independently deployed, the applications are interacted mainly through network requests, if a network is congested, the network requests are delayed, so that network jitter occurs, network interaction between the applications is abnormal, and normal service development can be influenced when the network interaction is serious.
Therefore, the existing application deployment has the problem of poor interaction performance among applications.
Disclosure of Invention
In view of the foregoing, there is a need to provide a container-based multi-application integrated deployment method, apparatus, computer device, computer-readable storage medium and computer program product capable of improving performance interaction between applications.
In a first aspect, the application provides a container-based multi-application integrated deployment method. The method comprises the following steps:
acquiring at least one application to be deployed, and merging and deploying the application to be deployed into the same directory in the same container;
classifying the types of the applications in the container into a function package and a tool package; the function package is a package which can be called by all applications in the container; the toolkit is a kit used only in the current application;
respectively setting the function packages of the applications in the container, so that the function packages can be called by all the applications in the container;
the tool packages of all applications in the container are respectively set, so that the tool packages are only used in the current application to which the tool packages belong.
In one embodiment, the classifying the classes of the applications in the container into a function package and a tool package includes:
acquiring the class of each application in the container;
and classifying the classes into a function package and a tool package according to a preset classification rule.
In one embodiment, the respectively setting the function packages of the applications in the container includes:
storing function identifiers of the corresponding services of the applications in the container;
setting the parent container of the function package of each application as a container, and simultaneously setting the child container of the function package of each application as all the applications in the container.
In one embodiment, the setting the tool pack of each application in the container respectively includes:
setting the dependency range of the tool pack in each application, and setting the dependency range of the tool pack in each application as the inside of the application to which the current tool pack belongs.
In one embodiment, the container-based multi-application integrated deployment method further includes:
when a first application in a container needs to call a function package except for an application function package in the container, detecting whether the function package which needs to be called by the first application exists in the container;
and if so, the first application calls the function packet which needs to be called by the first application based on the in-process communication request to acquire response data.
In one embodiment, the first application calls a function package that the first application needs to call based on an in-process communication request, and acquiring response data includes:
acquiring a second application to which a function package required to be called by the first application belongs through detection;
sending an in-process communication request to the second application; the in-process communication request comprises an identifier of the first application, a function identifier of a function packet required to be called by the first application and request parameters;
receiving response data sent by the second application; the response data is generated by the second application processing the in-process communication request.
In a second aspect, the application further provides a container-based multi-application integrated deployment apparatus. The device comprises:
the system comprises an acquisition module, a storage module and a deployment module, wherein the acquisition module is used for acquiring at least one application to be deployed and merging and deploying the application to be deployed into the same catalog in the same container;
the classification module is used for classifying the types of the applications in the container into a function package and a tool package; the function package is a package which can be called by all applications in the container; the toolkit is a kit used only in the current application;
the first setting module is used for respectively setting the function packages of the applications in the container, so that the function packages can be called by all the applications in the container;
and the second setting module is used for respectively setting the tool packages of the applications in the container, so that the tool packages are only used in the current application to which the tool packages belong.
In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor implementing the following steps when executing the computer program:
acquiring at least one application to be deployed, and merging and deploying the application to be deployed into the same directory in the same container;
classifying the types of the applications in the container into a function package and a tool package; the function package is a package which can be called by all applications in the container; the toolkit is a kit used only in the current application;
respectively setting the function packages of the applications in the container, so that the function packages can be called by all the applications in the container;
the tool packages of all applications in the container are respectively set, so that the tool packages are only used in the current application to which the tool packages belong.
In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of:
acquiring at least one application to be deployed, and merging and deploying the application to be deployed into the same directory in the same container;
classifying the types of the applications in the container into a function package and a tool package; the function package is a package which can be called by all applications in the container; the toolkit is a kit used only in the current application;
respectively setting the function packages of the applications in the container, so that the function packages can be called by all the applications in the container;
the tool packages of all applications in the container are respectively set, so that the tool packages are only used in the current application to which the tool packages belong.
In a fifth aspect, the present application further provides a computer program product. The computer program product comprising a computer program which when executed by a processor performs the steps of:
acquiring at least one application to be deployed, and merging and deploying the application to be deployed into the same directory in the same container;
classifying the types of the applications in the container into a function package and a tool package; the function package is a package which can be called by all applications in the container; the toolkit is a kit used only in the current application;
respectively setting the function packages of the applications in the container, so that the function packages can be called by all the applications in the container;
the tool packages of all applications in the container are respectively set, so that the tool packages are only used in the current application to which the tool packages belong.
The container-based multi-application integrated deployment method, the device, the computer equipment, the storage medium and the computer program product obtain at least one application to be deployed, merge and deploy the application to be deployed into the same directory in the same container, divide the types of the applications in the container into a function package and a tool package, the function packages of the applications in the container are respectively set, so that the function packages can be called by all the applications in the container, the tool packages of all the applications in the container are respectively set, so that the tool packages are only used in the current application to which the tool packages belong, by deploying a plurality of applications in the same container, hardware resources of the computer are saved, and the plurality of applications deployed in one container belong to the same process, original network interaction can be replaced by in-process interaction, and interaction efficiency and interaction stability among applications are improved.
Drawings
FIG. 1 is a diagram of an application environment for a container-based multi-application integrated deployment method in one embodiment;
FIG. 2 is a flowchart illustrating a method for container-based multi-application integrated deployment in one embodiment;
FIG. 3 is an architectural diagram illustrating the deployment of multiple applications within a container in one embodiment;
FIG. 4 is a block diagram of a container-based multi-application integrated deployment apparatus in one embodiment;
FIG. 5 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The container-based multi-application integrated deployment method provided by the embodiment of the application can be applied to the application environment shown in fig. 1. Wherein the terminal 102 communicates with the server 104 via a network. The data storage system may store data that the server 104 needs to process. The data storage system may be integrated on the server 104, or may be located on the cloud or other network server.
The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices and portable wearable devices, and the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart car-mounted devices, and the like. The portable wearable device can be a smart watch, a smart bracelet, a head-mounted device, and the like. The server 104 may be implemented as a stand-alone server or as a server cluster comprised of multiple servers.
In one embodiment, as shown in fig. 2, a container-based multi-application integrated deployment method is provided, which is described by taking the method as an example applied to the server in fig. 1, and includes the following steps:
step 202, at least one application to be deployed is obtained, and the applications to be deployed are merged and deployed into the same directory in the same container.
The container is an environment for supporting the running of programming language codes, is used for loading a deployment module without a starting method, and supports the running of the codes.
Specifically, the applications to be deployed are applications to be deployed, and are generally applications with tighter business dependence, and when the applications to be deployed are deployed, the applications to be deployed with tighter business dependence are placed in the same directory of the same container.
Step 204, classifying the types of the applications in the container into a function package and a tool package; the function package is a package which can be called by all applications in the container; the toolkit is a kit used only in the current application.
In particular, a Class (Class) is a collection of entities that have some common characteristics. Class loaders (classloaders) are tools used to load classes, and classes of containers and classes of applications are isolated during the loading process. The method comprises the steps of dividing the application classes deployed in a container into function packages and tool packages according to preset classification rules, enabling the function packages Shared by all the applications to be loaded by a Shared Classloader (parent loader), and enabling each application to have an independent Module Classloader (child loader) to be responsible for loading tool packages unique to the application. By means of the parent-child loader mode, the function class is loaded and used together, and each application independent tool class is isolated.
And step 206, respectively setting the function packages of the applications in the container, so that the function packages can be called by all the applications in the container.
Specifically, the function packages of the applications in the container are respectively set, so that the function packages can be called by all applications in the container, and when a new application (for example, a B application) is detected by the container, the function identifier of a service (function package) corresponding to the application is stored. And for the function package, setting the corresponding father module as a container, and setting the sub-modules as all applications, so that the function package is loaded by the father module and all the sub-modules are shared.
And step 208, respectively setting the tool packages of the applications in the container, so that the tool packages are only used in the current application to which the tool packages belong.
Specifically, the tool packages of the applications in the container are respectively set, so that the tool packages are only used in the current application to which the tool packages belong, and the tool packages set the dependency range as the interior of the application, so that when the application is started, the resource dependency range of the corresponding tool package is the interior of the application, and when the application calls the corresponding tool package or data, the tool packages are obtained in the resource dependency range. When an application (for example, an application A) obtains and uses a certain function, the application carries a function name to be used, a container detects whether a function corresponding to a function packet exists, if the application corresponding to the function identifier is detected to be an application B, an in-process communication request is sent, and the identifier of the application A, a required function identifier and a request parameter are carried in the request, so that the application B processes according to the communication request to obtain response data.
In the embodiment, a plurality of applications are deployed to the same process in the same common container, and the applications are isolated from each other, but the information of the common container can be read, and in-process communication can be performed, so that the purpose of integrated deployment of the plurality of applications is achieved.
The multiple application deployment loading scheme is shown in fig. 3, where applications in a container are isolated from each other, but may be configured to communicate with each other, or may issue applications outside the container for external invocation, and as shown in fig. 3, the applications in the container are isolated from each other by the following layers:
1. context isolation. Context in programming terms is the larger peripheral portion that has any effect on the behavior of the current unit of work. Such as the operating environment used, environment variables, instance variables, local variables, the state of other classes, the state of the current environment, and so forth. There are 1 context per application within a container, and the context of a common container is the parent context of all applications. The contexts of the common container are application-shared, while the contexts of each application are isolated from each other.
2. Class isolation. The class of the container and the class of the application are isolated in the loading process, and the function package Shared by all the applications is loaded by a Shared Classloader (parent loader). Each application has a separate Module class loader (child loader) responsible for loading toolkits unique to the application. By means of the parent-child loader mode, the function class is loaded and used together, and each application independent tool class is isolated.
3. And (5) isolating the threads. A process is a running activity of a program in a computer on a data set, is a basic unit for resource allocation and scheduling of a system, and is the basis of an operating system structure. A thread refers to one execution flow in a process, and multiple threads may run in one process. Most threads of each application within the container are isolated from each other, but there may also be some common thread pool.
Interaction can be performed between applications within the container. On the basis of ensuring that the applications cannot interfere with each other by isolation, the applications in the container are required to be ensured to be interacted, otherwise, the container is limited to use. The application can provide services for other applications only by adding some configurations, the calling among the services belongs to in-process calling, network interaction is completely not relied on, and the stability of the interaction among the applications is ensured as far as possible.
Applications inside the container can be published outside the container. The interaction between the application in the container and the application outside the container needs to be realized through a registry. The specific method is described as follows: applications of the service provider: the rpc importing the container relies on the package, configuring the service provider in a file and annotating to expose the service out of the container and registering with the registry. Application of service consumer: rpc, which also introduces containers, rely on packages to configure service consumers in files and consume services with annotated methods. And the container also provides one-click configuration, so that a developer can select whether the applied service is exposed locally or remotely, and the operation of the developer is simplified.
In the container-based multi-application integrated deployment method, at least one application to be deployed is obtained, the applications to be deployed are merged and deployed into the same directory in the same container, the classes of the applications in the container are divided into the function packages and the tool packages, the function packages of the applications in the container are respectively set, the function packages can be called by all the applications in the container, the tool packages of the applications in the container are respectively set, the tool packages are only used in the current application to which the tool packages belong, hardware resources of a computer are saved by deploying the applications in the same container, the applications deployed in the container belong to the same process, original network interaction can be replaced by in-process interaction, and interaction efficiency and interaction stability among the applications are improved.
In one embodiment, the classifying the classes of the applications in the container into a function package and a tool package includes:
acquiring the class of each application in the container;
and classifying the classes into a function package and a tool package according to a preset classification rule.
Specifically, when the classes of the applications in the container are classified into the function package and the tool package, the classes of the applications in the container are first obtained, and then the classes are classified according to a preset classification rule, generally, the types of the applications are determined and classified according to a naming rule or a purpose of the function package or the tool package, so that the classes of the applications in the container are classified.
In the embodiment, the classes of the applications in the container are obtained, and the classes are divided into the function package and the tool package according to the preset classification rule, so that the isolation and the normal interaction between different applications are realized, and the interaction efficiency and the interaction stability between the applications are improved.
In an embodiment, the respectively setting the function packages of the applications in the container includes:
storing function identifiers of the corresponding services of the applications in the container;
setting the parent container of the function package of each application as a container, and simultaneously setting the child container of the function package of each application as all the applications in the container.
Specifically, when setting the function package of each application in the container, first, the function identifier of the service corresponding to each application in the container is stored, the function identifier is used for interaction among applications in the container, the parent container of the function package of each application is set as the container, and meanwhile, the child container of the function package of each application is set as all applications in the container, so that the function package can be called by all applications in the container.
In this embodiment, the function identifier of the service corresponding to each application in the storage container is set as the container, the parent container of the function package of each application is set as the container, and the child containers of the function package of each application are set as all applications in the container, so that the function package is set, and the interaction efficiency and the interaction stability between applications are improved.
In one embodiment, the setting the tool pack of each application in the container respectively includes:
setting the dependency range of the tool pack in each application, and setting the dependency range of the tool pack in each application as the inside of the application to which the current tool pack belongs.
Specifically, for the tool kit of each application, the dependency range of the tool kit of each application needs to be set, and the dependency range of the tool kit in each application is set to be within the application to which the current tool kit belongs, so that the tool kit of each application can only be called by the application.
In this embodiment, the dependency range of the tool pack in each application is set, and the dependency range of the tool pack in each application is set to be within the application to which the current tool pack belongs, so that the setting of each application tool pack is realized, the tool pack of each application can only be called by the application, and the interaction efficiency and the interaction stability between applications are improved.
In one embodiment, the container-based multi-application integrated deployment method further comprises:
when a first application in a container needs to call a function package except for an application function package in the container, detecting whether the function package which needs to be called by the first application exists in the container;
and if so, the first application calls the function packet which needs to be called by the first application based on the in-process communication request to acquire response data.
Specifically, when a first application in a container needs to call a function package other than the application function package in the container, detecting whether the function package which needs to be called by the first application exists in the container; wherein the first application may be any application within the container. If the function package which needs to be called by the first application exists in the container, the first application calls the function package which needs to be called by the first application based on the in-process communication request, response data is obtained, and the use of the required function package is achieved.
In this embodiment, when a first application in the container needs to call a function package other than the function package of the application, whether the function package needed by the first application exists in the container is determined by detection, and corresponding operation is performed according to a detection result, so that calling of the application in the container to the other function packages is realized, and interaction efficiency and interaction stability between applications are improved.
In one embodiment, the first application calls a function package which needs to be called by the first application based on an in-process communication request, and the obtaining response data includes:
acquiring a second application to which a function package required to be called by the first application belongs through detection;
sending an in-process communication request to the second application; the in-process communication request comprises an identifier of the first application, a function identifier of a function packet required to be called by the first application and request parameters;
receiving response data sent by the second application; the response data is generated by the second application processing the in-process communication request.
Specifically, in order to call a function package required by a first application, a second application to which the function package required to be called by the first application belongs is obtained through detection, and an in-process communication request is sent to the second application; the in-process communication request comprises an identifier of a first application, a function identifier of a function packet required to be called by the first application and a request parameter; and the second application generates corresponding response data according to the received in-process communication request sent by the first application and sends the response data to the first application. And the first application receives the response data sent by the second application to realize the calling of the required function package.
In this embodiment, the first application obtains, through detection, the second application to which the function package that the first application needs to call belongs, and sends the in-process communication request to the second application, and realizes, through receiving the response data sent by the second application, call between applications in the container, without depending on network interaction, and thus stability of interaction between applications is ensured as much as possible.
It should be understood that, although the steps in the flowcharts related to the embodiments as described above are sequentially displayed as indicated by arrows, the steps are not necessarily performed sequentially as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the flowcharts related to the embodiments described above may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the execution order of the steps or stages is not necessarily sequential, but may be rotated or alternated with other steps or at least a part of the steps or stages in other steps.
Based on the same inventive concept, the embodiment of the present application further provides a container-based multi-application integrated deployment apparatus for implementing the container-based multi-application integrated deployment method mentioned above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme described in the above method, so specific limitations in one or more embodiments of the container-based multi-application integrated deployment device provided below may refer to the limitations in the above container-based multi-application integrated deployment method, and are not described herein again.
In one embodiment, as shown in fig. 4, there is provided a container-based multi-application integrated deployment apparatus, comprising: an obtaining module 401, a classifying module 402, a first setting module 403, and a second setting module 404, wherein:
the obtaining module 401 is configured to obtain at least one application to be deployed, and merge and deploy the application to be deployed to the same directory in the same container.
A classification module 402, configured to classify the classes of the applications in the container into a function package and a tool package; the function package is a package which can be called by all applications in the container; the toolkit is a kit used only in the current application.
A first setting module 403, configured to set the function packages of the applications in the container respectively, so that the function packages can be called by all applications in the container.
And a second setting module 404, configured to set a tool kit of each application in the container, so that the tool kit is only used in the current application to which the tool kit belongs.
In one embodiment, the classification module 402 is specifically configured to: acquiring the class of each application in the container; and classifying the classes into a function package and a tool package according to a preset classification rule.
In an embodiment, the first setting module 403 is specifically configured to: storing function identifiers of the corresponding services of the applications in the container; setting the parent container of the function package of each application as a container, and simultaneously setting the child container of the function package of each application as all the applications in the container.
In an embodiment, the second setting module 404 is specifically configured to: setting the dependency range of the tool pack in each application, and setting the dependency range of the tool pack in each application as the inside of the application to which the current tool pack belongs.
In one embodiment, the second setup module 404 is further configured to: when a first application in a container needs to call a function package except for an application function package in the container, detecting whether the function package which needs to be called by the first application exists in the container; and if so, the first application calls the function packet which needs to be called by the first application based on the in-process communication request to acquire response data.
In one embodiment, the second setup module 404 is further configured to: acquiring a second application to which a function package required to be called by the first application belongs through detection; sending an in-process communication request to the second application; the in-process communication request comprises an identifier of the first application, a function identifier of a function packet required to be called by the first application and request parameters; receiving response data sent by the second application; the response data is generated by the second application processing the in-process communication request.
The container-based multi-application integrated deployment device obtains at least one application to be deployed, the application to be deployed is merged and deployed into the same directory in the same container, the classes of the applications in the container are divided into the function packages and the tool packages, the function packages of the applications in the container are respectively set, the function packages can be called by all the applications in the container, the tool packages of the applications in the container are respectively set, the tool packages are only used in the current applications to which the tool packages belong, hardware resources of a computer are saved by deploying the applications in the same container, the applications deployed in the container belong to the same process, original network interaction can be replaced by in-process interaction, and interaction efficiency and interaction stability among the applications are improved.
The various modules in the container-based multi-application integrated deployment apparatus may be implemented in whole or in part by software, hardware, and combinations thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 5. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a container-based multi-application integration deployment method.
Those skilled in the art will appreciate that the architecture shown in fig. 5 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:
acquiring at least one application to be deployed, and merging and deploying the application to be deployed into the same directory in the same container;
classifying the types of the applications in the container into a function package and a tool package; the function package is a package which can be called by all applications in the container; the toolkit is a kit used only in the current application;
respectively setting the function packages of the applications in the container, so that the function packages can be called by all the applications in the container;
the tool packages of all applications in the container are respectively set, so that the tool packages are only used in the current application to which the tool packages belong.
In one embodiment, the processor, when executing the computer program, further performs the steps of: acquiring the class of each application in the container; and classifying the classes into a function package and a tool package according to a preset classification rule.
In one embodiment, the processor, when executing the computer program, further performs the steps of: storing function identifiers of the corresponding services of the applications in the container; setting the parent container of the function package of each application as a container, and simultaneously setting the child container of the function package of each application as all the applications in the container.
In one embodiment, the processor, when executing the computer program, further performs the steps of: setting the dependency range of the tool pack in each application, and setting the dependency range of the tool pack in each application as the inside of the application to which the current tool pack belongs.
In one embodiment, the processor, when executing the computer program, further performs the steps of: when a first application in a container needs to call a function package except for an application function package in the container, detecting whether the function package which needs to be called by the first application exists in the container; and if so, the first application calls the function packet which needs to be called by the first application based on the in-process communication request to acquire response data.
In one embodiment, the processor, when executing the computer program, further performs the steps of: acquiring a second application to which a function package required to be called by the first application belongs through detection; sending an in-process communication request to the second application; the in-process communication request comprises an identifier of the first application, a function identifier of a function packet required to be called by the first application and request parameters; receiving response data sent by the second application; the response data is generated by the second application processing the in-process communication request.
The computer equipment obtains at least one application to be deployed, the application to be deployed is merged and deployed into the same directory in the same container, the types of the applications in the container are divided into the function packages and the tool packages, the function packages of the applications in the container are respectively set, the function packages can be called by all the applications in the container, the tool packages of the applications in the container are respectively set, the tool packages are only used in the current applications to which the tool packages belong, hardware resources of a computer are saved by deploying the applications in the same container, the applications deployed in the same container belong to the same process, original network interaction can be replaced by in-process interaction, and interaction efficiency and interaction stability among the applications are improved.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
acquiring at least one application to be deployed, and merging and deploying the application to be deployed into the same directory in the same container;
classifying the types of the applications in the container into a function package and a tool package; the function package is a package which can be called by all applications in the container; the toolkit is a kit used only in the current application;
respectively setting the function packages of the applications in the container, so that the function packages can be called by all the applications in the container;
the tool packages of all applications in the container are respectively set, so that the tool packages are only used in the current application to which the tool packages belong.
In one embodiment, the computer program when executed by the processor further performs the steps of: acquiring the class of each application in the container; and classifying the classes into a function package and a tool package according to a preset classification rule.
In one embodiment, the computer program when executed by the processor further performs the steps of: storing function identifiers of the corresponding services of the applications in the container; setting the parent container of the function package of each application as a container, and simultaneously setting the child container of the function package of each application as all the applications in the container.
In one embodiment, the computer program when executed by the processor further performs the steps of: setting the dependency range of the tool pack in each application, and setting the dependency range of the tool pack in each application as the inside of the application to which the current tool pack belongs.
In one embodiment, the computer program when executed by the processor further performs the steps of: when a first application in a container needs to call a function package except for an application function package in the container, detecting whether the function package which needs to be called by the first application exists in the container; and if so, the first application calls the function packet which needs to be called by the first application based on the in-process communication request to acquire response data.
In one embodiment, the computer program when executed by the processor further performs the steps of: acquiring a second application to which a function package required to be called by the first application belongs through detection; sending an in-process communication request to the second application; the in-process communication request comprises an identifier of the first application, a function identifier of a function packet required to be called by the first application and request parameters; receiving response data sent by the second application; the response data is generated by the second application processing the in-process communication request.
The storage medium obtains at least one application to be deployed, the applications to be deployed are merged and deployed into the same directory in the same container, the classes of the applications in the container are divided into the function packages and the tool packages, the function packages of the applications in the container are respectively set, the function packages can be called by all the applications in the container, the tool packages of the applications in the container are respectively set, the tool packages are only used in the current applications to which the tool packages belong, hardware resources of a computer are saved by deploying the applications in the same container, the applications deployed in the same container belong to the same process, original network interaction can be replaced by in-process interaction, and interaction efficiency and interaction stability among the applications are improved.
In one embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, performs the steps of:
acquiring at least one application to be deployed, and merging and deploying the application to be deployed into the same directory in the same container;
classifying the types of the applications in the container into a function package and a tool package; the function package is a package which can be called by all applications in the container; the toolkit is a kit used only in the current application;
respectively setting the function packages of the applications in the container, so that the function packages can be called by all the applications in the container;
the tool packages of all applications in the container are respectively set, so that the tool packages are only used in the current application to which the tool packages belong.
In one embodiment, the computer program when executed by the processor further performs the steps of: acquiring the class of each application in the container; and classifying the classes into a function package and a tool package according to a preset classification rule.
In one embodiment, the computer program when executed by the processor further performs the steps of: storing function identifiers of the corresponding services of the applications in the container; setting the parent container of the function package of each application as a container, and simultaneously setting the child container of the function package of each application as all the applications in the container.
In one embodiment, the computer program when executed by the processor further performs the steps of: setting the dependency range of the tool pack in each application, and setting the dependency range of the tool pack in each application as the inside of the application to which the current tool pack belongs.
In one embodiment, the computer program when executed by the processor further performs the steps of: when a first application in a container needs to call a function package except for an application function package in the container, detecting whether the function package which needs to be called by the first application exists in the container; and if so, the first application calls the function packet which needs to be called by the first application based on the in-process communication request to acquire response data.
In one embodiment, the computer program when executed by the processor further performs the steps of: acquiring a second application to which a function package required to be called by the first application belongs through detection; sending an in-process communication request to the second application; the in-process communication request comprises an identifier of the first application, a function identifier of a function packet required to be called by the first application and request parameters; receiving response data sent by the second application; the response data is generated by the second application processing the in-process communication request.
The computer program product obtains at least one application to be deployed, the applications to be deployed are merged and deployed into the same directory in the same container, the types of the applications in the container are divided into the function packages and the tool packages, the function packages of the applications in the container are respectively set, the function packages can be called by all the applications in the container, the tool packages of the applications in the container are respectively set, the tool packages are only used in the current applications to which the tool packages belong, hardware resources of a computer are saved by deploying the applications in the same container, the applications deployed in the same container belong to the same process, original network interaction can be replaced by in-process interaction, and interaction efficiency and interaction stability among the applications are improved.
It should be noted that, the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high-density embedded nonvolatile Memory, resistive Random Access Memory (ReRAM), Magnetic Random Access Memory (MRAM), Ferroelectric Random Access Memory (FRAM), Phase Change Memory (PCM), graphene Memory, and the like. Volatile Memory can include Random Access Memory (RAM), external cache Memory, and the like. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others. The databases referred to in various embodiments provided herein may include at least one of relational and non-relational databases. The non-relational database may include, but is not limited to, a block chain based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, quantum computing based data processing logic devices, etc., without limitation.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.
Claims (10)
1. A container-based multi-application integrated deployment method, the method comprising:
acquiring at least one application to be deployed, and merging and deploying the application to be deployed into the same directory in the same container;
classifying the types of the applications in the container into a function package and a tool package; the function package is a package which can be called by all applications in the container; the toolkit is a kit used only in the current application;
respectively setting the function packages of the applications in the container, so that the function packages can be called by all the applications in the container;
the tool packages of all applications in the container are respectively set, so that the tool packages are only used in the current application to which the tool packages belong.
2. The method of claim 1, wherein the classifying the classes of applications in the container into a function package and a tool package comprises:
acquiring the class of each application in the container;
and classifying the classes into a function package and a tool package according to a preset classification rule.
3. The method according to claim 2, wherein the setting the function packages of the applications in the container respectively comprises:
storing function identifiers of the corresponding services of the applications in the container;
setting the parent container of the function package of each application as a container, and simultaneously setting the child container of the function package of each application as all the applications in the container.
4. The method of claim 1, wherein the individually setting up the tool packs for the applications in the container comprises:
setting the dependency range of the tool pack in each application, and setting the dependency range of the tool pack in each application as the inside of the application to which the current tool pack belongs.
5. The method of claim 1, wherein the container-based multi-application integration deployment method further comprises:
when a first application in a container needs to call a function package except for an application function package in the container, detecting whether the function package which needs to be called by the first application exists in the container;
and if so, the first application calls the function packet which needs to be called by the first application based on the in-process communication request to acquire response data.
6. The method of claim 5, wherein the first application calls a feature package that the first application needs to call based on an in-process communication request, and wherein obtaining response data comprises:
acquiring a second application to which a function package required to be called by the first application belongs through detection;
sending an in-process communication request to the second application; the in-process communication request comprises an identifier of the first application, a function identifier of a function packet required to be called by the first application and request parameters;
receiving response data sent by the second application; the response data is generated by the second application processing the in-process communication request.
7. A container-based multi-application integrated deployment apparatus, the apparatus comprising:
the system comprises an acquisition module, a storage module and a deployment module, wherein the acquisition module is used for acquiring at least one application to be deployed and merging and deploying the application to be deployed into the same catalog in the same container;
the classification module is used for classifying the types of the applications in the container into a function package and a tool package; the function package is a package which can be called by all applications in the container; the toolkit is a kit used only in the current application;
the first setting module is used for respectively setting the function packages of the applications in the container, so that the function packages can be called by all the applications in the container;
and the second setting module is used for respectively setting the tool packages of the applications in the container, so that the tool packages are only used in the current application to which the tool packages belong.
8. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 6.
9. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 6.
10. A computer program product comprising a computer program, characterized in that the computer program realizes the steps of the method of any one of claims 1 to 6 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111501477.4A CN114185644A (en) | 2021-12-09 | 2021-12-09 | Container-based multi-application integrated deployment method and device and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111501477.4A CN114185644A (en) | 2021-12-09 | 2021-12-09 | Container-based multi-application integrated deployment method and device and computer equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114185644A true CN114185644A (en) | 2022-03-15 |
Family
ID=80604119
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111501477.4A Pending CN114185644A (en) | 2021-12-09 | 2021-12-09 | Container-based multi-application integrated deployment method and device and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114185644A (en) |
-
2021
- 2021-12-09 CN CN202111501477.4A patent/CN114185644A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10505830B2 (en) | Container monitoring configuration deployment | |
| EP3221795B1 (en) | Service addressing in distributed environment | |
| US11188561B2 (en) | Prioritizing microservices on a container platform for a restore operation | |
| CN109614167B (en) | Method and system for managing plug-ins | |
| JP2017514218A (en) | Running third-party applications | |
| CN108268211B (en) | Data processing method and device | |
| US9684689B2 (en) | Distributed parallel processing system having jobs processed by nodes based on authentication using unique identification of data | |
| CN113204353B (en) | Big data platform assembly deployment method and device | |
| TW202008763A (en) | Data processing method and apparatus, and client | |
| US20200274758A1 (en) | Provisioning hybrid cloud resources in an operating environment | |
| CN113867600A (en) | Development method and device for processing streaming data and computer equipment | |
| US11418583B2 (en) | Transaction process management by dynamic transaction aggregation | |
| CN113485830A (en) | Micro-service automatic capacity expansion method for power grid monitoring system | |
| CN111399999B (en) | Computer resource processing method, device, readable storage medium and computer equipment | |
| US20240061732A1 (en) | Industry opinionated api managed service | |
| CN114185644A (en) | Container-based multi-application integrated deployment method and device and computer equipment | |
| CN113867776B (en) | Method and device for issuing middle-stage application, electronic equipment and storage medium | |
| US11531674B2 (en) | System and method for supporting rollback of changes made to target systems via an integration platform | |
| CN115357433A (en) | Database backup method, device, equipment and storage medium under container environment | |
| US20180341475A1 (en) | Just In Time Deployment with Package Managers | |
| CN115080955A (en) | Target data filtering method and device, electronic equipment and storage medium | |
| CN111538491A (en) | Data event processing method, device, equipment and storage medium | |
| US20180165376A1 (en) | Configuration resolution for transitive dependencies | |
| CN112486501B (en) | Spark application deployment management method and related equipment | |
| US20240103818A1 (en) | Annotation driven just in time and state-based rbac policy control |
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 | ||
| CB02 | Change of applicant information |
Country or region after: China Address after: 518000 Room 201, building A, No. 1, Qian Wan Road, Qianhai Shenzhen Hong Kong cooperation zone, Shenzhen, Guangdong (Shenzhen Qianhai business secretary Co., Ltd.) Applicant after: Zhaolian Consumer Finance Co.,Ltd. Address before: 518000 Room 201, building A, No. 1, Qian Wan Road, Qianhai Shenzhen Hong Kong cooperation zone, Shenzhen, Guangdong (Shenzhen Qianhai business secretary Co., Ltd.) Applicant before: MERCHANTS UNION CONSUMER FINANCE Co.,Ltd. Country or region before: China |
|
| CB02 | Change of applicant information |