Method and system for providing cloud application, electronic equipment and medium

Abstract

The invention provides a method and system for providing a cloud application, electronic equipment and a storage medium, and aims to solve the problems that the cloud application is weak in universality and low in configurability and cannot provide customized cloud application services for enterprises, and the method comprises the following steps: obtaining various program components developed according to cloud demands of users, product categories to which the program components belong are distinguished; displaying different product categories for the cloud users for selection and use; assembling the program components of the same product category into a new application service according to the product category selected by the cloud user, and combining the application service into a new cloud product by carrying out personalized configuration on the business process; and publishing a new cloud product, and after the product is successfully published, automatically generating login information to provide cloud product service for a cloud user. According to the method and the device, the randomly assembled cloud service capability can be realized; and the plasticity, remoldability and freedom of the product are improved, and cloud services meeting the requirements of the user are provided for the user.

Description

Technical Field

[0001] This disclosure relates to the field of enterprise cloud technology, specifically to a method for providing cloud applications, a system for providing cloud applications, an electronic device, and a computer-readable storage medium. Background Technology

[0002] Small and medium-sized enterprises (SMEs) are numerous and play a crucial role in economic development. Compared to large enterprises, SMEs generally have lower investment and levels of IT infrastructure development. In recent years, more SMEs have been migrating to the cloud, but the extent and enthusiasm for this move are far lower than those of large enterprises. According to relevant surveys and data, the cloud adoption rate among SMEs is low; most are still operating under traditional IT infrastructure models, resulting in numerous information silos, outdated systems, and difficulties in meeting business needs. Faced with increasingly fierce market competition and a rapidly changing business environment, SMEs urgently need to improve their IT capabilities and enhance their overall competitiveness. Cloud adoption by SMEs has become an undeniable trend.

[0003] As cloud computing technology continues to advance, the technological trends for enterprises migrating to the cloud are also changing. Currently, the mainstream technologies used include virtualization, containerization, microservice architecture, and DevOps (a combination of Development and Operations). Furthermore, cloud-native applications and artificial intelligence have become major development directions for cloud computing technology.

[0004] The advantages of cloud adoption for enterprises are becoming increasingly apparent, and SMEs are constantly exploring and introducing cloud services to reduce their cost burden while ensuring normal operations and completing their digital transformation and upgrading tasks. However, cloud adoption also presents many challenges. For example, cloud users have diverse businesses, and while there are many cloud application services available, none are truly tailored to the specific needs of each enterprise. Currently, cloud products are marketed with standardized labels, but when enterprises want to optimize certain applications or processes, these services often do not support significant changes, meaning the system cannot achieve true loose coupling. Furthermore, there is a current lack of cloud service capabilities that can integrate all application systems, allowing for the segmentation and flexible assembly of applications. Summary of the Invention

[0005] To address at least the existing problems of weak universality, low configurability, and inability to provide customized cloud application services for enterprises, this disclosure provides a method, system, electronic device, and computer-readable storage medium for providing cloud applications. This method integrates all application systems, segments application programs, and enables freely assembled cloud service capabilities. It increases the product's flexibility, reconfigurability, and freedom, providing users with cloud services tailored to their specific needs.

[0006] Firstly, this disclosure provides a method for providing cloud applications, the method

[0007] include:

[0008] Acquire various program components developed based on users' cloud migration needs, and distinguish the product categories to which each program component belongs;

[0009] To showcase different product categories to cloud users for them to choose from;

[0010] Based on the product category selected by the cloud user, program components of the same product category are assembled into new application services, and the application services are combined into new cloud products by customizing the business process.

[0011] New cloud products are released, and login information is automatically generated after successful release to provide cloud product services to cloud users.

[0012] Furthermore, the acquisition of various program components developed based on users' cloud migration needs...

[0013] include:

[0014] Provide a dedicated development zone for R&D personnel, and define the components that R&D personnel can use through login permissions, so as to distinguish the permissions and development components used by different R&D personnel;

[0015] Account permissions and developer environments are assigned based on the R&D personnel's field of expertise, enabling R&D personnel to develop program components based on their understanding of enterprise cloud migration requirements or enterprise cloud migration requirements released by the system, and store them in the corresponding database according to the submitted product category;

[0016] Obtain the various program components developed.

[0017] Furthermore, the distinction of product categories to which each program component belongs includes:

[0018] Get the product category selected by the application component when submitting;

[0019] The code of the submitted program components is parsed and its corresponding product category is matched to analyze whether the code matches the product category.

[0020] If they match, then the product category to which the program component belongs is correct;

[0021] If they do not match, the code is returned to the developer so they can select a new product category and the code is checked again to see if it matches the new product category.

[0022] Furthermore,

[0023] The product categories are sequentially filtered through four levels: national industry, field, product direction, and product.

[0024] The above describes how different product categories are displayed for cloud users to choose from, including:

[0025] By displaying similar products in a list format, cloud users can select product categories based on their industry and needs.

[0026] Furthermore, based on the product category selected by the cloud user, program components of the same product category are assembled into new application services, and the application services are combined into new cloud products through personalized configuration of business processes, including:

[0027] Obtain the intended applications selected by cloud users based on the list of cloud applications displayed under similar products, as well as the application modules selected by users and the data fields involved;

[0028] Based on the selected intended application, the corresponding program components will be assembled into a new application service;

[0029] Without changing the data structure, the relevant data is filtered and reduced based on the data fields involved;

