Business function automatic publishing method and device based on module multiplexing and medium
By analyzing and abstracting the business modules in the system to be reused, generating module prefabricated data and function expansion forms, the automatic release of business functions is realized, the module reuse problem in the existing technology is solved, and the development efficiency and system flexibility are improved. , ensuring system stability and user experience.
Patent Information
- Application Number
- CN202411272231.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-11
- Publication Date
- 2024-12-13
AI Technical Summary
In enterprise-level application development, it is difficult for the existing technology to automatically release business functions through module reuse according to specific scenarios and needs, resulting in increased system complexity, performance degradation and difficulty in code maintenance.
By analyzing the system to be reused, reusable business modules are identified, abstract packaging and generalization processing is performed, multiplexed packaging modules and module prefabricated data is generated, business function modules are configured according to the multiplexing requirements, and operating status is monitored for performance analysis and optimization .
It improves software development efficiency and code reusability, enhances system flexibility and configurability, meets users' personalized needs, promptly discovers and solves performance problems, and ensures system reliability and stability.
Smart Images
Figure CN119127172A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of business processing technology, and in particular to a method, device and medium for automatically publishing business functions based on module reuse. Background Art
[0002] In today's enterprise application development field, especially when it is necessary to quickly respond to market changes and customer needs, the reusability of business functions and the flexibility of the system have become important trends in the industry. With the development of cloud computing, microservice architecture, containerization technology, etc., the traditional monolithic application architecture is gradually being replaced by a more modular and service-oriented system architecture. This architecture makes it easier to reuse business functions, while also improving the scalability and maintainability of the system.
[0003] In order to solve the defects of existing technologies, the industry and academia have proposed many innovative technical solutions. For example, the microservice architecture is used to split the system into multiple independent services, each of which is responsible for a specific business function and communicates through APIs. This architecture makes it easier to reuse and expand business functions. In addition, dynamic form generation technology and role-based permission management strategies are also widely used in enterprise-level application systems to improve the flexibility and security of the system.
[0004] However, although these measures have solved the defects of existing technologies to a certain extent, there are still some shortcomings. For example, the microservice architecture brings problems such as increased complexity and distributed transaction processing; dynamic form generation technology may lead to performance degradation and difficulty in code maintenance; role-based permission management strategies may also fail to meet certain special security requirements. Therefore, how to realize the automatic release of business functions through module reuse according to specific scenarios and requirements in actual applications has become a technical problem that needs to be solved urgently. Summary of the invention
[0005] The embodiments of the present application provide a method, device and medium for automatically publishing business functions based on module reuse, which are used to solve the following technical problem: how to realize automatic publishing of business functions through module reuse according to specific scenarios and requirements in actual applications.
[0006] In the first aspect, an embodiment of the present application provides a method for automatically publishing business functions based on module reuse, characterized in that the method includes: parsing the system to be reused to identify the reusable business modules in the system to be reused; abstractly encapsulating the reusable business modules to generate a reused encapsulation module, and generalizing the original configuration data of the reusable business modules to generate module prefabricated data for the obtained generalized data according to the reuse requirements; when it is necessary to publish functions of the system to be reused, configuring the reused encapsulation module based on the module prefabricated data to generate the business function module to be released; and publishing the business function module to be released.
[0007] In one implementation of the present application, the system to be reused is analyzed to identify the reusable business modules in the system to be reused, specifically including: performing logical independence verification and reusability evaluation on each business module in the system to be reused to determine the business modules that meet the logical independence and the reuse possibility evaluation results of each business module; among the business modules that meet the logical independence, the business modules whose reuse possibility evaluation results are greater than a preset threshold are selected as reusable business modules.
[0008] In one implementation of the present application, a reusable business module is abstractly encapsulated to generate a reusable encapsulation module, specifically including: extracting the functional logic and interface configuration of the reusable business module; abstracting the functional logic to form reusable functional logic, and standardizing the interface configuration to form a standardized interface; encapsulating the reusable functional logic and the standardized interface into a reusable encapsulation module.
[0009] In one implementation of the present application, the original configuration data of the reusable business module is generalized, specifically including: identifying specific business configuration information and / or specific permission configuration information in the original configuration data; generalizing the specific business configuration information and / or specific permission configuration information to replace them with general placeholders or variables; and forming generalized data based on the general information in the original configuration data and the generalized specific business configuration information and / or specific permission configuration information.
[0010] In one implementation of the present application, module prefabricated data is generated for the obtained generalized data according to the reuse requirements, specifically including: obtaining the reuse requirements; wherein the reuse requirements include the target data of the target project, and the target data includes the target business configuration information and the target right configuration information; according to the reuse requirements, the corresponding data in the generalized data is replaced with the target data to combine the general data to form the module prefabricated data of the target project.
[0011] In one implementation of the present application, after abstractly encapsulating the reusable business module to generate a reusable encapsulation module, the method also includes: constructing a function extension form of the reusable encapsulation module so that the reusable encapsulation module can select additional special business functions based on the function extension form, specifically including: determining the applicable business type corresponding to the reusable encapsulation module, and matching the adapted extended form items in a preset extended form library based on the applicable business type; wherein the extended form items and their corresponding extended function logic are mutually associated; corresponding function prefabricated data are preset in the extended function logic; and generating the function extension form of the reusable encapsulation module based on the adapted extended form items.
[0012] In one implementation of the present application, after publishing the business function module to be released, the method also includes: monitoring the operating status of the business function module to be released, and collecting operating data in real time; based on the operating data, performing performance analysis and generating optimization suggestions for the business function module to be released; wherein the performance analysis includes response time analysis, resource occupancy analysis, and error rate analysis; the optimization suggestions include adjustment strategies for performance bottlenecks, resource allocation optimization suggestions, and error handling and prevention suggestions.
[0013] In one implementation of the present application, the method further includes: building a version management mechanism for the reused encapsulation module and the business function module to be released; recording the released version each time a function is released, and performing function and performance testing on each version.
[0014] On the second aspect, the embodiment of the present application also provides an automatic business function publishing device based on module reuse, characterized in that the device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can: parse the system to be reused to identify the reusable business modules in the system to be reused; abstractly encapsulate the reusable business modules to generate a reused encapsulation module, and generalize the original configuration data of the reusable business modules to generate module prefabricated data for the obtained generalized data according to the reuse requirements; when it is necessary to publish functions of the system to be reused, configure the reused encapsulation module based on the module prefabricated data to generate the business function module to be released; and publish the business function module to be released.
[0015] On the third aspect, the embodiment of the present application also provides a non-volatile computer storage medium for automatic release of business functions based on module reuse, storing computer executable instructions, characterized in that the computer executable instructions are set to: parse the system to be reused to identify the reusable business modules in the system to be reused; abstractly encapsulate the reusable business modules to generate a reused encapsulation module, and generalize the original configuration data of the reusable business module to generate module prefabricated data for the obtained generalized data according to the reuse requirements; when it is necessary to release the function of the system to be reused, configure the reused encapsulation module based on the module prefabricated data to generate the business function module to be released; and release the business function module to be released.
[0016] The method, device and medium for automatically publishing business functions based on module reuse provided in the embodiments of the present application have the following beneficial effects:
[0017] 1. By analyzing the system to be reused and identifying reusable business modules, and then abstracting, encapsulating and generalizing them, these modules can be reused in different projects, thus significantly improving the efficiency of software development and the reusability of code. This reduces development costs and shortens the development cycle.
[0018] 2. Through the generation and configuration of module prefabricated data, this method can quickly customize and release business function modules according to different reuse requirements, increasing the flexibility and configurability of the system. This enables the system to adapt to market changes and customer needs more quickly.
[0019] 3. By constructing a function extension form of the reused encapsulation module, this method enables the reused encapsulation module to select additional special business functions based on the function extension form, thereby enhancing the functional extensibility of the system. This enables the system to better meet the personalized needs of users.
[0020] 4. By monitoring the operating status of the business function modules to be released and collecting operating data in real time, as well as performing performance analysis and generating optimization suggestions based on the operating data, this method helps to promptly discover and resolve system performance problems, thereby improving user experience and system stability.
[0021] 5. This method ensures the traceability and quality assurance of the system by building a version management mechanism for reused encapsulation modules and business function modules to be released, recording the release version and performing function and performance tests on each version each time a function is released. This helps reduce potential problems introduced by version updates and improves the reliability and stability of the system. BRIEF DESCRIPTION OF THE DRAWINGS
[0022] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:
[0023] Figure 1 A flow chart of a method for automatically publishing business functions based on module reuse provided in an embodiment of the present application;
[0024] Figure 2 A schematic diagram of the internal structure of a device for automatically publishing business functions based on module reuse provided in an embodiment of the present application. DETAILED DESCRIPTION
[0025] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.
[0026] The embodiments of the present application provide a method, device and medium for automatically publishing business functions based on module reuse, which are used to solve the following technical problem: how to realize automatic publishing of business functions through module reuse according to specific scenarios and requirements in actual applications.
[0027] The technical solution proposed in the embodiments of the present application is described in detail below with reference to the accompanying drawings.
[0028] Figure 1 A flowchart of a method for automatically publishing business functions based on module reuse provided in an embodiment of the present application. Figure 1 As shown, an automatic publishing method for business functions based on module reuse provided in an embodiment of the present application specifically includes the following steps:
[0029] Step 101: parse the system to be multiplexed to identify reusable service modules in the system to be multiplexed.
[0030] In one embodiment of the present application, in order to realize automatic release of business functions based on module reuse, it is first necessary to parse the system to be reused to identify the reusable business modules in the system to be reused.
[0031] Specifically, a logical independence check and reusability assessment are performed on each business module in the reused system to determine the business modules that meet the logical independence and the reuse possibility assessment results of each business module; among the business modules that meet the logical independence, the business modules whose reuse possibility assessment results are greater than a preset threshold are selected as reusable business modules.
[0032] In one embodiment, logical independence test: conduct a detailed logical analysis of each business module in the reuse system; use a combination of automated tools and manual review to ensure that each module is logically independent in terms of function, data, and control flow; it is understandable that logical independence is the premise of module reuse, and only logically independent modules can be seamlessly integrated in different systems without side effects. Reusability evaluation: after confirming the logical independence of the business module, further evaluate its reusability; the evaluation criteria include but are not limited to: the universality of the module, the degree of interface standardization, the completeness of the document, the historical reuse record, etc.; automated testing tools can be used to simulate the module reuse in different scenarios to verify its stability and compatibility. Further, according to historical data and business requirements, a preset threshold for reuse possibility evaluation is set, which can be a comprehensive score or a scoring standard in multiple dimensions. Among all the business modules that pass the logical independence test, those modules whose reuse possibility evaluation results are higher than the preset threshold are screened out according to the reusability evaluation results; these modules will be marked as reusable business modules and enter a reusable module library for subsequent projects and system automatic release processes.
[0033] Step 102: abstractly encapsulate the reusable business module to generate a reusable encapsulation module, and generalize the original configuration data of the reusable business module to generate module prefabricated data for the obtained generalized data according to the reuse requirements.
[0034] In one embodiment of the present application, after the reusable service module in the system to be reused is identified, on the one hand, the reusable service module is abstractly encapsulated to generate a reuse encapsulation module.
[0035] Specifically, the functional logic and interface configuration of the reusable business module are extracted; the functional logic is abstracted to form the reusable functional logic, and the interface configuration is standardized to form a standardized interface; the reusable functional logic and the standardized interface are encapsulated into a reusable encapsulation module.
[0036] In one embodiment, after successfully identifying the reusable business modules in the system to be reused, the following process of abstract encapsulation of these reusable business modules to generate reusable encapsulation modules is crucial to ensure the portability and wide applicability of the modules. First, the internal structure and operation mechanism of each reusable business module are deeply analyzed; professional code analysis tools and techniques are used to accurately extract the core functional logic of the module and related interface configuration information; the functional logic is the key code part of the module to implement specific business functions, and the interface configuration defines the interaction between the module and the external system. Then, the extracted functional logic is carefully analyzed to identify and strip out the parts that are strongly coupled with the specific business scenarios, retaining its general and reusable logical core; through programming techniques such as abstract classes and interfaces, the common and variable parts in the functional logic are separated, thereby forming a reusable functional logic with high flexibility and scalability; the purpose of this step is to ensure that the encapsulated modules can be reused in different business scenarios without a lot of custom development work. At the same time, the extracted interface configuration is reviewed in detail to ensure that it complies with the common interface specifications and standards of the industry; necessary adjustments and optimizations are made to interfaces that do not meet the standards, such as unified parameter naming specifications, data types, error handling mechanisms, etc.; through standardization, the interoperability and compatibility of reused encapsulation modules can be significantly improved, and the complexity of integration and maintenance can be reduced. After completing the abstraction of functional logic and the standardization of interface configuration, these elements are integrated together to form a complete reused encapsulation module. Use appropriate encapsulation technology (such as classes and objects in object-oriented programming) to ensure that the internal implementation details of the module are transparent to the outside, while providing clear and consistent interfaces for external calls. The encapsulated module should have good encapsulation, inheritance, and polymorphism to adapt to different application requirements and changes.
[0037] In one embodiment of the present application, after the reusable service module in the system to be reused is identified, the original configuration data of the reusable service module is also generalized.
[0038] Specifically, identify specific business configuration information and / or specific permission configuration information in the original configuration data; generalize the specific business configuration information and / or specific permission configuration information to replace them with general placeholders or variables; and form generalized data based on the general information in the original configuration data and the generalized specific business configuration information and / or specific permission configuration information.
[0039] In one embodiment, after successfully identifying the reusable business modules in the system to be reused, the original configuration data of these modules is generalized. The purpose is to ensure that the modules can adapt to different business scenarios and permission requirements during the reuse process, while protecting the privacy and security of the original business data. First, the original configuration data of the reusable business modules is deeply analyzed, which usually includes database connection information, business rule parameters, user permission settings, etc. Using data parsing technology, specific business configuration information and specific permission configuration information in the original configuration data are automatically identified. These information are usually associated with specific business logic or specific user groups, such as a specific business process rule of a certain customer, access rights of a specific role, etc. Then, the identified specific business configuration information and specific permission configuration information are generalized. This means replacing these specific information with general placeholders or variables. For example, a specific customer name can be replaced with a placeholder such as "{CLIENT_NAME}", or a specific permission code can be replaced with a variable such as "{ROLE_PERMISSION}". Generalization processing aims to remove business specificity and permission specificity in the configuration data so that it can adapt to a wider range of scenarios and needs. Finally, after the generalization process is completed, the general information in the original configuration data is combined with the generalized specific business configuration information and / or specific permission configuration information to form new generalized data. General information may include database structure definition, general business rules, etc., which are the same for all business scenarios and therefore do not need to be generalized. Generalized data retains the structure of the original configuration data, but removes information related to specific businesses and permissions, thereby improving the versatility and reusability of the data.
[0040] Furthermore, after generalizing the original configuration data of the reusable service module, it is also necessary to generate module prefabricated data for the obtained generalized data according to the reuse requirements.
[0041] Specifically, the reuse requirement is obtained; wherein the reuse requirement includes target data of the target project, and the target data includes target business configuration information and target right configuration information; according to the reuse requirement, the corresponding data in the generalized data is replaced with the target data to form module prefabricated data of the target project in combination with the general data.
[0042] In one embodiment, after the original configuration data of the reusable business module is generalized, in order to ensure that the module can be reused smoothly in the new target project and meet specific requirements, it is necessary to generate module prefabricated data for the obtained generalized data according to the reuse requirements. This process involves replacing the placeholders or variables in the generalized data with the specific data required by the target project. The reuse requirements include the target data of the target project, which are mainly divided into two categories: target business configuration information and target authority configuration information. The target business configuration information may involve specific business processes, rule parameters, etc.; the target authority configuration information may include user roles, access rights, etc. After obtaining the reuse requirements, the corresponding target data is prepared according to the reuse requirements. These data should match the placeholders or variables in the generalized data for subsequent replacement operations. Then, a special data replacement tool or script is used to replace the corresponding data in the generalized data (such as placeholders "{CLIENT_NAME}" or variables, etc.) with specific values in the target data. During the replacement process, the structure and format of the data should be kept unchanged to ensure the compatibility and readability of the data. After the replacement is completed, the common data and the replaced target data are combined to form the module prefabricated data of the target project. These prefabricated data will serve as the initial configuration for the module to run in the new project.
[0043] In one embodiment of the present application, after abstractly encapsulating the reusable business module to generate a reusable encapsulation module, the method also includes: constructing a function extension form of the reusable encapsulation module so that the reusable encapsulation module can select additional special business functions based on the function extension form.
[0044] Specifically, the applicable business type corresponding to the reused encapsulation module is determined, and based on the applicable business type, the adapted extended form item is matched in the preset extended form library; wherein the extended form item and its corresponding extended function logic are mutually associated; the corresponding function prefabricated data is preset in the extended function logic; and the function extended form of the reused encapsulation module is generated based on the adapted extended form item.
[0045] In one embodiment, in order to further enhance the flexibility and scalability of the reuse encapsulation module, the embodiment of the present application also introduces the construction process of the function extension form, which allows users or developers to select additional special business functions for the reuse encapsulation module according to actual needs. First, the business characteristics and application scenarios of the reuse encapsulation module are deeply analyzed to clarify its applicable business types, which may include but are not limited to e-commerce, financial services, logistics management, online education, etc.; the purpose of this step is to ensure that the subsequent functional expansion is closely related to the core business of the reuse encapsulation module. Then, based on the determined applicable business types, the adaptive extended form items are searched and matched in the preset extended form library; wherein, the extended form library is a pre-built collection of form items related to various business types, and each extended form item is closely associated with its corresponding extended function logic, ensuring that the corresponding functional expansion can be smoothly realized after the form item is selected. Once the adaptive extended form item is matched, the system will automatically associate the extended function logic corresponding to these form items, and the corresponding functional prefabricated data are preset in the extended function logic, which are the initial configuration or parameters required to realize the characteristic business functions. For example, if the selected extension form item is "online payment", the corresponding extension function logic may include the configuration of the payment interface, the processing of the payment process, etc., and the function prefabricated data may include the default settings of the payment method, the payment limit, etc. Further, according to the matched adaptation extension form items, the system automatically generates a function extension form for the reuse encapsulation module. This form is presented in a user-friendly way, allowing users or developers to select or configure the required special business functions according to actual needs. Users can customize their own reuse encapsulation modules by checking, filling in or selecting to meet specific business needs.
[0046] Step 103: When it is necessary to release functions to the system to be reused, the reuse encapsulation module is configured based on the module prefabricated data to generate a business function module to be released.
[0047] In one embodiment of the present application, when it is necessary to release functions to the system to be reused, we will configure the reuse encapsulation module based on the module prefabricated data to generate the business function module to be released. This process ensures the rapid and accurate deployment of new functions while reducing the risks and complexity of the release process.
[0048] Step 104: Publish the business function modules to be published.
[0049] In one embodiment of the present application, after publishing the business function module to be released, the method also includes: monitoring the operating status of the business function module to be released, and collecting operating data in real time; based on the operating data, performing performance analysis and generating optimization suggestions for the business function module to be released; wherein the performance analysis includes response time analysis, resource occupancy analysis, and error rate analysis; the optimization suggestions include adjustment strategies for performance bottlenecks, resource allocation optimization suggestions, and error handling and prevention suggestions.
[0050] In one embodiment, after publishing the business function module to be released, the embodiment of the present application also takes monitoring and optimization measures. Specifically, professional monitoring tools are deployed to monitor the operating status of the business function module to be released in real time. These tools can capture and record various key indicators during the operation of the module, such as response time, CPU and memory occupancy, network bandwidth usage, etc. The real-time collected operation data is stored in a central database for subsequent performance analysis and generation of optimization suggestions. Performance analysis includes response time analysis, resource occupancy analysis, and error rate analysis. Among them, response time analysis: by analyzing the operation data, the average response time, maximum response time, and response time distribution of the business function module to be released are calculated to identify possible delays or bottlenecks; resource occupancy analysis: the occupancy of computing resources (such as CPU, memory) and network resources by the evaluation module during operation to determine whether there is a problem of over-consumption or unreasonable allocation; error rate analysis: statistics and analysis of the types and frequencies of errors that occur during the operation of the module, and identify common error patterns and potential causes. Optimization suggestions include adjustment strategies for performance bottlenecks, resource allocation optimization suggestions, error handling and prevention suggestions. Among them, adjustment strategies for performance bottlenecks: Based on the results of response time analysis and resource occupancy analysis, specific adjustment strategies are proposed, such as optimizing code logic, reducing unnecessary database queries, introducing cache mechanisms, etc., to reduce response time and reduce resource consumption; resource allocation optimization suggestions: According to resource occupancy, a reasonable resource allocation plan is proposed to ensure that each business function module can obtain sufficient resources while avoiding resource waste; error handling and prevention suggestions: Combined with the results of error rate analysis, targeted error handling mechanisms are formulated, such as enhancing exception capture and logging functions, so as to locate and solve problems more quickly. At the same time, preventive measures are proposed, such as improving code quality and strengthening test coverage, to reduce the probability of future errors.
[0051] In one embodiment of the present application, the method further includes: building a version management mechanism for the reused encapsulation module and the business function module to be released; recording the released version each time a function is released, and performing function and performance testing on each version.
[0052] The above is an embodiment of the method proposed in this application. Based on the same inventive concept, the embodiment of this application also provides a business function automatic publishing device based on module reuse, and its structure is as follows: Figure 2 shown.
[0053] Figure 2 A schematic diagram of the internal structure of a device for automatically publishing business functions based on module reuse provided in an embodiment of the present application. Figure 2 As shown, the device includes:
[0054] at least one processor 201;
[0055] and, a memory 202 communicatively connected to the at least one processor;
[0056] The memory 202 stores instructions that can be executed by at least one processor, and the instructions are executed by at least one processor 201 to enable at least one processor 201 to:
[0057] Analyze the system to be reused to identify the reusable business modules in the system to be reused;
[0058] Abstractly encapsulate the reusable business module to generate a reusable encapsulation module, and generalize the original configuration data of the reusable business module to generate module prefabricated data for the obtained generalized data according to the reuse requirements;
[0059] When it is necessary to release functions to the reused system, the reuse encapsulation module is configured based on the module prefabricated data to generate the business function module to be released;
[0060] Release the business function modules to be released.
[0061] Some embodiments of the present application provide corresponding Figure 1 A non-volatile computer storage medium for automatically publishing business functions based on module reuse, storing computer executable instructions, wherein the computer executable instructions are set as:
[0062] Analyze the system to be reused to identify the reusable business modules in the system to be reused;
[0063] Abstractly encapsulate the reusable business module to generate a reusable encapsulation module, and generalize the original configuration data of the reusable business module to generate module prefabricated data for the obtained generalized data according to the reuse requirements;
[0064] When it is necessary to release functions to the reused system, the reuse encapsulation module is configured based on the module prefabricated data to generate the business function module to be released;
[0065] Release the business function modules to be released.
[0066] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the IoT device and medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.
[0067] The system and medium provided in the embodiments of the present application correspond one-to-one to the method. Therefore, the system and medium also have similar beneficial technical effects to the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the system and medium will not be repeated here.
[0068] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.
[0069] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0070] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0071] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0072] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0073] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.
[0074] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.
[0075] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.
[0076] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims
1. A method for automatically publishing business functions based on module reuse, characterized in that: The method comprises: Parsing the system to be multiplexed to identify the reusable service modules in the system to be multiplexed; Abstractly encapsulating the reusable business module to generate a reuse encapsulation module, and generalizing the original configuration data of the reusable business module to generate module prefabricated data for the obtained generalized data according to reuse requirements; In the case where it is necessary to publish functions to the system to be reused, the reuse encapsulation module is configured based on the module prefabricated data to generate a business function module to be published; Release the business function module to be released.
2. According to the method for automatically publishing business functions based on module reuse according to claim 1, it is characterized in that: Parsing the system to be multiplexed to identify the reusable service modules in the system to be multiplexed, specifically including: Performing a logical independence test and a reusability evaluation on each service module in the system to be reused, so as to determine service modules that meet the logical independence requirements and the reusability evaluation results of each service module; Among the business modules that meet the logical independence requirements, the business modules whose reuse possibility evaluation results are greater than a preset threshold are selected as reusable business modules.
3. The method for automatically publishing business functions based on module reuse according to claim 1 is characterized in that: Abstract encapsulation of the reusable service module to generate a reusable encapsulation module specifically includes: Extracting the functional logic and interface configuration of the reusable business module; Abstracting the functional logic to form a reusable functional logic, and standardizing the interface configuration to form a standardized interface; The reusable functional logic and the standardized interface are encapsulated into a multiplexing encapsulation module.
4. The method for automatically publishing business functions based on module reuse according to claim 1 is characterized in that: The original configuration data of the reusable service module is generalized, specifically including: Identifying specific service configuration information and / or specific authority configuration information in the original configuration data; Generalizing the specific service configuration information and / or the specific permission configuration information to replace them with general placeholders or variables; Generalized data is formed based on the general information in the original configuration data and the generalized specific service configuration information and / or the specific authority configuration information.
5. The method for automatically publishing business functions based on module reuse according to claim 4 is characterized in that: According to the reuse requirements, the obtained generalized data is used to generate module prefabricated data, including: Acquire the reuse requirement; wherein the reuse requirement includes target data of the target project, and the target data includes target business configuration information and target right configuration information; According to the reuse requirement, the corresponding data in the generalized data is replaced with the target data to form module prefabricated data of the target project in combination with the general data.
6. The method for automatically publishing business functions based on module reuse according to claim 1, characterized in that: After abstracting and encapsulating the reusable service module to generate a reusable encapsulation module, the method further includes: Constructing a function extension form of the multiplexing encapsulation module so that the multiplexing encapsulation module can select additional special business functions based on the function extension form, specifically including: Determine the applicable business type corresponding to the multiplexing encapsulation module, and match the adapted extended form item in the preset extended form library based on the applicable business type; wherein the extended form item and its corresponding extended function logic are mutually associated; and the corresponding function prefabricated data are preset in the extended function logic; A function extension form of the multiplexing encapsulation module is generated based on the adapted extension form items.
7. The method for automatically publishing business functions based on module reuse according to claim 1 is characterized in that: After publishing the to-be-published business function module, the method further includes: Monitor the operating status of the business function module to be released and collect operating data in real time; Based on the operation data, a performance analysis is performed on the business function module to be released and optimization suggestions are generated; Among them, the performance analysis includes response time analysis, resource usage analysis, and error rate analysis; the optimization suggestions include adjustment strategies for performance bottlenecks, resource allocation optimization suggestions, and error handling and prevention suggestions.
8. The method for automatically publishing business functions based on module reuse according to claim 1, characterized in that: The method further comprises: Constructing a version management mechanism for the reused encapsulation module and the business function module to be released; Every time a feature is released, the release version is recorded and each version is tested for functionality and performance.
9. A business function automatic publishing device based on module reuse, characterized in that: The device comprises: at least one processor; and, a memory communicatively coupled to the at least one processor; The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: Parsing the system to be multiplexed to identify the reusable service modules in the system to be multiplexed; Abstractly encapsulating the reusable business module to generate a reuse encapsulation module, and generalizing the original configuration data of the reusable business module to generate module prefabricated data for the obtained generalized data according to reuse requirements; In the case where it is necessary to publish functions to the system to be reused, the reuse encapsulation module is configured based on the module prefabricated data to generate a business function module to be published; Release the business function module to be released.
10. A non-volatile computer storage medium for automatically publishing business functions based on module reuse, storing computer executable instructions, characterized in that: The computer executable instructions are configured to: Parsing the system to be multiplexed to identify the reusable service modules in the system to be multiplexed; Abstractly encapsulating the reusable business module to generate a reuse encapsulation module, and generalizing the original configuration data of the reusable business module to generate module prefabricated data for the obtained generalized data according to reuse requirements; In the case where it is necessary to publish functions to the system to be reused, the reuse encapsulation module is configured based on the module prefabricated data to generate a business function module to be published; Release the business function module to be released.