CN113296794A - Software engineering management method and device, storage medium and electronic equipment - Google Patents
Software engineering management method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN113296794A CN113296794A CN202110568818.3A CN202110568818A CN113296794A CN 113296794 A CN113296794 A CN 113296794A CN 202110568818 A CN202110568818 A CN 202110568818A CN 113296794 A CN113296794 A CN 113296794A
- Authority
- CN
- China
- Prior art keywords
- virtual machine
- deployment
- service field
- target
- target service
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 42
- 238000000034 method Methods 0.000 claims abstract description 26
- 230000004927 fusion Effects 0.000 claims description 8
- 238000012790 confirmation Methods 0.000 claims description 7
- 238000004590 computer program Methods 0.000 claims description 5
- 238000012544 monitoring process Methods 0.000 claims description 4
- 238000012216 screening Methods 0.000 claims description 2
- 230000008859 change Effects 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 11
- 238000011161 development Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 230000009471 action Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012827 research and development Methods 0.000 description 2
- 238000010276 construction Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- 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/45583—Memory management, e.g. access or allocation
Abstract
The application provides a software engineering management method, a device, a storage medium and electronic equipment, wherein a local package is constructed according to a target service field in configuration information, wherein the local package comprises an operation logic for operating the target service field; constructing a complete deployment package on the basis of the local package according to a preset deployment rule; the complete deployment package is used for running inside the target virtual machine to complete the operation corresponding to the target service field, and comprises deployment rules, wherein the deployment rules comprise loading modes of loading each running logic by the target virtual machine. An engineer can change configuration information according to the service supported by the engineer, so that a target service field is determined, and a corresponding local package is generated. After deployment is completed, the virtual machine application capable of supporting the corresponding service is generated, and the method is simple, quick and high in efficiency.
Description
Technical Field
The present application relates to the field of software engineering management, and in particular, to a software engineering management method, an apparatus, a storage medium, and an electronic device.
Background
Because the Dmall OS early-stage system research and development are carried out according to the internet enterprise system splitting mode, the sub-systems of all the service lines are finely split, and the number of the sub-systems is large. The number of applications under only supply chain and IOT development department can reach 400+, and the complexity and cost in development, maintenance and the like are greatly increased by the huge subsystems. In the subsequent iteration process of the Dmall OS, the number of subsystems of the OS needs to be reasonably controlled by formulating a certain specification.
With the rapid development of services, regardless of the complexity of the field contained in the services, regardless of the actual traffic size of the services, and regardless of the importance of application grading, applications are split by using a vertical service module and a horizontal service module, and then are deployed according to services with different characteristics, such as a background management service (WEB), an externally provided API service (RPC), a timed task execution service (JOB), an asynchronous message processing service (MQ), and the like, so that the number of service systems and the number of deployed instances increase rapidly. Therefore, a software engineering management method is urgently needed, and flexible expansion deployment in the service field can be flexibly performed along with the development of services, so that the number of service systems and deployment examples can be as consistent as possible with the actual development requirements of the services.
Disclosure of Invention
An object of the present application is to provide a software engineering management method, apparatus, storage medium and electronic device, so as to at least partially improve the above problems.
In order to achieve the above purpose, the embodiments of the present application employ the following technical solutions:
in a first aspect, an embodiment of the present application provides a software engineering management method, which is applied to an electronic device, and the method includes:
constructing a local package according to a target service field in configuration information, wherein the local package comprises an operation logic for operating the target service field;
constructing a complete deployment package on the basis of the local package according to a preset deployment rule;
the complete deployment package is used for running inside a target virtual machine to complete the operation corresponding to the target service field, and the complete deployment package comprises the deployment rule, and the deployment rule comprises a loading mode of loading each running logic by the target virtual machine.
In a second aspect, an embodiment of the present application provides a software engineering management apparatus, which is applied to an electronic device, and the apparatus includes:
the service field module is used for constructing a local package according to the target service field in the configuration information, wherein the local package comprises operation logic for operating the target service field;
the deployment module is used for constructing a complete deployment package on the basis of the local package according to a preset deployment rule;
the complete deployment package is used for running inside a target virtual machine to complete the operation corresponding to the target service field, and the complete deployment package comprises the deployment rule, and the deployment rule comprises a loading mode of loading each running logic by the target virtual machine.
In a third aspect, the present application provides a storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the method described above.
In a fourth aspect, an embodiment of the present application provides an electronic device, including: a processor and memory for storing one or more programs; the one or more programs, when executed by the processor, implement the methods described above.
Compared with the prior art, the software engineering management method, the device, the storage medium and the electronic equipment provided by the embodiment of the application construct the local package according to the target service field in the configuration information, wherein the local package comprises the operation logic for operating the target service field; constructing a complete deployment package on the basis of the local package according to a preset deployment rule; the complete deployment package is used for running inside the target virtual machine to complete the operation corresponding to the target service field, and comprises deployment rules, wherein the deployment rules comprise loading modes of loading each running logic by the target virtual machine. An engineer can change configuration information according to the service supported by the engineer, so that a target service field is determined, and a corresponding local package is generated. After deployment is completed, the virtual machine application capable of supporting the corresponding service is generated, and the method is simple, quick and high in efficiency.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and it will be apparent to those skilled in the art that other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure;
fig. 2 is a schematic flowchart of a software engineering management method according to an embodiment of the present application;
fig. 3 is a schematic diagram of a target service domain provided in an embodiment of the present application;
FIG. 4 is a flowchart illustrating a software engineering management method according to an embodiment of the present disclosure;
fig. 5 is a schematic view of substeps of S101 provided in an embodiment of the present application;
fig. 6 is a schematic block diagram of a software engineering management apparatus according to an embodiment of the present application.
In the figure: 10-a processor; 11-a memory; 12-a bus; 13-a communication interface; business domain module-201; module-202 is deployed.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, 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 some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. 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.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
In the description of the present application, it should be noted that the terms "upper", "lower", "inner", "outer", and the like indicate orientations or positional relationships based on orientations or positional relationships shown in the drawings or orientations or positional relationships conventionally found in use of products of the application, and are used only for convenience in describing the present application and for simplification of description, but do not indicate or imply that the referred devices or elements must have a specific orientation, be constructed in a specific orientation, and be operated, and thus should not be construed as limiting the present application.
In the description of the present application, it is also to be noted that, unless otherwise explicitly specified or limited, the terms "disposed" and "connected" are to be interpreted broadly, e.g., as being either fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meaning of the above terms in the present application can be understood in a specific case by those of ordinary skill in the art.
Some embodiments of the present application will be described in detail below with reference to the accompanying drawings. The embodiments described below and the features of the embodiments can be combined with each other without conflict.
The application is to provide a software engineering management method capable of flexibly and telescopically supporting a business domain, the data volume of the business domain supported by an application on an engineering structure can be more or less, and the services supported by the application on the engineering structure can be flexibly deployed in a detachable and combinable manner (background management service, external API service, timing task execution service, asynchronous message processing service and the like), so that deployment examples are as consistent as possible with the actual requirements of the business as much as possible, and finally the number of SaaS business systems in the new retail domain and the number of the deployment examples are controlled within a reasonable range, thereby reducing the complexity and cost of research and development and maintenance.
The embodiment of the application provides an electronic device which can be a server or a computer device. Please refer to fig. 1, a schematic structural diagram of an electronic device. The electronic device comprises a processor 10, a memory 11, a bus 12. The processor 10 and the memory 11 are connected by a bus 12, and the processor 10 is configured to execute an executable module, such as a computer program, stored in the memory 11.
The processor 10 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the software engineering management method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 10. The Processor 10 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the device can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component.
The Memory 11 may comprise a high-speed Random Access Memory (RAM) and may further comprise a non-volatile Memory (non-volatile Memory), such as at least one disk Memory.
The bus 12 may be an ISA (Industry Standard architecture) bus, a PCI (peripheral Component interconnect) bus, an EISA (extended Industry Standard architecture) bus, or the like. Only one bi-directional arrow is shown in fig. 1, but this does not indicate only one bus 12 or one type of bus 12.
The memory 11 is used for storing programs, such as programs corresponding to the software engineering management device. The software engineering management means includes at least one software functional module which may be stored in the memory 11 in the form of software or firmware (firmware) or solidified in an Operating System (OS) of the electronic device. The processor 10, upon receiving the execution instruction, executes the program to implement the software engineering management method.
Possibly, the electronic device provided by the embodiment of the present application further includes a communication interface 13. The communication interface 13 is connected to the processor 10 via a bus.
It should be understood that the structure shown in fig. 1 is merely a structural schematic diagram of a portion of an electronic device, which may also include more or fewer components than shown in fig. 1, or have a different configuration than shown in fig. 1. The components shown in fig. 1 may be implemented in hardware, software, or a combination thereof.
The software engineering management method provided in the embodiment of the present application can be applied to, but is not limited to, the electronic device shown in fig. 1, and please refer to fig. 2:
s101, a local package is constructed according to the target service field in the configuration information.
Wherein the local packet comprises operation logic for operating the target service domain.
Specifically, please refer to fig. 3, where fig. 3 is a schematic diagram of a target service area according to an embodiment of the present application. As shown in fig. 3, the Business fields include a commodity Business field (Sub Business Domain Module-1(ware)), a Business field (Sub Business Domain Module-2 (finder)), a store Business field (Sub Business Domain Module-3(shop)), and other Business fields (Sub Business Domain Module-N).
The configuration information may include any one or more service fields, and the service field included in the configuration information is a target service field. An engineer can change configuration information according to the service supported by the engineer, so that a target service field is determined, and a corresponding local package is generated.
S102, constructing a complete deployment package on the basis of the local package according to a preset deployment rule.
The complete deployment package is used for running inside the target virtual machine to complete the operation corresponding to the target service field, and comprises deployment rules, wherein the deployment rules comprise loading modes of loading each running logic by the target virtual machine.
After deployment is completed, the virtual machine application capable of supporting the corresponding service is generated, and the method is simple, quick and high in efficiency.
To sum up, the embodiment of the present application provides a software engineering management method, which constructs a local package according to a target service field in configuration information, where the local package includes an operation logic for operating the target service field; constructing a complete deployment package on the basis of the local package according to a preset deployment rule; the complete deployment package is used for running inside the target virtual machine to complete the operation corresponding to the target service field, and comprises deployment rules, wherein the deployment rules comprise loading modes of loading each running logic by the target virtual machine. An engineer can change configuration information according to the service supported by the engineer, so that a target service field is determined, and a corresponding local package is generated. After deployment is completed, the virtual machine application capable of supporting the corresponding service is generated, and the method is simple, quick and high in efficiency.
On the basis of fig. 3, regarding to the field of flexible splitting service, the embodiment of the present application further provides an implementation manner. For example, the configuration information Maven config: a profile indicates that all the business fields are included in the configuration information, and all the business fields are target business fields; configuration information Maven config: profile indicates that service fields corresponding to the vender and the ware are both contained in the configuration information, and the service fields corresponding to the vender and the ware are target service fields; configuration information Maven config: and the profile indicates that all the business fields corresponding to the ware are contained in the configuration information, and the business field corresponding to the ware is the target business field.
The engineer constructs a local package through different configuration information, and the service fields supported by the deployed instances are different.
On the basis of fig. 2, regarding how to run the complete deployment package, a possible implementation manner is further provided in the embodiment of the present application, please refer to fig. 4, where the software engineering management method further includes:
and S103, deploying the complete deployment package in the corresponding target virtual machine.
Specifically, the complete deployment package is used for running inside the target virtual machine to complete the operation corresponding to the target service field, and loading each running logic to the target virtual machine according to the deployment rule.
And S104, monitoring the running load of the target virtual machine.
In one possible implementation, the operation load is the amount of traffic processed by the target virtual machine per unit time or the amount of traffic flowing into and out of the target virtual machine.
And S105, judging whether the operation load exceeds a first load threshold value. If yes, executing S106; if not, go to S110.
When the operating load exceeds a first load threshold value, the current load is overweight, and S106 is executed to generate an alarm prompt; otherwise, it is determined whether the current load is too light, and S110 is performed.
And S106, generating an alarm prompt.
The alarm prompt is used for prompting corresponding personnel to process, and the problem of downtime caused by overload for a long time is avoided.
In a case that the operating load exceeds the first load threshold, regarding how to reduce the load of the target virtual machine, the embodiment of the present application further provides a possible implementation manner, please refer to fig. 4 again, and the software engineering management method further includes:
s107, judging whether the number of the sub-business fields in the target business field is more than 1. If yes, executing S108; if not, go to S112.
It should be noted that the target business field in S107 is all business fields currently supported in the target virtual machine. For example, when the Business Domain currently supported in the target virtual machine includes a commodity Business Domain (Sub Business Domain Module-1(ware)) and a Business Domain (Sub Business Domain Module-2 (finder)), both the commodity Business Domain (Sub Business Domain Module-1(ware)) and the Business Domain (Sub Business Domain Module-2 (finder)) may be used as the Sub Business domains.
When the currently supported service field in the target virtual machine is only a large service field, the embodiment of the present application further provides a possible implementation manner regarding the sub-service fields, where each service field includes different services, such as a background management service (controller), an externally provided API service (rpc), a timing task execution service, and an asynchronous message processing service, and the different services in each service field may be used as one sub-service field.
When the number of the sub-service fields in the target service field is greater than 1, the service field supported by the virtual machine can be further split, and then S108 is executed; otherwise, it indicates that the splitting cannot be performed, and S112 is performed.
And S108, generating a splitting inquiry request.
The splitting inquiry request is used for prompting a user whether to split a target service field in a target virtual machine.
In one possible implementation, the split query request includes an identifier of the split sub-service domain and a corresponding load generated by each sub-service domain, so as to facilitate the observation by the user.
And S109, after receiving the splitting confirmation instruction, splitting the original target service field into at least two new target service fields according to the ratio of each sub-service field in the operation load.
In a possible implementation manner, when the number of the detachable sub-service fields is greater than or equal to 3, a recommended splitting manner may be generated according to a load correspondingly generated by each sub-service field, and after receiving a recommended splitting manner confirmation instruction, the original target service field is split into at least two new target service fields according to the recommended splitting manner.
And then S115 is executed, a new local package is constructed based on the new target service field, and a new complete deployment package is constructed on the basis of the new local package according to a preset deployment rule.
The new complete deployment packages are respectively deployed in different virtual machines, and the load of each virtual machine is controlled within a preset range, so that the phenomenon of overload is avoided.
In a case that the operating load does not exceed the first load threshold, regarding how to target the utilization rate of the virtual machine, the embodiment of the present application further provides a possible implementation manner, please refer to fig. 4 again, and the software engineering management method further includes:
and S110, judging whether the running load is smaller than a second load threshold value. If yes, executing S111; if not, go to S112.
Wherein the second load threshold is less than the first load threshold.
When the running load is smaller than the second load threshold, it indicates that the current state of the target virtual machine is idle and the utilization rate is low, and at this time, the utilization rate needs to be increased, so S111 is executed; otherwise, S112 is executed.
And S111, judging whether the virtual machine to be fused exists or not. If yes, go to S113; if not, go to S112.
And the virtual machines to be fused are the virtual machines except the target virtual machine and the running load of the virtual machines is smaller than the second load threshold value.
When the virtual machine to be fused exists, the fusion possibility exists, and S113 is executed; otherwise, S112 is executed.
S112, skipping.
And S113, generating a fusion inquiry request.
The fusion inquiry request comprises identification information of a target virtual machine and a virtual machine to be fused, and is used for prompting a user whether to fuse target service fields in the target virtual machine and the virtual machine to be fused.
And S114, after receiving the fusion confirmation instruction, generating a new target service field according to the target service field in the target virtual machine and the virtual machine to be fused.
And S115, constructing a new local package based on the new target service field, and constructing a new complete deployment package based on the new local package according to a preset deployment rule.
On the basis of fig. 2, in a case that the electronic device is configured with operation logics corresponding to each service domain in advance, regarding the content in S101, the embodiment of the present application further provides a possible implementation manner, please refer to fig. 5, where S101 includes:
s101-1, screening out corresponding operation logic according to the target service field in the configuration information.
It should be noted that the operating logic may be formed from a piece of code.
S101-2, the running logic is combined and constructed into a local package.
Referring to fig. 3, the deployment Module (pop-deployment) is a deployment Module (Web/Rpc) in fig. 3.
In the embodiment of the application, the business layer logic and the control layer logic are separated from the deployment module, and the deployment module has flexible business assembly capacity and flexible service deployment capacity, so that the application has flexible business domain expansion and support capacity.
The service interfaces are relied on between the service fields instead of service implementation, so that whether objects relied on between the service fields are in the same instance or not can be possible without considering during deployment, and the cost of application support service domain expansion is reduced.
The deployment module loading items are matched through wildcards, and the configuration maintenance cost of the telescopic service domain during application deployment is reduced to the minimum. The logic module to be loaded by the deployment module is flexible and variable through configuration, so that the service supported by the application example is scalable. The universal capability of the cross-service field is independently formed into a universal module, and the logic of the external providing capability in the service field is placed in the universal module, so that the code reuse rate is improved as much as possible.
In the embodiment of the application, the software engineering management method capable of flexibly and telescopically supporting the service domain is realized by applying language polymorphic characteristics and wildcard matching loading capacity and adopting a modular construction idea and configuration capacity. The service field is used as the minimum unit of an engineering service module, the service module only comprises a logic module, the deployment module is used as the service field for sharing, the service field borne by the deployment module is controlled by configuration instead of being fixed by the traditional default, and the service field can be flexibly assembled.
The splitting or merging of the deployment service is realized under no code or little configuration code adjustment. And the vertical splitting of the service field in the engineering is supported, and the horizontal splitting of the support function module in the service field is supported. And the business field supported by the deployment module is finally constructed, packed and assembled by maven.
Referring to fig. 6, fig. 6 is a diagram of a software engineering management apparatus according to an embodiment of the present application, where optionally, the software engineering management apparatus is applied to the electronic device described above.
The software engineering management device comprises: a business domain module 201 and a deployment module 202.
The service domain module 201 is configured to construct a local package according to the target service domain in the configuration information, where the local package includes an operation logic for operating the target service domain. Alternatively, the business segment module 201 may perform S101 described above.
The deployment module 202 is configured to construct a complete deployment package on the basis of the local package according to a preset deployment rule.
The complete deployment package is used for running inside the target virtual machine to complete the operation corresponding to the target service field, and comprises deployment rules, wherein the deployment rules comprise loading modes of loading each running logic by the target virtual machine.
Alternatively, the deployment module 202 may perform S102 described above.
In a possible implementation manner, the deployment module 202 is further configured to deploy the complete deployment package into the corresponding target virtual machine; monitoring the running load of the target virtual machine; when the operating load exceeds a first load threshold, an alert prompt is generated.
When the operating load exceeds the first load threshold, the deployment module 202 is further configured to determine whether the number of sub-service fields in the target service field is greater than 1; if so, generating a splitting inquiry request, wherein the splitting inquiry request is used for prompting a user whether to split a target service field in the target virtual machine; after receiving the splitting confirmation instruction, splitting the original target service field into at least two new target service fields according to the ratio of each sub-service field in the operation load.
Alternatively, the deployment module 202 may perform S103 to S109 described above.
The service domain module 201 is further configured to construct a new local package based on the new target service domain, and construct a new complete deployment package based on the new local package according to a preset deployment rule. Alternatively, the business segment module 201 may perform S115 described above.
It should be noted that the software engineering management apparatus provided in this embodiment may execute the method flows shown in the above method flow embodiments to achieve the corresponding technical effects. For the sake of brevity, the corresponding contents in the above embodiments may be referred to where not mentioned in this embodiment.
The embodiment of the application also provides a storage medium, wherein the storage medium stores computer instructions and programs, and the computer instructions and the programs execute the software engineering management method of the embodiment when being read and run. The storage medium may include memory, flash memory, registers, or a combination thereof, etc.
The following provides an electronic device, which may be a server or a computer device, and as shown in fig. 1, the electronic device may implement the software engineering management method described above; specifically, the electronic device includes: processor 10, memory 11, bus 12. The processor 10 may be a CPU. The memory 11 is used for storing one or more programs, and when the one or more programs are executed by the processor 10, the software engineering management method of the above-described embodiment is performed.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules 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 or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including 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 description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.
It will be evident to those skilled in the art that the present application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned.
Claims (10)
1. A software engineering management method is applied to electronic equipment, and the method comprises the following steps:
constructing a local package according to a target service field in configuration information, wherein the local package comprises an operation logic for operating the target service field;
constructing a complete deployment package on the basis of the local package according to a preset deployment rule;
the complete deployment package is used for running inside a target virtual machine to complete the operation corresponding to the target service field, and the complete deployment package comprises the deployment rule, and the deployment rule comprises a loading mode of loading each running logic by the target virtual machine.
2. The software engineering management method of claim 1, wherein after building a complete deployment package, the method comprises:
deploying the complete deployment package in a corresponding target virtual machine;
monitoring the running load of the target virtual machine;
and when the operation load exceeds a first load threshold value, generating an alarm prompt.
3. The software engineering management method of claim 2, wherein when the operational load exceeds a first load threshold, the method further comprises:
judging whether the number of the sub-service fields in the target service field is more than 1;
if so, generating a splitting inquiry request, wherein the splitting inquiry request is used for prompting a user whether to split a target service field in the target virtual machine;
after receiving the splitting confirmation instruction, splitting the original target service field into at least two new target service fields according to the ratio of each sub-service field in the running load;
and constructing a new local package based on the new target service field, and constructing a new complete deployment package based on the new local package according to a preset deployment rule.
4. The software engineering management method of claim 2, wherein when the operational load does not exceed a first load threshold, the method further comprises:
when the running load is smaller than a second load threshold value, judging whether a virtual machine to be fused exists or not;
the second load threshold is smaller than the first load threshold, the virtual machine to be fused is a virtual machine except the target virtual machine, and the running load of the virtual machine is smaller than the second load threshold;
generating a fusion inquiry request, wherein the fusion inquiry request comprises identification information of the target virtual machine and the virtual machine to be fused, and the fusion inquiry request is used for prompting a user whether to fuse target service fields in the target virtual machine and the virtual machine to be fused;
after receiving a fusion confirmation instruction, generating a new target service field according to the target virtual machine and the target service field in the virtual machine to be fused;
and constructing a new local package based on the new target service field, and constructing a new complete deployment package based on the new local package according to a preset deployment rule.
5. The software engineering management method according to claim 1, wherein the electronic device is preconfigured with operation logic corresponding to each service domain, and the step of constructing the local package according to the target service domain in the configuration information includes:
screening out corresponding operation logic according to the target service field in the configuration information;
and constructing the running logic combination into the local package.
6. A software engineering management device is applied to electronic equipment, and the device comprises:
the service field module is used for constructing a local package according to the target service field in the configuration information, wherein the local package comprises operation logic for operating the target service field;
the deployment module is used for constructing a complete deployment package on the basis of the local package according to a preset deployment rule;
the complete deployment package is used for running inside a target virtual machine to complete the operation corresponding to the target service field, and the complete deployment package comprises the deployment rule, and the deployment rule comprises a loading mode of loading each running logic by the target virtual machine.
7. The software engineering management apparatus of claim 6, wherein the deployment module is further configured to deploy the complete deployment package in the corresponding target virtual machine; monitoring the running load of the target virtual machine; and when the operation load exceeds a first load threshold value, generating an alarm prompt.
8. The software engineering management device according to claim 7, wherein when the operation load exceeds a first load threshold, the deployment module is further configured to determine whether the number of sub-business domains in the target business domain is greater than 1; if so, generating a splitting inquiry request, wherein the splitting inquiry request is used for prompting a user whether to split a target service field in the target virtual machine; after receiving the splitting confirmation instruction, splitting the original target service field into at least two new target service fields according to the ratio of each sub-service field in the running load;
the service field module is also used for constructing a new local package based on the new target service field and constructing a new complete deployment package based on the new local package according to a preset deployment rule.
9. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-5.
10. An electronic device, comprising: a processor and memory for storing one or more programs; the one or more programs, when executed by the processor, implement the method of any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110568818.3A CN113296794A (en) | 2021-05-25 | 2021-05-25 | Software engineering management method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110568818.3A CN113296794A (en) | 2021-05-25 | 2021-05-25 | Software engineering management method and device, storage medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113296794A true CN113296794A (en) | 2021-08-24 |
Family
ID=77324585
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110568818.3A Pending CN113296794A (en) | 2021-05-25 | 2021-05-25 | Software engineering management method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113296794A (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110243142A1 (en) * | 2010-03-31 | 2011-10-06 | Brocade Communications Systems, Inc. | Ingress and egress switch which determines services related to an incoming packet |
| WO2016177049A1 (en) * | 2015-08-31 | 2016-11-10 | 中兴通讯股份有限公司 | Method and device for achieving capacity expansion and reduction of access apparatus |
| WO2018072708A1 (en) * | 2016-10-21 | 2018-04-26 | 中兴通讯股份有限公司 | Cloud platform service capacity reduction method, apparatus, and cloud platform |
| CN110597623A (en) * | 2019-08-13 | 2019-12-20 | 平安普惠企业管理有限公司 | Container resource allocation method and device, computer equipment and storage medium |
| US20200142788A1 (en) * | 2018-11-06 | 2020-05-07 | International Business Machines Corporation | Fault tolerant distributed system to monitor, recover and scale load balancers |
| CN112181439A (en) * | 2020-09-24 | 2021-01-05 | 中国建设银行股份有限公司 | Micro-service deployment method and device, electronic equipment and readable storage medium |
| CN112416506A (en) * | 2019-08-21 | 2021-02-26 | 中移(苏州)软件技术有限公司 | Container management method, device and computer storage medium |
| CN112433845A (en) * | 2020-10-29 | 2021-03-02 | 苏州浪潮智能科技有限公司 | HBase service management method, device, equipment and readable medium |
| CN112711465A (en) * | 2021-03-23 | 2021-04-27 | 腾讯科技（深圳）有限公司 | Data processing method and device based on cloud platform, electronic equipment and storage medium |
-
2021
- 2021-05-25 CN CN202110568818.3A patent/CN113296794A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110243142A1 (en) * | 2010-03-31 | 2011-10-06 | Brocade Communications Systems, Inc. | Ingress and egress switch which determines services related to an incoming packet |
| WO2016177049A1 (en) * | 2015-08-31 | 2016-11-10 | 中兴通讯股份有限公司 | Method and device for achieving capacity expansion and reduction of access apparatus |
| WO2018072708A1 (en) * | 2016-10-21 | 2018-04-26 | 中兴通讯股份有限公司 | Cloud platform service capacity reduction method, apparatus, and cloud platform |
| CN107977252A (en) * | 2016-10-21 | 2018-05-01 | 中兴通讯股份有限公司 | A kind of capacity reduction method, device and the cloud platform of cloud platform business |
| US20200142788A1 (en) * | 2018-11-06 | 2020-05-07 | International Business Machines Corporation | Fault tolerant distributed system to monitor, recover and scale load balancers |
| CN110597623A (en) * | 2019-08-13 | 2019-12-20 | 平安普惠企业管理有限公司 | Container resource allocation method and device, computer equipment and storage medium |
| CN112416506A (en) * | 2019-08-21 | 2021-02-26 | 中移(苏州)软件技术有限公司 | Container management method, device and computer storage medium |
| CN112181439A (en) * | 2020-09-24 | 2021-01-05 | 中国建设银行股份有限公司 | Micro-service deployment method and device, electronic equipment and readable storage medium |
| CN112433845A (en) * | 2020-10-29 | 2021-03-02 | 苏州浪潮智能科技有限公司 | HBase service management method, device, equipment and readable medium |
| CN112711465A (en) * | 2021-03-23 | 2021-04-27 | 腾讯科技（深圳）有限公司 | Data processing method and device based on cloud platform, electronic equipment and storage medium |
Non-Patent Citations (4)
| Title |
|---|
| CZ__: "Maven多模块——打包指定模块", pages 3 - 4, Retrieved from the Internet <URL:https://blog.csdn.net/ththcc/article/details/103769851> * |
| 于溥天;: "分布式服务架构在气象业务***中的应用研究", 信息与电脑(理论版), no. 01, 10 January 2020 (2020-01-10) * |
| 杨小愚: "通过shell脚本实现代码自动化部署", pages 7 - 8, Retrieved from the Internet <URL:https://www.cnblogs.com/yangliheng/p/5783852.html> * |
| 王义;: "微服务架构特点、技术趋势及在行业应用中关键问题研究", 软件, no. 06, 15 June 2020 (2020-06-15) * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6686910B2 (en) | Network function virtualization management and orchestration method, device and program | |
| EP3675424B1 (en) | Method and apparatus for deploying network service | |
| US11210122B2 (en) | Virtual network function management for creating sequence using dependency entry defined to confirm constrain violation | |
| US20180123875A1 (en) | Dynamic scheduling of network updates | |
| JP6441404B2 (en) | Methods and devices for updating clients | |
| US20190334781A1 (en) | Network functions virtualization | |
| CN110476402A (en) | The method, apparatus and communication system of network slice creation | |
| US10152357B1 (en) | Monitoring application workloads scheduled on heterogeneous elements of information technology infrastructure | |
| EP3451594A1 (en) | Network function virtualization management orchestration device, method, and program | |
| CN111130825B (en) | Network slice template generation method, device, equipment and storage medium | |
| CN111786886B (en) | Message processing method, device and system, electronic equipment and storage medium | |
| KR20170104500A (en) | Network features Virtualization management and orchestration methods, devices and programs | |
| CN108494622A (en) | Monitoring rules configuration method, device and server | |
| CN112506617B (en) | Mirror image updating method and device for side car containers in Kubernetes cluster | |
| JP2017503421A (en) | Network function virtualized NFV failure management apparatus, device, and method | |
| US10848366B2 (en) | Network function management method, management unit, and system | |
| US11909603B2 (en) | Priority based resource management in a network functions virtualization (NFV) environment | |
| CN111176789B (en) | Container set exception handling method and device, storage medium and server | |
| US20140053146A1 (en) | Network hardware and software upgrade recommender | |
| CN112789832A (en) | Dynamic slice priority handling | |
| CN105025458B (en) | Method, equipment and system for resource notification | |
| EP3901770A1 (en) | Method and device for instantiating virtualized network function | |
| CN107534577B (en) | Method and equipment for instantiating network service | |
| WO2023045552A1 (en) | Service deployment method, service deployment system, electronic device, and storage medium | |
| CN113296794A (en) | Software engineering management method and device, storage medium and electronic equipment |
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 |