[0030] After data confirmation, the business process is configured, including: editing relevant information according to the selected application module, and providing a visual orchestration tool. On the orchestration steps page, based on the complete flowchart, all steps from the initiation to the end of the process are connected, and the application services are combined into a new cloud product.

[0031] Furthermore, upon successful release of the new cloud product, login information is automatically generated, including:

[0032] Once the new cloud products and business processes are combined, all selected code, business processes, and code will be deployed uniformly. Based on the cloud resources selected by the cloud users, the code will be deployed in the designated resource directory, and access links, login accounts, and passwords will be automatically generated and sent to the users through the system.

[0033] Furthermore, the method also includes:

[0034] Embedded code auditing tools automatically audit the code after developers upload it and output the audit results.

[0035] The audit report is matched with the code, and code audit issues are highlighted in the code as tags. This allows developers to review the code based on the audit results, and the code can only be stored in the corresponding database after the audit is passed.

[0036] Furthermore, the method also includes:

[0037] Check the submitted program components for code overlap;

[0038] If there are issues with high or moderate code overlap, the product is considered an existing product, and the program component is returned. After the return, the developers can re-edit and resubmit it, or the program component can be destroyed.

[0039] Secondly, this disclosure provides a system for providing cloud applications, the system comprising:

[0040] The acquisition module is configured to acquire various program components developed based on users' cloud migration needs and distinguish the product categories to which each program component belongs.

[0041] The display module is designed to showcase different product categories for cloud users to choose from.

[0042] The product generation module is configured to assemble program components of the same product category into new application services based on the product category selected by the cloud user, and combine the application services into new cloud products by customizing the business process.

[0043] The publishing module is set up to publish new cloud products. After successful product publishing, login information is automatically generated to provide cloud product services to cloud users.

[0044] Thirdly, this disclosure provides an electronic device including a memory and a processor, wherein the memory stores a computer program, and when the processor runs the computer program stored in the memory, the processor performs a method for providing cloud applications as described in any of the first aspects.

[0045] Fourthly, this disclosure provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method for providing cloud applications as described in any of the first aspects above.

[0046] Beneficial effects:

[0047] The methods, systems, electronic devices, and storage media for providing cloud applications disclosed herein can integrate all application systems, segment applications, and achieve freely configurable cloud service capabilities; improve the flexibility of cloud applications, reduce the coupling between the system and business processes, and increase the product's adaptability and reconfigurability.

[0048] Freedom, providing users with cloud services that meet their own needs. Attached Figure Description

[0049] Figure 1This is a flowchart illustrating a method for providing cloud applications according to Embodiment 1 of this disclosure;

[0050] Figure 2 A flowchart of a code review method provided in this embodiment of the disclosure;

[0051] Figure 3 This is an architecture diagram of a system for providing cloud applications, provided in Embodiment 2 of this disclosure;

[0052] Figure 4 This is an architecture diagram of a system for providing cloud applications, provided in Embodiment 3 of this disclosure;

[0053] Figure 5 This is an architectural diagram of an electronic device provided in Embodiment 4 of this disclosure. Detailed Implementation

[0054] To enable those skilled in the art to better understand the technical solutions of this disclosure, the disclosure will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments and drawings described herein are merely for explaining the invention and are not intended to limit the invention.

[0055] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence; furthermore, in the absence of conflict, the embodiments and features in the embodiments of this disclosure can be arbitrarily combined with each other.

[0056] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of this disclosure. The singular forms “a,” “the,” and “the” as used in the embodiments of this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0057] In the following description, the use of suffixes such as “module,” “part,” or “unit” to denote elements is solely for the purpose of illustrative purposes and has no specific meaning in itself. Therefore, “module,” “part,” or “unit” may be used interchangeably.

[0058] Currently, cloud-native applications and artificial intelligence have become the main development directions of cloud computing technology.

[0059] Cloud-native applications: Cloud-native applications are a cloud-based application development methodology. Their core concept is to consider the application and its infrastructure as a whole to improve application performance, reliability, and scalability. Currently, an increasing number of enterprises and organizations are adopting cloud-native applications to improve application delivery speed and reduce operational costs.

[0060] Artificial Intelligence (AI): AI is a key application area of ​​cloud computing technology. By performing large-scale computing and storage in the cloud, AI technology can analyze and process massive amounts of data, thereby providing users with more intelligent services. Currently, AI technology is widely used in various industries, such as natural language processing, image recognition, and intelligent recommendation.

[0061] However, existing technologies also present many problems for enterprises migrating to the cloud. For example, the businesses of enterprises migrating to the cloud are different, and there are many cloud application services, but none of them are completely suitable for the actual business of the enterprise.

[0062] The following detailed embodiments illustrate the technical solutions of this disclosure and how they solve the aforementioned problems in the prior art. It is understood that in the embodiments of this application, the executing entity may perform some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments of this application, and it is not necessary to execute all the operations in the embodiments of this application. Moreover, the following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0063] Figure 1 This is a flowchart illustrating a method for providing cloud applications according to Embodiment 1 of this disclosure, as shown below. Figure 1 As shown, the method includes:

[0064] Step S101: Obtain various program components developed according to users' cloud migration needs, and distinguish the product category to which each program component belongs;

[0065] Step S102: Show different product categories to cloud users for them to choose from;

[0066] Step S103: Based on the product category selected by the cloud user, assemble program components of the same product category into a new application service, and combine the application service into a new cloud product by customizing the business process.

[0067] Step S104: Publish the new cloud product. After successful product publication, login information will be automatically generated to provide cloud product services to cloud users.

