SaaS platform development method, computer equipment and computer readable storage medium

Abstract

The invention relates to the technical field of computers, and discloses an SaaS (Software as a Service) platform development method, computer equipment, a computer readable storage medium and a computer program product in order to solve the problem of serious coupling between standard products and personalized codes during SaaS platform development. The method is applied to a web end, and comprises the following steps: generating a plug-in and a plug-in engine according to a service demand; the plug-in comprises a front-end UI code, a back-end service code, a configuration file and an SQL script file; the plug-in engine is used for managing the plug-in and providing a running environment of the plug-in; and loading a plug-in through the plug-in engine so as to integrate the customized part of the subsystem of the SaaS platform corresponding to the service demand. By adopting the method, the difference requirements of web end users can be met, and the development cost is saved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and more specifically, to a SaaS platform development method, a computer device, a computer-readable storage medium, and a computer program product. Background Art

[0002] At present, when developing SaaS platforms, different users may have different needs. Standard products cannot meet the specific requirements of all users, so additional codes and configuration items are generally added to standard products. However, the disadvantage of this method is that there is a serious coupling between standard products and personalized codes, the product code is bloated, and the coupling part cannot be clearly sorted out, which has a huge impact on subsequent code maintenance. Summary of the invention

[0003] In order to solve the problem of serious coupling between standard products and personalized codes during SaaS platform development, the present invention provides a SaaS platform development method, computer equipment, computer-readable storage medium and computer program product, which will meet the differentiated requirements of web users and save development costs.

[0004] To achieve the above object, according to a first aspect of the present invention, a SaaS platform development method is provided, which is applied to a web terminal, and the method comprises:

[0005] Generate plug-ins and plug-in engines according to business needs; plug-ins include front-end UI code, back-end service code, configuration files, and SQL script files; the plug-in engine is used to manage plug-ins and provide a running environment for plug-ins;

[0006] Plug-ins are loaded through the plug-in engine to integrate the customized parts of the subsystems of the SaaS platform corresponding to the business needs.

[0007] Furthermore, according to business needs, plug-ins are generated, including building project scripts and generating a web development framework; according to business needs, front-end UI code and back-end service code are generated; a new database folder is created, SQL script files are named according to the execution order, and all SQL script files are placed in the database folder; a new configuration folder is created, and all configuration files are placed in the configuration folder; a new xml configuration file is created, and the xml configuration file is used to describe the metadata of the plug-in; the front-end UI code, back-end service code, database folder, and configuration folder are written into the xml configuration file to generate a file in plug-in format.

[0008] Furthermore, the plug-in also includes a file compression tool, a file packaging tool, and a file encryption tool, which write the front-end UI code, the back-end service code, the database folder, and the configuration folder into the XML configuration file to generate the plug-in, including packaging the front-end UI code corresponding to the front-end project and the back-end service code corresponding to the back-end project through the file packaging tool, and putting the packaged files into the front-end project folder and the back-end project folder respectively; writing the front-end project folder, the back-end project folder, the database folder, and the configuration folder into the XML configuration file; compressing the written files through the file compression tool; calculating the signature value of the compressed file through the digest algorithm, and saving the signature value to the XML configuration file; symmetrically encrypting the compressed file through the file encryption tool, and saving the XML configuration file as a file in the plug-in format.

[0009] Furthermore, the plug-in engine includes a plug-in boot program and plug-in management; the plug-in boot program is used to automatically deploy, automatically configure, and execute at least one of plug-in SQL scripts; plug-in management includes at least one of plug-in storage, import / export, plug-in enabling and disabling, plug-in metadata viewing, and uploading plug-ins to the plug-in market.

[0010] Furthermore, the configuration files include Nacos configuration files, routing configuration files and k8s configuration files. The plug-ins are loaded through the plug-in engine, including executing all SQL script files; namespaces are created and Nacos configuration files are added or modified through the Http interface; Docker images are generated according to the compiled programs of the front-end and back-end, and uploaded to the intranet server; the front-end and back-end services are started through the kubectl command line tool provided by the container orchestration system; and the menu routes of the portal are bound according to the routing configuration of the xml configuration file.

[0011] Furthermore, the plug-in bootstrap is also used to decrypt and decompress the plug-in and execute all SQL script files, including decrypting and decompressing files in the plug-in format through a symmetric algorithm; calculating the signature value of each decompressed file through a digest algorithm, and comparing the signature value with the signature value in the plug-in generation step; when the two signature values ​​are the same, executing all SQL script files.