[0068] Enterprise cloud adoption refers to deploying an enterprise's basic systems, business operations, and platforms to the cloud via high-speed interconnection networks. This allows enterprises to conveniently access computing, storage, data, and application services, which helps reduce the cost of enterprise IT infrastructure development, build an innovative industrial internet ecosystem, promote the optimization of the entire manufacturing process, the entire industrial chain, and the entire product lifecycle, and enhance the level of integration between manufacturing and the internet.

[0069] Currently, cloud products are typically offered with standardized product labels. When enterprises want to optimize certain applications or processes, the services often don't support major changes and fail to match the enterprise's actual situation. To address this issue, this disclosure proposes a solution where the application is segmented, with each application module implementing its own function. Based on user selection, these modules are then assembled and their business processes configured, ensuring that the cloud application fully meets the user's needs and providing tailored services for their specific business requirements. Users of this disclosure can be enterprises, organizations, or individuals. First, they acquire program components developed based on their cloud migration needs and determine the product category (i.e., product classification) to which each component belongs. These program components are generated by developers through coding based on the specific needs of each enterprise, typically edited and delivered in minimal unit code, facilitating subsequent application service combination. Furthermore, this publicly disclosed cloud system can display different product categories for cloud users, providing them with product classification and selection. When cloud users choose to use a product, the application service functions of each software product are provided to them in a modular and visual manner. They can also combine the selected application modules, and after combination, configure the business processes between each module to personalize the business processes to suit their needs. Through personalized configuration of the business processes, a brand-new software product is packaged. After the product combination and process configuration are completed, the cloud-adopting enterprise can release the new product through this unit. After successful product release, login information is automatically generated to provide cloud product services to cloud users.

[0070] The embodiments disclosed herein can integrate all application systems, divide applications, and realize cloud service capabilities that can be assembled at will; improve the flexibility of cloud applications, reduce the coupling between the system and business and processes, increase the plasticity, reshaping and freedom of the product, and provide users with cloud services that meet their own needs.

[0071] Furthermore, the acquisition of various program components developed according to users' cloud migration needs includes:

[0072] Provide a dedicated development zone for R&D personnel, and define the components that R&D personnel can use through login permissions, so as to distinguish the permissions and development components used by different R&D personnel;

[0073] Account permissions and developer environments are assigned based on the R&D personnel's field of expertise, enabling R&D personnel to develop program components based on their understanding of enterprise cloud migration requirements or enterprise cloud migration requirements released by the system, and store them in the corresponding database according to the submitted product category;

[0074] Obtain the various program components developed.

[0075] This disclosed embodiment is a developer zone unit for R&D personnel. This unit focuses on the application development role itself, providing developers with a development environment and development components, encapsulating underlying technologies such as Docker and Kubernetes, and providing users with a visual operation interface, enabling traditional application development teams to seamlessly transform into cloud-native digital application development teams. Before coding, developers can review and find suitable databases, middleware, AI and big data, and business groups to support rapid development.

[0076] R&D personnel log in to this unit using their registered accounts. During the registration phase, R&D personnel need to complete their technical field information. The system will allocate account permissions and developer environment based on the completed technical field information. At the same time, R&D personnel can develop programs based on their understanding of enterprise cloud migration needs, or they can develop programs according to the enterprise cloud migration needs published by the system. The enterprise cloud migration needs published by the system are obtained from different channels.

[0077] By segmenting the program and having dedicated R&D personnel develop corresponding program components, the complexity of product development can be reduced, maintainability and reusability can be improved, development costs can be reduced and development speed can be accelerated, and the system can be divided into different layers according to actual needs and changes. This reduces system coupling, enhances system scalability, facilitates module combination and decomposition, facilitates individual module function debugging and upgrades, and supports multi-person collaboration without interference.

[0078] Furthermore, the distinction of product categories to which each program component belongs includes:

[0079] Get the product category selected by the application component when submitting;

[0080] The code of the submitted program components is parsed and its corresponding product category is matched to analyze whether the code matches the product category.

[0081] If they match, then the product category to which the program component belongs is correct;

[0082] If they do not match, the code is returned to the developer so they can select a new product category and the code is checked again to see if it matches the new product category.

[0083] Product categories are defined data tags. After the code passes through the developer zone, developers can independently select product category tags. Once selected, AI technology is used to analyze the submitted code and product category. The AI ​​interprets the code and analyzes whether it matches the product category; mismatched code is rejected, and developers must reselect a product category. By determining the product category of program components, it's easy to assemble program components of the same product category into new application services, and to combine program components with corresponding functions into application modules with specific functions.

[0084] The process of using AI to interpret and audit code, such as Figure 2 The diagram illustrates a scenario for the code inspection process, which involves four steps: original code, code features, training model, and code auditing.

[0085] The S201 source code is submitted by R&D personnel and stored in the corresponding library according to the product category. The source code serves as the source data, and it cannot be modified or deleted. After the source code is stored, this module performs feature verification on the category to which the source code belongs.

[0086] S202 code characteristics, including code comment attributes, main / branch business process definitions, business data fields, and other multi-dimensional analysis, will be used to match the judgment results with the storage category to determine whether the code should be included in this product category. If a mismatch occurs, the code needs to be stored in another category library. The original code in the original category will not be deleted, but it will be hidden in this category and will not be queried by front-end users. This type of original data will be cleaned up periodically, and the time limit will depend on the situation. This is for the purpose of tracing code issues.

[0087] The S203 training model is designed for code recognition training scenarios. It identifies and classifies massive amounts of product data based on features. This data has been accumulated over a long period, and data recognition experience has been summarized. The recognition features are also regularly improved, continuously refining the feature points to achieve higher classification accuracy. In addition, the code recognition dimension verifies the completeness of submitted code and implements automatic business verification through deployed products. This verification uses business process diagrams and data flow diagrams provided by developers during release as references. Through long-term verification, the code verification conditions are continuously enriched, thus implementing a code verification training mechanism.

[0088] S304 code auditing, or source code auditing service, aims to fully uncover security and regulatory flaws in current code. This allows developers to understand the potential threats their applications may face and guides them in correctly fixing these defects. Two important vulnerability discovery techniques are source code auditing and fuzzing. Source code auditing uses static analysis of the program's source code to identify security issues, while fuzzing executes the test code and constructs various types of data to determine if the code processes the data correctly, thus revealing potential security problems.

[0089] Furthermore,

[0090] The product categories are sequentially filtered through four levels: national industry, field, product direction, and product.

[0091] The above describes how different product categories are displayed for cloud users to choose from, including:

[0092] By displaying similar products in a list format, cloud users can select product categories based on their industry and needs.

[0093] Cloud users can select product categories in the system based on their industry and needs. Product categories are filtered according to four levels: national industry, field, product direction, and product. Users can drill down to each level, and similar products are displayed in a list, providing precise services for cloud-based enterprises.

[0094] Furthermore, based on the product category selected by the cloud user, program components of the same product category are assembled into new application services, and the application services are combined into new cloud products through personalized configuration of business processes, including:

[0095] Obtain the intended applications selected by cloud users based on the list of cloud applications displayed under similar products, as well as the application modules selected by users and the data fields involved;

[0096] Based on the selected intended application, the corresponding program components will be assembled into a new application service;

[0097] Without changing the data structure, the relevant data is filtered and reduced based on the data fields involved;

[0098] After data confirmation, the business process is configured, including: editing relevant information according to the selected application module, and providing a visual orchestration tool. On the orchestration steps page, based on the complete flowchart, all steps from the initiation to the end of the process are connected, and the application services are combined into a new cloud product.

[0099] Combining the product list, cloud users can select all similar products and open the displayed list of cloud applications. Based on the application descriptions, users can choose their desired applications and assemble them into corresponding application service functions using relevant program components, such as user management, decision management, and business approval. Multiple selections are allowed, and after completion, the selected applications can be combined to generate new cloud products. The newly generated cloud product workflow can be configured to accommodate scenarios where each cloud-migrating enterprise has different business processes and selected application modules.

[0100] Each application service function is independent. These independent application service functions are linked through process configuration to form a brand-new cloud product. The configuration process includes data flow and business flow. In the data flow, the user selects a pre-developed application module. The application module is a pre-set, relatively standard application service function. The application module involves data fields, and the data is filtered and reduced while keeping the data structure unchanged. A data visualization module is provided to operate on data items. After the data is confirmed, the business flow configuration item is set, and the time flow configuration item in this item is bound to the business module. To achieve business flow assembly, after modular selection, the business flow is automatically filtered and assembled. Due to different products, there may be process mismatch issues or uncertainties in detailed processes. This process can automatically remind users and allow for actual user intervention and adjustment. By providing a visual configuration interface, it fully meets the needs of simple configuration. The business configuration process is divided into: defining steps and orchestrating the process. First, define the steps. Select the corresponding application module and edit basic information, forms, and approval items, including: step name, executor, time limit, step description, and approvers. The workflow orchestration tool provides a visual orchestration interface. On the workflow orchestration page, you can see a complete flowchart connecting all steps within the workflow from initiation to termination. All data in the configuration items is obtained from the data flow.

[0101] By assembling application services and configuring processes, we can solve the problem that users in the same industry have different business processes due to different sizes, and cannot use similar standardized products or achieve complete standardization. They can release an application that is more suitable for themselves by assembling it themselves.

[0102] After the business process editing is completed, the entire business module and business process will be validated. The validation methods include: Figure 2 The AI ​​code auditing capability was used to complete the configuration of the application modules.

[0103] Furthermore, upon successful release of the new cloud product, login information is automatically generated, including:

[0104] Once the new cloud products and business processes are combined, all selected code, business processes, and code will be deployed uniformly. Based on the cloud resources selected by the cloud users, the code will be deployed in the designated resource directory, and access links, login accounts, and passwords will be automatically generated and sent to the users through the system.

[0105] Releasing a new cloud product means uniformly deploying all selected code, business processes, and code, and deploying them in a designated resource directory according to the cloud resources selected by the enterprise.

[0106] When releasing a product to the cloud, the configured application modules and processes must be integrated with the code for final verification. Once verification is complete, the product can be released. Release refers to redeploying the code to the cloud environment; this product can only be viewed and used by the enterprise with that configuration. During the release process, a new formal environment resource configuration can be requested, and the environment can be built according to actual business needs. Resources can be expanded based on business volume to complete the environment setup. The following steps can be completed uniformly during this process: selecting a cloud platform, creating cloud resources, configuring the environment, deploying the application, testing and verification, monitoring, and maintenance. Selecting a cloud platform: Choose a suitable cloud platform based on your needs and conditions, such as AWS, Azure, GCP, etc. Different cloud platforms provide different services and functions; choosing the right cloud platform is the foundation of deployment. Creating cloud resources: Create the required cloud resources on the selected cloud platform, such as virtual machines, storage, and networks. These cloud resources will be used to deploy applications and services. Configuring the environment: Configure the cloud resources to meet the requirements of the applications and services. This may involve installing the operating system, configuring the network, and installing software. Deploying applications and services: Deploy the applications and services to the cloud platform. This can be achieved by uploading code, installing software packages, and configuring parameters. Testing and Validation: After deployment, the application and services should be tested and validated to ensure they function correctly. This can include unit testing, performance testing, and security testing. Monitoring and Maintenance: After the application and services are officially launched, they need to be monitored and maintained to promptly identify and resolve issues. This can be achieved through log analysis, performance monitoring, and automated operations and maintenance.