[0012] Furthermore, the above-mentioned SaaS platform development method also includes creating a portal, which is used to provide single sign-on, data permission interface, menu routing control, and enter the subsystem of the SaaS platform through the single sign-on portal; adding a plug-in engine to the portal.

[0013] According to a second aspect of the present invention, there is also provided a computer device, which includes a memory, a processor and a computer program stored in the memory, and the processor executes the computer program to implement the steps of any one of the above methods.

[0014] According to a third aspect of the present invention, there is also provided a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps of any of the above methods are implemented.

[0015] According to a fourth aspect of the present invention, there is also provided a computer program product, comprising a computer program, which implements the steps of any of the above methods when executed by a processor.

[0016] In general, the above technical solutions conceived by the present invention can achieve the following beneficial effects compared with the prior art:

[0017] (1) The SaaS platform development method provided by the present invention is applied to the web side, and generates plug-ins and plug-in engines according to business needs. The plug-ins are loaded through the plug-in engine to integrate the customized parts of the subsystems of the SaaS platform corresponding to the business needs. It can be applied to the web side project of the SaaS platform, and the metadata of the customized system is managed by plug-ins to meet the differentiated requirements of web side users, and users can reuse existing plug-ins. In addition, new functions can be added without changing the main code of the subsystem, avoiding large-scale customized development work and saving development costs.

[0018] (2) The SaaS platform development method provided by the present invention can realize standardized master data and corresponding interfaces by creating a portal, providing single sign-on, data permission interface, and menu routing control; and can reduce the coupling between subsystems by dividing the subsystems of the SaaS platform by business domains. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0020] Figure 1 A flowchart of a SaaS platform development method provided in an embodiment of the present application;

[0021] Figure 2 A structural block diagram of the plug-in development provided for the embodiment of the present application;

[0022] Figure 3A schematic diagram of the structure of the SaaS platform and its portal provided in the embodiment of the present application;

[0023] Figure 4 A schematic diagram of a process for implementing single sign-on provided in an embodiment of the present application;

[0024] Figure 5 A schematic diagram of the plug-in generation process provided in an embodiment of the present application;

[0025] Figure 6 A schematic diagram of the plug-in loading process provided in an embodiment of the present application;

[0026] Figure 7 A schematic diagram of the internal structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. In addition, the technical features involved in the various embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0028] The terms "first", "second", "third", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices.

[0029] like Figure 1 As shown, a SaaS platform development method is provided, which is applied to the web side. The method can be executed by a terminal or by a server that communicates with the terminal through a network. The terminal can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, etc. The server can be an independent server, or a server cluster composed of multiple servers can be used. Taking the method applied to the terminal as an example, it includes the following steps:

[0030] Step 101, generate a plug-in and a plug-in engine according to business needs; the plug-in includes front-end UI code, back-end service code, configuration files, and SQL script files; the plug-in engine is used to manage the plug-in and provide a running environment for the plug-in.

[0031] Among them, the business demand is determined according to the actual business demand, for example, it can be an invoice-related business demand.

[0032] Figure 2 This is a structural diagram of the plug-in development provided in the embodiment of the present application. Figure 2 As shown in the figure, plug-in development mainly includes two parts, one is the plug-in composition, and the other is the plug-in engine. The plug-in is to standardize the front-end UI code, back-end service code, configuration file, and SQL script file of the executable customized subsystem, compress it into a ZIP package, and encrypt it. The plug-in engine parses, deploys, and manages the plug-in.

[0033] The plugin engine is divided into two parts, namely the plugin bootstrap and the plugin manager. The plugin bootstrap is used to decompress, automatically deploy, automatically configure, and execute plugin SQL scripts. Plugin management mainly includes plugin storage, import / export, plugin enablement and disablement, plugin metadata viewing, plugin upload to the plugin market, plugin archiving, etc. Plugin automatic deployment can use the cloud native (k8s or k3s) container orchestration system to realize automatic deployment, expansion, and management of containerized applications. If the container orchestration system is not used, you need to implement the deployment and maintenance of the front-end and back-end programs by yourself through shell scripts. The plugin market mainly solves the problem of plugin reusability, and uploads plugins to the plugin market for users to use. That is, users can obtain plugins that meet their business needs from the plugin market without the need for developers to perform secondary development based on the user's business needs, so that plugins can be flexibly applied to other users.