[0107] When a product is launched on the cloud, an access link, login account, and password are automatically generated and sent to the user's email via the system.

[0108] Furthermore, the method also includes:

[0109] Embedded code auditing tools automatically audit the code after developers upload it and output the audit results.

[0110] The audit report is matched with the code, and code audit issues are highlighted in the code as tags. This allows developers to review the code based on the audit results, and the code can only be stored in the corresponding database after the audit is passed.

[0111] The more significant purpose of embedding code auditing tools is to review the code submitted by developers. This helps developers identify errors in their submitted code, saving them time in code verification. The embedded tool automatically audits the code after upload and outputs the audit results. This step breaks away from the conventional audit report model, matching the audit report with the code and highlighting audit issues in the code using tags. Developers can then review the code based on the audit results, ensuring the security of the source code. Code can only be submitted after passing the audit. After submission, a product category must be selected before proceeding to application module assembly. We recommend editing and delivering code in the smallest unit format to facilitate module combination within the application.

[0112] Furthermore, the method also includes:

[0113] Check the submitted program components for code overlap;

[0114] If there are issues with high or moderate code overlap, the product is considered an existing product, and the program component is returned. After the return, the developers can re-edit and resubmit it, or the program component can be destroyed.

[0115] To address the issue of high to moderate code overlap, which is considered an existing product, the product needs to be returned. After return, developers can either re-edit and resubmit, or destroy the product. This operation is to solve the problem of an excessive number of product code instances, resulting in a large workload. Therefore, this unit needs to be processed using multiple threads, and the processing results should be quickly categorized and colored to achieve a seamless and rapid processing experience for users.

[0116] This disclosed embodiment establishes a dedicated developer zone where product program components are first developed. Then, product configuration is completed through product categorization, application module assembly, and process configuration. Finally, the product is migrated to the cloud, providing service capabilities to end users. By breaking the product down into small, relatively independent modules, coupling and complexity between modules are reduced, making software development and maintenance easier and enabling freely assembleable cloud services. This increases the flexibility of cloud applications, reduces coupling between the system and business processes, and enhances the product's adaptability, reconfigurability, and freedom, providing users with cloud services tailored to their specific needs. Furthermore, AI technology is leveraged to provide automated verification capabilities in areas such as code auditing and business process verification, reducing human intervention and significantly increasing product security and development efficiency.

[0117] This disclosure also discloses a method for providing cloud applications, implemented through a system for providing cloud applications. The system mainly includes: a developer zone unit, a product classification unit, an application module library unit, a process configuration unit, and a product cloud deployment unit.

[0118] S1: Developer Zone Unit Implementation: Provides a development zone for R&D personnel, defines the content of components used by R&D personnel through login permissions, and distinguishes the different permissions and development components used by different R&D personnel.

[0119] S2: Product Category Unit Implementation: This feature displays different product categories for cloud-enabled enterprises within the system. These product categories are based on the cloud product partitions defined by the developers, providing cloud-enabled enterprises with a choice of product categories to use.

[0120] S3: Application Module Library Unit Implementation: This unit is a sub-partition of the product category. The application of each software product is provided to cloud enterprises in a modular and visual way. At the same time, the selected application modules can be combined, and after combination, they can be packaged into a brand-new software product through process configuration.

[0121] S4: Process Configuration Unit Implementation: After selecting the application module combination, enterprises can configure the business processes between each module in the process configuration unit to personalize the business processes that suit their own needs.

[0122] S5: Product Cloud Migration Unit Implementation: After the product portfolio and process configuration are completed, cloud-migrating enterprises can release new products through this unit. After successful product release, a login address, login account, and password are automatically generated to provide cloud product services to cloud-migrating enterprises.

[0123] In S1, the developer zone unit is a development entry point provided for R&D personnel. R&D personnel log in to this unit through their registered accounts. During the registration phase, R&D personnel need to complete their technical field. The system allocates account permissions and developer environment based on the complete field of the R&D personnel. At the same time, R&D personnel can develop programs based on their understanding of enterprise cloud migration needs, or they can develop according to the enterprise cloud migration needs published by the system. The enterprise cloud migration needs published by the system are obtained from different channels.

[0124] In S2, the application module library unit provides application services for cloud-based enterprises. Cloud-based enterprises select product categories in the system based on their own industry and needs. Product categories are filtered according to four levels: national industry, field, product direction, and product, and drill down level by level. Similar products are displayed in a list, providing precise services for cloud-based enterprises.

[0125] In step S3, combined with the product list in S2, cloud-adopting enterprises can select all similar products and open the list of cloud applications. Based on the application descriptions, enterprises can select their desired applications. This unit allows for multiple selections, and after multiple selections are completed, the selected applications are combined to generate new cloud products.

[0126] In S4, the newly generated cloud product process is configured, which can realize scenarios where the business processes and selected application modules of each cloud enterprise are different.

[0127] In S5, after the new product and business process are combined, they are released through this unit. This release action refers to the unified deployment of all selected code, business processes and code, which are deployed in the designated resource directory according to the cloud resources selected by the cloud-going enterprise. At the same time, access links, login accounts and passwords are automatically generated and sent to the user's email through the system.

[0128] The system architecture diagram is as follows: Figure 3 As shown, the functions of each unit are explained in more detail below:

[0129] The S101 Developer Zone unit focuses on the application development role itself, providing developers with development environments and components, encapsulating underlying technologies such as Docker and Kubernetes, and offering a visual operation interface to enable traditional application development teams to seamlessly transform into cloud-native digital application development teams. Before coding, developers should review and identify suitable databases, middleware, AI and big data, and business groups to support rapid development. More importantly, this unit audits developers' code, highlighting errors and saving developers time in verification. An embedded code auditing tool automatically audits the uploaded code and outputs the results. This step breaks the conventional audit report model, matching the audit report with the code and highlighting audit issues in the code using tags. Developers review the audit results, ensuring source code security. Submission is only allowed after the audit is passed, and after submission, a product category must be selected before entering the application module library unit. The recommended minimum unit for code editing and delivery facilitates module combination in the S103 application module library unit.

[0130] The S102 Product Category Unit is primarily responsible for distinguishing the product category to which the code belongs. Product categories are predefined data tags. After the code passes through the Developer Zone unit, developers independently select product category tags. Once selected, AI technology is used to analyze the submitted code and product category. The AI ​​auditing process is as follows: Figure 2The key significance of this unit is to use AI to interpret the code, analyze whether the code matches the product category, and identify any code overlap (including high and moderate overlap). For mismatched code products, a rollback operation is performed, after which developers need to reselect the product category. For high and moderate code overlap issues, the product is identified as an existing product and needs to be rolled back. After rollback, developers can either re-edit and submit it again, or destroy the product. This operation addresses the issue of an excessive number of product codes, resulting in a large workload. Therefore, this unit requires multi-threading and rapid color-coding of the processing results to achieve a seamless and fast processing experience for users.

[0131] The S103 Application Module Library unit modularizes applications of similar products, assembling code from the same product categories into new application service functions. This unit addresses the issue of users in the same industry experiencing business process differences due to varying scales, making it impossible to use standardized products or achieve complete standardization. It allows for the release of an application more suited to the user's specific needs through flexible assembly. Users can select pre-developed application modules. These modules involve data fields, and this process filters and reduces the data while maintaining the original data structure. A data visualization module is provided to manipulate data items. After data confirmation, business process configuration items are set. The time-based process configuration item is bound to the business module. Combined with the S104 Process Configuration unit, the business process is edited. After editing, the entire business module and process are validated using the following methods: Figure 2 The AI ​​code auditing capability was used to complete the configuration of the application modules.

[0132] The S104 process configuration unit assembles business processes. Through modular selection, business processes are automatically filtered and assembled. Due to product differences, process mismatches or uncertainties in detailed processes may arise. This unit can automatically remind users and allow for user intervention. This module provides a visual configuration interface, fully meeting simple configuration needs. The process configuration in this unit is divided into: defining steps and orchestrating processes. First, defining steps requires selecting the corresponding application module and editing basic information, forms, and approval items, including: step name, executor, time limit, step description, and approvers. A visual orchestration tool is provided; on the orchestration page, a complete flowchart is displayed, connecting all steps within the process from initiation to termination. All data in the configuration items is obtained from the S103 unit.

[0133] The S105 product cloud deployment unit is the unit released after the above configurations are completed. During product cloud deployment, this unit performs final verification of the configuration modules, process integration code, etc. Once verification is complete, the product can be released. Deployment refers to redeploying the code to the cloud environment. This product can only be viewed and used by the enterprise with this configuration. In this unit, you can reapply for formal environment resource configuration and build the environment according to actual business needs. Resources can be expanded according to business volume to complete the environment setup. This unit allows you to uniformly complete the following steps: selecting a cloud platform, creating cloud resources, configuring the environment, deploying applications, testing and verification, monitoring, and maintenance. Selecting a cloud platform: Choose a suitable cloud platform based on your needs and conditions, such as AWS, Azure, GCP, etc. Different cloud platforms provide different services and functions; choosing the right cloud platform is the foundation of deployment. Creating cloud resources: Create the required cloud resources on the selected cloud platform, such as virtual machines, storage, and networks. These cloud resources will be used to deploy applications and services. Configuring the environment: Configure the cloud resources to meet the requirements of the applications and services. This may involve installing the operating system, configuring the network, and installing software. Deploying applications and services: Deploy the applications and services to the cloud platform. This can be achieved by uploading code, installing software packages, and configuring parameters. Testing and Verification: After deployment, the application and services are tested and verified to ensure they function correctly. This can include unit testing, performance testing, and security testing. Monitoring and Maintenance: After the application and services are officially launched, they need to be monitored and maintained to promptly identify and resolve issues. This can be achieved through log analysis, performance monitoring, and automated operations and maintenance.

[0134] The following is for reference. Figure 2 This provides a detailed description of a scenario for the code inspection process. This scenario involves four steps: original code, code features, model training, and code auditing.

[0135] The S201 source code is submitted by R&D personnel and stored in the corresponding library according to the product category. The source code serves as the source data, and it cannot be modified or deleted. After the source code is stored, this module performs feature verification on the category to which the source code belongs.