[0034] Exemplarily, the steps for generating a plug-in are as follows:

[0035] S1. Build project scripts and generate web development framework;

[0036] S2. Generate front-end UI code and back-end service code according to business needs;

[0037] S3. Create a new database folder, name the SQL script files in the order of execution, and put all SQL script files into the database folder;

[0038] S4. Create a new configuration folder and put all configuration files into the configuration folder;

[0039] S5. Create a new XML configuration file, which is used to describe the metadata of the plug-in;

[0040] S6. Write the front-end UI code, back-end service code, database folder, and configuration folder into the XML configuration file to generate a file in plug-in format.

[0041] In one embodiment, the configuration file includes a Nacos configuration file and a k8s configuration file, and the configuration folder includes a nacos folder and a k8s folder. The above step S4, creates a new configuration folder, puts all configuration files into the configuration folder, includes creating a new nacos folder, and then creates a new Nacos configuration file therein, and names the Nacos configuration file according to the namespace; creates a new k8s folder, and puts the k8s-related configuration files into the k8s folder.

[0042] In one embodiment, the plug-in also includes a file compression tool, a file packaging tool, and a file encryption tool. The above step S6, writing the front-end UI code, the back-end service code, the database folder, and the configuration folder into the xml configuration file to generate the plug-in, includes packaging the front-end UI code corresponding to the front-end project and the back-end service code corresponding to the back-end project through the file packaging tool, and putting the packaged files into the front-end project folder and the back-end project folder respectively; writing the front-end project folder, the back-end project folder, the database folder, and the configuration folder into the xml configuration file; compressing the written files through the file compression tool; calculating the signature value of the compressed file through the digest algorithm, and saving the signature value to the xml configuration file; symmetrically encrypting the compressed file through the file encryption tool, and saving the xml configuration file as a file in the plug-in format.

[0043] Step 102 , loading the plug-in through the plug-in engine to integrate the customized parts of the subsystems of the SaaS platform corresponding to the business requirements.

[0044] Exemplarily, the configuration file includes a Nacos configuration file, a routing configuration file and a k8s configuration file. In the above step 102, loading the plug-in through the plug-in engine includes executing all SQL script files; creating a namespace through the Http interface and adding or modifying the Nacos configuration file; generating a docker image according to the compiled programs of the front-end and back-end, and uploading it to the intranet server; starting the front-end and back-end services through the kubectl command line tool provided by the container orchestration system; and binding with the menu routing of the portal according to the routing configuration of the xml configuration file.

[0045] Before executing all SQL script files, the above step 102, loading the plug-in through the plug-in engine also includes decrypting and decompressing the plug-in format file through a symmetric algorithm; calculating the signature value of each decompressed file through a digest algorithm, and comparing the signature value with the signature value in the plug-in generation step; when the two signature values ​​are the same, executing all SQL script files.

[0046] Figure 3 This is a schematic diagram of the structure of the SaaS platform and its portal provided in the embodiment of the present application. Figure 3 As shown, the subsystem of the SaaS platform includes standard version and customized parts, and the standard version includes web standardized products or platforms.

[0047] In the above SaaS platform development method, plug-ins and plug-in engines are generated according to business needs; plug-ins are loaded through the plug-in engine to integrate the customized parts of the subsystems of the SaaS platform corresponding to the business needs, which can be applied to the web-side projects of the SaaS platform. Metadata management of the customized system is performed through plug-ins to meet the differentiated requirements of web-side users, and users can reuse existing plug-ins; in addition, new functions are added without changing the main code of the subsystem, avoiding large-scale custom development work and saving development costs.

[0048] In one embodiment, the above SaaS platform development method also includes creating a portal, which is used to provide single sign-on, data permission interface, menu routing control, and enter the subsystem of the SaaS platform through the single sign-on portal; adding a plug-in engine to the portal.

[0049] In one embodiment, the above SaaS platform development method further includes dividing the subsystems of the SaaS platform by business domains.

[0050] Figure 4 A schematic diagram of the process of implementing single sign-on provided in the embodiment of the present application. Figure 3 and Figure 4 , standard product projects need to be designed as follows:

[0051] (1) Microservices (i.e., subsystems) are split according to business domains. Functional codes of different business domains should be encapsulated into independent microservices. Microservices communicate with each other through lightweight HTTP interfaces. Each microservice revolves around one or a group of specific businesses and can be deployed independently.

[0052] (2) Each subsystem does not need to develop a separate login page, all of them are connected to CAS single sign-on. For details about the CAS single sign-on process, please refer to Figure 4 .

[0053] (3) The portal uniformly exports standard API specifications, such as user, permission, session, plug-in and other related interfaces. It also provides a docking SDK to facilitate quick access to subsystems.

[0054] Through the unified portal, cas single sign-on and master data management are provided, and a unified portal page is provided for integrating subsystems and plug-ins. The plug-in engine is added to the portal. After logging in to the portal, users can enter the subsystem of the SaaS platform through the plug-in engine in the portal without having to log in again.

[0055] Figure 5This is a schematic diagram of the plug-in generation process provided in the embodiment of the present application. Figure 5 As shown, according to business needs, plug-ins are generated, including:

[0056] A. Build the project script and generate the VUE and Springboot source code framework structure (i.e. web development framework);

[0057] B. Generate front-end UI and back-end service codes according to business needs;

[0058] C. Prepare SQL scripts: Create a new sql folder and name the SQL script files according to the SQL execution order, such as: 1.xxx.sql; put all SQL script files into the sql folder;

[0059] D. Prepare Nacos configuration adjustment file: create a new folder nacos, and then create a new Nacos configuration file. The naming rule is: serial number.namespace_Datald.properties;

[0060] E. Prepare k8s configuration adjustment files: create a new folder k8s and put k8s related configuration files in it;

[0061] F. Package the front-end UI and back-end service codes and put them into the vue folder and java folder in the build folder respectively;

[0062] G. Create a new plugin.xml (i.e. XML configuration file) to describe the metadata of the plugin;

[0063] H. In Plugin Management, click Generate Plugin and upload the relevant files from steps A to F;

[0064] I. The plug-in engine performs ZIP compression on the uploaded files;

[0065] J. For the file compressed in step I, first perform a digest algorithm to obtain a signature value, and then save the signature value to plugin.xml to prevent the plug-in from being tampered with;

[0066] K. Perform symmetrical encryption on the file compressed in step J, generate a plug-in, and save plugin.xml as xxx.plugin (i.e., a file in plug-in format).

[0067] Figure 6 The following is a schematic diagram of the plug-in loading process provided in the embodiment of the present application. Figure 6 As shown, plugins are loaded through the plugin engine, including:

[0068] A. Decryption and compression: After receiving xxx.plugin, it is decrypted using a symmetric algorithm and then decompressed using ZIP;

[0069] B. Verify the integrity of the plugin: Reference Figure 5 The signature algorithm in the decompressed files is used to calculate the signature value, and the signature value is compared with Figure 5 Compare with the signature value in step J;

[0070] C. Execute SQL: When the two signature values ​​are consistent, all SQL script files are executed through Jdbc;

[0071] D. Adjust Nacos configuration: Create a namespace and add or modify Nacos configuration files through the Http interface officially provided by Nacos;

[0072] E. Generate a Docker image based on the compiled programs of the front-end and back-end, and upload it to the intranet server;

[0073] F. Start the front-end and back-end services: Start pod and ingress through the kubectl command line tool provided by the k8s container orchestration system;

[0074] G. Bind route: According to the route configuration of plugin.xml, bind it with the menu route of the portal.

[0075] The present application also provides a computer device, whose internal structure diagram can be as follows: Figure 7 As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless method can be implemented through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a SaaS platform development method is implemented.

[0076] Those skilled in the art will understand that Figure 7 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0077] like Figure 7 As shown, the present application also provides a computer device, which includes a memory, a processor, and a computer program stored in the memory, and the processor executes the computer program to implement the steps in the above-mentioned method embodiments.

[0078] The present application also provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented. The computer-readable storage medium may include, but is not limited to, any type of disk, including a floppy disk, an optical disk, a DVD, a CD-ROM, a micro drive, and a magneto-optical disk, a ROM, a RAM, an EPROM, an EEPROM, a DRAM, a VRAM, a flash memory device, a magnetic card or an optical card, a nanosystem (including a molecular memory IC), or any type of medium or device suitable for storing instructions and / or data.