[0136] S202 code characteristics, including code comment attributes, main / branch business process definitions, business data fields, and other multi-dimensional analysis, will be used to match the judgment results with the storage category to determine whether the code should be included in this product category. If a mismatch occurs, the code needs to be stored in another category library. The original code in the original category will not be deleted, but it will be hidden in this category and will not be queried by front-end users. This type of original data will be cleaned up periodically, and the time limit will depend on the situation. This is for the purpose of tracing code issues.

[0137] The S203 training model is designed for code recognition training scenarios. It identifies and classifies massive amounts of product data through features. This data has been accumulated over a long period, and data recognition experience has been summarized. The recognition features are also regularly improved, continuously refining the feature points to achieve higher classification accuracy. In addition, the code recognition dimension verifies the completeness of submitted code and implements automatic business verification through deployed products. This verification uses business process diagrams and data flow diagrams provided by developers during release as references. Through long-term verification, the code verification conditions are continuously enriched, thus implementing a code verification training mechanism.

[0138] S304 code auditing, or source code auditing service, aims to fully uncover security and regulatory flaws in current code. This allows developers to understand the potential threats their applications may face and guides them in correctly fixing these defects. Two important vulnerability discovery techniques are source code auditing and fuzzing. Source code auditing uses static analysis of the program's source code to identify security issues, while fuzzing executes the test code and constructs various types of data to determine if the code processes the data correctly, thus revealing potential security problems.

[0139] This disclosed embodiment realizes the entire process of enterprise cloud migration, including research and development, configuration, release, and verification, and clarifies the overall operation process and mechanism. First, product development is completed in the developer zone. Then, product configuration is completed through product classification, application module library, and process configuration. Finally, the product is migrated to the cloud to provide service capabilities to end users. In terms of code auditing and business process verification, AI technology is also used to provide automated verification capabilities, saving manpower and greatly increasing the product's plasticity, reshaping, and flexibility.

[0140] Embodiment 3 of this disclosure also provides a system for providing cloud applications, such as Figure 4 As shown, the system includes:

[0141] The module 11 is configured to acquire various program components developed based on users' cloud migration needs and distinguish the product categories to which each program component belongs.

[0142] Display module 12 is configured to display different product categories for cloud users to choose from.

[0143] Product generation module 13 is configured to assemble program components of the same product category into new application services based on the product category selected by the cloud user, and combine application services into new cloud products by personalizing the business process.

[0144] The publishing module 14 is configured to publish new cloud products. After successful product publishing, login information is automatically generated to provide cloud product services to cloud users.

[0145] Furthermore, the acquisition module 11 is specifically configured as follows:

[0146] Provide a dedicated development zone for R&D personnel, and define the components that R&D personnel can use through login permissions, so as to distinguish the permissions and development components used by different R&D personnel;

[0147] Account permissions and developer environments are assigned based on the R&D personnel's field of expertise, enabling R&D personnel to develop program components based on their understanding of enterprise cloud migration requirements or enterprise cloud migration requirements released by the system, and store them in the corresponding database according to the submitted product category;

[0148] Obtain the various program components developed.

[0149] Furthermore, the acquisition module 11 is specifically configured as follows:

[0150] Get the product category selected by the application component when submitting;

[0151] The code of the submitted program components is parsed and its corresponding product category is matched to analyze whether the code matches the product category.

[0152] If they match, then the product category to which the program component belongs is correct;

[0153] If they do not match, the code is returned to the developer so they can select a new product category and the code is checked again to see if it matches the new product category.

[0154] Furthermore,

[0155] The product categories are sequentially filtered through four levels: national industry, field, product direction, and product.

[0156] The display module 12 is specifically configured as follows:

[0157] By displaying similar products in a list format, cloud users can select product categories based on their industry and needs.

[0158] Furthermore, the product generation module 13 is specifically configured as follows:

[0159] Obtain the intended applications selected by cloud users based on the list of cloud applications displayed under similar products, as well as the application modules selected by users and the data fields involved;

[0160] Based on the selected intended application, the corresponding program components will be assembled into a new application service;

[0161] Without changing the data structure, the relevant data is filtered and reduced based on the data fields involved;

[0162] After data confirmation, the business process is configured, including: editing relevant information according to the selected application module, and providing a visual orchestration tool. On the orchestration steps page, based on the complete flowchart, all steps from the initiation to the end of the process are connected, and the application services are combined into a new cloud product.

[0163] Furthermore, the publishing module 14 is specifically configured as follows:

[0164] Once the new cloud products and business processes are combined, all selected code, business processes, and code will be deployed uniformly. Based on the cloud resources selected by the cloud users, the code will be deployed in the designated resource directory, and access links, login accounts, and passwords will be automatically generated and sent to the users through the system.

[0165] Furthermore, the system also includes an audit module 15;

[0166] The audit module 15 is configured to embed a code auditing tool, which automatically audits the code after the developers have uploaded it and outputs the audit results; and,

[0167] The audit report is matched with the code, and code audit issues are highlighted in the code as tags. This allows developers to review the code based on the audit results, and the code can only be stored in the corresponding database after the audit is passed.

[0168] Furthermore, the audit module 15 is also configured as follows:

[0169] Check the submitted program components for code overlap;

[0170] If there are issues with high or moderate code overlap, the product is considered an existing product, and the program component is returned. After the return, the developers can re-edit and resubmit it, or the program component can be destroyed.

[0171] The system for providing cloud applications in this disclosure is used to implement the methods for providing cloud applications in Embodiment 1 and Embodiment 2, so the description is relatively simple. For details, please refer to the relevant descriptions in the previous method embodiments, which will not be repeated here.

[0172] In addition, such as Figure 5 As shown, Embodiment 4 of this disclosure also provides an electronic device, including a memory 100 and a processor 200. The memory 100 stores a computer program. When the processor 200 runs the computer program stored in the memory 100, the processor 200 executes the various possible methods described above.

[0173] The memory 100 is connected to the processor 200. The memory 100 can be a flash memory, a read-only memory, or another type of memory. The processor 200 can be a central processing unit or a microcontroller.

[0174] Furthermore, embodiments of this disclosure also provide a computer-readable storage medium storing a computer program, which is executed by a processor using the various possible methods described above.

[0175] The computer-readable storage medium includes volatile or non-volatile, removable or non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules or other data). Computer-readable storage media includes, but is not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other memory technologies, CD-ROM (Compact Disc Read-Only Memory), Digital Video Disc (DVD) or other optical disc storage, cartridges, magnetic tapes, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer.

[0176] It is understood that the above embodiments are merely exemplary embodiments used to illustrate the principles of this disclosure, and this disclosure is not limited thereto. For those skilled in the art, various modifications and improvements can be made without departing from the spirit and substance of this disclosure, and these modifications and improvements are also considered to be within the scope of protection of this disclosure.

Claims

1. A method for providing cloud applications, characterized in that, The method includes: Acquire various program components developed based on users' cloud migration needs, and distinguish the product categories to which each program component belongs; To showcase different product categories to cloud users for them to choose from; Based on the product category selected by the cloud user, program components of the same product category are assembled into new application services, and the application services are combined into new cloud products by customizing the business process. New cloud products are released, and login information is automatically generated after successful release to provide cloud product services to cloud users.

2. The method according to claim 1, characterized in that, The acquisition of various program components developed based on users' cloud migration needs includes: Provide a dedicated development zone for R&D personnel, and define the components that R&D personnel can use through login permissions, so as to distinguish the permissions and development components used by different R&D personnel; Account permissions and developer environments are assigned based on the R&D personnel's field of expertise, enabling R&D personnel to develop program components based on their understanding of enterprise cloud migration requirements or enterprise cloud migration requirements released by the system, and store them in the corresponding database according to the submitted product category; Obtain the various program components developed.

3. The method according to claim 2, characterized in that, The product categories to which each program component belongs include: Get the product category selected by the application component when submitting; The code of the submitted program components is parsed and its corresponding product category is matched to analyze whether the code matches the product category. If they match, then the product category to which the program component belongs is correct; If they do not match, the code is returned to the developer so they can select a new product category and the code is checked again to see if it matches the new product category.

4. The method according to claim 1, characterized in that, The product categories are sequentially filtered through four levels: national industry, field, product direction, and product. The above describes how different product categories are displayed for cloud users to choose from, including: By displaying similar products in a list format, cloud users can select product categories based on their industry and needs.

5. The method according to claim 4, characterized in that, The process of assembling program components of the same product category into new application services based on the product category selected by the cloud user, and combining these application services into new cloud products through personalized configuration of business processes, includes: Obtain the intended applications selected by cloud users based on the list of cloud applications displayed under similar products, as well as the application modules selected by users and the data fields involved; Based on the selected intended application, the corresponding program components will be assembled into a new application service; Without changing the data structure, the relevant data is filtered and reduced based on the data fields involved; After data confirmation, the business process is configured, including: editing relevant information according to the selected application module, and providing a visual orchestration tool. On the orchestration steps page, based on the complete flowchart, all steps from the initiation to the end of the process are connected, and the application services are combined into a new cloud product.

6. The method according to claim 1, characterized in that, The process involves releasing a new cloud-based product. Upon successful release, login information is automatically generated, including: Once the new cloud products and business processes are combined, all selected code, business processes, and code will be deployed uniformly. Based on the cloud resources selected by the cloud users, the code will be deployed in the designated resource directory, and access links, login accounts, and passwords will be automatically generated and sent to the users through the system.

7. The method according to claim 2, characterized in that, The method further includes: Embedded code auditing tools automatically audit the code after developers upload it and output the audit results. The audit report is matched with the code, and code audit issues are highlighted in the code as tags. This allows developers to review the code based on the audit results, and the code can only be stored in the corresponding database after the audit is passed.

8. The method according to claim 2, characterized in that, The method further includes: Check the submitted program components for code overlap; If there are issues with high or moderate code overlap, the product is considered an existing product, and the program component is returned. After the return, the developers can re-edit and resubmit it, or the program component can be destroyed.

9. A system for providing cloud applications, characterized in that, The system includes: The acquisition module is configured to acquire various program components developed based on users' cloud migration needs and distinguish the product categories to which each program component belongs. The display module is designed to showcase different product categories for cloud users to choose from. The product generation module is configured to assemble program components of the same product category into new application services based on the product category selected by the cloud user, and combine the application services into new cloud products by customizing the business process. The publishing module is set up to publish new cloud products. After successful product publishing, login information is automatically generated to provide cloud product services to cloud users.

10. An electronic device, characterized in that, It includes a memory and a processor, wherein the memory stores a computer program, and when the processor runs the computer program stored in the memory, the processor performs the method of providing cloud applications as described in any one of claims 1-8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method for providing cloud applications as described in any one of claims 1-8.

Images