[0079] The present application also provides a computer program product, including a computer program, which implements the steps in the above-mentioned method embodiments when executed by a processor.

[0080] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

[0081] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0082] The above is only an exemplary embodiment of the present disclosure, and the scope of the present disclosure cannot be limited thereto. That is, any equivalent changes and modifications made according to the teachings of the present disclosure are still within the scope of the present disclosure. After considering the specification and practicing the disclosure here, those skilled in the art will easily think of the implementation scheme of the present disclosure. This application is intended to cover any modification, use or adaptation of the present disclosure, which follows the general principles of the present disclosure and includes common knowledge or customary technical means in the technical field not recorded in the present disclosure. The description and examples are only regarded as exemplary, and the scope and spirit of the present disclosure are defined by the claims.

[0083] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0084] It will be easily understood by those skilled in the art that the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A SaaS platform development method, characterized in that: Applied to the web side, including: Generate plug-ins and plug-in engines according to business needs; the plug-ins include front-end UI code, back-end service code, configuration files, and SQL script files; the plug-in engine is used to manage the plug-ins and provide a running environment for the plug-ins; The plug-in is loaded through the plug-in engine to integrate the customized part of the subsystem of the SaaS platform corresponding to the business demand.

2. The method according to claim 1, characterized in that The plug-in is generated according to business requirements, including: Build project scripts and generate web development framework; Generate front-end UI code and back-end service code according to business needs; Create a new database folder, name the SQL script files in the order of execution, and put all SQL script files into the database folder; Create a new configuration folder and put all configuration files into the configuration folder; Create a new XML configuration file, which is used to describe the metadata of the plug-in; The front-end UI code, the back-end service code, the database folder, and the configuration folder are written into the xml configuration file to generate a file in a plug-in format.

3. The method according to claim 2, characterized in that The plug-in further includes a file compression tool, a file packaging tool, and a file encryption tool. The front-end UI code, the back-end service code, the database folder, and the configuration folder are written into the xml configuration file to generate a plug-in, including: Use the file packaging tool to package the front-end UI code corresponding to the front-end project and the back-end service code corresponding to the back-end project, and put the packaged files into the front-end project folder and the back-end project folder respectively; Write the front-end project folder, the back-end project folder, the database folder, and the configuration folder into the xml configuration file; Use the file compression tool to compress the written files; Calculate the signature value of the compressed file through a digest algorithm, and save the signature value to the XML configuration file; The compressed file is symmetrically encrypted using a file encryption tool, and the XML configuration file is saved as a file in a plug-in format.

4. The method according to claim 2, characterized in that The plug-in engine includes a plug-in boot program and a plug-in management program; the plug-in boot program is used to automatically deploy, automatically configure, and execute at least one of plug-in SQL scripts; the plug-in management includes at least one of plug-in storage, import / export, plug-in enabling and disabling, plug-in metadata viewing, and uploading plug-ins to a plug-in market.

5. The method according to claim 4, characterized in that The configuration files include a Nacos configuration file, a routing configuration file, and a k8s configuration file, and the loading of the plug-in through the plug-in engine includes: Execute all SQL script files; Create a namespace and add or modify Nacos configuration files through the Http interface; Generate a Docker image based on the compiled programs of the front-end and back-end, and upload it to the intranet server; Start the front-end and back-end services through the kubectl command-line tool provided by the container orchestration system; According to the routing configuration of the xml configuration file, it is bound to the menu routing of the portal.

6. The method according to claim 5, characterized in that The plug-in boot program is also used to decrypt and decompress the plug-in, and execute all SQL script files, including: Decrypting and decompressing the file in the plug-in format by using a symmetric algorithm; Calculate the signature value of each decompressed file through the digest algorithm, and compare the signature value with the signature value in the plug-in generation step; If the two signature values ​​are the same, all SQL script files are executed.

7. The method according to claim 1, characterized in that The method further comprises: Create a portal that provides single sign-on, data permission interface, menu routing control, and access to the subsystem of the SaaS platform through single sign-on to the portal; Adding the plug-in engine to the portal.

8. A computer device, characterized in that: The invention comprises a memory, a processor and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the method according to any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer program product, characterized in that The invention comprises a computer program, which implements the steps of the method according to any one of claims 1 to 7 when being executed by a processor.

Images