Component deployment method of application and related equipment

Abstract

The embodiment of the invention discloses a component deployment method of an application and related equipment, belongs to the technical field of computers, and is used for dynamically deploying and rendering components in the application according to user permission and improving the data security of the application. The method is executed by a server and comprises the steps of determining permission information corresponding to a first user, obtaining a target component according to the permission information corresponding to the first user; wherein the authority information is used for indicating a component corresponding to an application which the user has access to; the target component is a component of an application which the first user has access to; the target component comprises a resource file; the resource file is used for realizing functions of an application corresponding to the target component; deploying the resource file of the target component to a server; sending the deployment information to a client of the first user, so that the client renders a front-end page of the application according to the deployment information; the deployment information is generated when the resource file of the target component is deployed in the server.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, and in particular to a component deployment method for an application and related equipment. Background Art

[0002] Microservice architecture is a software architecture pattern that splits complex backend applications into multiple independent, autonomous small services. In the microservice architecture, each service focuses on completing a specific business function, has clear boundaries and responsibilities, and these services can be independently developed, deployed, expanded, and maintained. The micro-frontend architecture derived from the microservice concept is an architecture pattern that splits a large frontend application into multiple small, independently deployable frontend applications. This architecture allows different teams to independently develop, test, and deploy different parts of the same frontend application, which can form a complete frontend application.

[0003] In modern large-scale applications, micro-frontend architecture and microservice architecture are widely favored due to their independence, easy maintainability, and scalability.

[0004] In related technologies, the micro-frontend architecture will cause all front-end pages to be exposed to users, which will cause some sensitive components in the application to be accessed or attacked, threatening data security and increasing security risks. Summary of the invention

[0005] The embodiment of the present application provides an application component deployment method and related devices, which are used to dynamically deploy and render components in an application according to user permissions, thereby improving the data security of the application. The technical solution is as follows:

[0006] In a first aspect, a method for deploying components of an application is provided, the method being executed by a server, the method comprising: determining permission information corresponding to a first user, the permission information being used to indicate a component corresponding to an application that the user has the right to access, and the server determining a target component based on the permission information corresponding to the first user. The target component is a component of an application that the first user has the right to access; the target component includes a resource file; the resource file is used to implement the function of the application corresponding to the target component. The resource file of the target component is deployed to the server. The server sends the deployment information to the client of the first user, so that the client renders the front-end page of the application based on the deployment information. The deployment information is generated when the resource file of the target component is deployed on the server.

[0007] From the above, it can be seen that the above method can ensure that only the client of authorized users can render and access the front-end page of a specific application, fundamentally reducing the possibility of the application system receiving access attacks, reducing the risk of exposure of unauthorized components and sensitive data, and improving the security of the application.

[0008] In one possible implementation, path information of each target component is determined, where the path information is used to indicate the location of the target component in a database; resource files of at least one target component are obtained from the database, where the resource files include a front-end page file and a back-end service file.

[0009] From the above, it can be seen that obtaining the resource files corresponding to each target component from the database according to the path information of each target component can ensure the accuracy of obtaining the resource files of each target component while avoiding resource exposure.

[0010] In one possible implementation, a first access request from a first user is obtained; the first access request includes identification information of the first user; the first access request is used to instruct the server to deploy a component corresponding to an application that the first user has the right to access; and permission information corresponding to the first user is determined based on the identification information of the first user.

[0011] From the above, it can be seen that determining the permission information of the first user based on the identification information of the first user in the first access request can meet the role requirements of different users. At the same time, authorizing a specific target component to allow the first user to access improves the efficiency and flexibility of managing application permissions.

[0012] In one possible implementation, permission information corresponding to the first user is determined based on the first user's identification information and a first mapping relationship; the first mapping relationship is a correspondence between the identification information and permission information of an application user; the first user is a user in the first mapping relationship.

[0013] From the above, it can be seen that the server can determine the permission information of the first user according to the identification information of the first user through the preset first mapping relationship, thereby ensuring the stability and accuracy of the permission management of the application.

[0014] In one possible implementation, a modification request is obtained; the modification request is used to indicate modification of permission information corresponding to at least one user in the first mapping relationship; and according to the modification request, permission information corresponding to at least one user in the first mapping relationship is updated.

[0015] From the above, it can be known that the server can modify the permission information corresponding to at least one user in the first mapping relationship through a modification request and update the permission information corresponding to the user, which can meet the personalized permission management of users and improve the flexibility of application permission management.

[0016] In a possible implementation, the deployment information includes routing information; the routing information is used to indicate address information of a resource file of a target component after being deployed on a server.

[0017] As can be seen from the above, the routing information included in the deployment information can indicate the address information of the resource files of each target component in the business server, thereby avoiding exposure of the real address of the resource files and enhancing data security.

[0018] In one possible implementation, there are multiple target components, and priority information of each target component is determined, where the priority information is used to indicate the deployment order of each target component; resource files of the multiple target components are deployed to the server according to the priority order of the multiple target components.

[0019] In a second aspect, a component rendering method for an application is provided, which is executed by a client device, and the method includes: in response to a target operation of a first user, upon obtaining deployment information sent by a server, rendering a front-end page of an application corresponding to a target component according to the deployment information; the deployment information is generated when a resource file of the target component is deployed on the server; the target component is a component corresponding to an application that the first user has access to.

[0020] From the above, it can be seen that the above method can ensure that only the target components of the authorized first user can render and access the front-end page of a specific application on the client, fundamentally reducing the possibility of the application system receiving access attacks, reducing the risk of exposure of unauthorized components and sensitive data, and improving the security of the application.

[0021] In one possible implementation, without obtaining the deployment information sent by the server, a first access request is sent, so that the server determines the permission information of the first user based on the first access request, obtains the resource file of the target component corresponding to the application that the first user has the right to access; the resource file is deployed to the server; the permission information is used to indicate the component corresponding to the application that the user has the right to access; the first request includes the identification information of the first user, and the identification information has a corresponding relationship with the permission information of the first user.

[0022] From the above, it can be seen that before the client device renders, it is determined whether the deployment information has been generated. If the deployment information already exists, the client device can render directly; if the deployment information does not exist, the client device sends a first access request to the server to obtain the deployment information, which can improve the efficiency and performance of the client device rendering the front-end page of the target component.

[0023] In a possible implementation, the deployment information includes routing information; the routing information is used to indicate address information of a resource file of a target component after being deployed on a server.

[0024] As can be seen from the above, the routing information included in the deployment information can indicate the address information of the resource files of each target component in the business server, thereby avoiding exposure of the real address of the resource files and enhancing data security.

[0025] In a third aspect, a component deployment device for an application is provided. An embodiment of the present application may divide the component deployment device for the application into functional modules according to the method provided in the first aspect above. For example, each functional module may be divided according to each function, or two or more functions may be inherited in one processing module. Exemplarily, an embodiment of the present application may divide the component deployment device for the application into a processing module, an acquisition module, a deployment module, and a sending module according to the function. The description of the possible technical solutions and beneficial effects executed by each of the functional modules divided above can refer to the technical solutions provided by the first aspect above or its corresponding possible implementation method, which will not be repeated here.

[0026] In a fourth aspect, a component rendering device for an application is provided. An embodiment of the present application may divide the component rendering device for the application into functional modules according to the method provided in the second aspect above. For example, each functional module may be divided corresponding to each function, or two or more functions may be inherited in one processing module. Exemplarily, an embodiment of the present application may divide the component rendering device for the application into a processing module and a rendering module according to the function. The description of the possible technical solutions and beneficial effects executed by each of the functional modules divided above can refer to the technical solutions provided by the second aspect above or its corresponding possible implementation method, which will not be repeated here.

[0027] In a fifth aspect, an embodiment of the present application provides a server, wherein the computing device includes a processor and a memory, wherein the memory stores computer instructions, and the computer instructions are loaded and executed by the processor so that the server implements the component deployment method of the application as described in the first aspect above.

[0028] In a sixth aspect, an embodiment of the present application provides a client device, the client device comprising a processor and a memory, the memory storing computer instructions, the computer instructions being loaded and executed by the processor so that the client device implements a component rendering method for an application as described in the second aspect above.

[0029] In the seventh aspect, an embodiment of the present application provides a computer-readable storage medium, in which at least one computer program is stored. The computer program is loaded and executed by a processor to implement the component deployment method of the application of the first aspect or the component rendering method of the application of the second aspect as described above.

[0030] In an eighth aspect, an embodiment of the present application provides a computer program product or a computer program, the computer program product or the computer program including computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a server reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the server executes the component deployment method of the application provided in various optional implementations of the first aspect above.

[0031] For the specific description of the third to eighth aspects and their various implementations in the embodiments of the present application, reference can be made to the detailed description in the first aspect, the second aspect and their various implementations; and for the beneficial effects of the third to eighth aspects and their various implementations, reference can be made to the analysis of the beneficial effects in the first aspect, the second aspect and their various implementations, which will not be repeated here.

[0032] These and other aspects of the embodiments of the present application will be more clearly understood in the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 A schematic diagram of a microservice software architecture is shown;

[0034] Figure 2 A schematic diagram of a micro front-end software architecture is shown;

[0035] Figure 3 A schematic diagram of an application system environment 100 is shown;

[0036] Figure 4 A schematic diagram of an application system 200 provided in an embodiment of the present application is shown;

[0037] Figure 5 A schematic diagram of a server hardware structure provided by an embodiment of the present application is shown;

[0038] Figure 6 A schematic diagram of a software architecture 300 of a method for deploying components of an application provided in an embodiment of the present application is shown;

[0039] Figure 7 A schematic diagram showing a component deployment method flow of an application provided by an embodiment of the present application;

[0040] Figure 8 A schematic diagram showing a component rendering method flow of an application provided in an embodiment of the present application;

[0041] Fig. 9 A schematic diagram showing the process of a method for accessing a component of an application provided in an embodiment of the present application;

[0042] Fig.10A schematic diagram showing the structure of a component deployment device 400 for an application provided in an embodiment of the present application is shown;

[0043] Fig.11 A schematic diagram showing the structure of a component rendering device 800 of an application provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0044] In order to make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the implementation methods of the present application will be further described in detail below in conjunction with the accompanying drawings.

[0045] The term "multiple" as used herein refers to two or more than two. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.

[0046] First, the application scenarios of the embodiments of the present application are exemplarily introduced.

[0047] Figure 1 A schematic diagram of a microservice software architecture is shown. Figure 1 As shown in the figure, microservices are applied in the backend service, splitting the backend service into n subservices, namely subservice 1, subservice 2, subservice 3, and so on, subservice n. Among them, n is a positive integer greater than 1. Each subservice is a project that can be independently run, deployed, and maintained, and each subservice is used to implement different functions and services. The subservices do not interfere with each other, which not only improves the flexibility and independence of the development and deployment of the backend service, but also greatly improves the maintainability and fault tolerance of the backend service.

[0048] The micro front-end architecture splits a large front-end application into multiple small, independently deployable front-end applications. Each micro front-end application has its own functions and responsibilities, and can be independently developed, tested, deployed, and maintained.

[0049] Figure 2 A schematic diagram of a micro front-end software architecture is shown. Figure 2 As shown in the figure, the micro-frontend architecture can split the front-end application into m sub-applications, including sub-application 1, sub-application 2, sub-application 3, and so on, sub-service m. Among them, m is a positive integer greater than 1. Each sub-application after splitting can be regarded as an application-level component. Each sub-application is independent of each other and is used to implement a specific function and page. The micro-frontend architecture can not only improve the flexibility and independence of the front-end application and increase the reuse rate of sub-applications; it can also reduce conflicts and collaboration costs during the development process and improve the stability of the front-end application.

[0050] For large applications, microservices and micro frontends provide them with the architectural advantages of independence, maintainability, and scalability, improving the efficiency of large applications during development and maintenance.

[0051] Figure 3 1 shows a schematic diagram of an application system environment 100. Figure 3 As shown, the application system environment 100 includes a server 110 and a terminal device 120. Data is transmitted between the server 110 and the terminal device 120 via a network. The application includes a front-end application and a back-end service. Among them, the front-end application adopts a micro-front-end software architecture, and the front-end application includes multiple sub-applications; the back-end service adopts a micro-service software architecture, and the back-end service includes multiple sub-services. The front-end application can be understood as the entrance of the application, which is rendered on the front-end interface. The user can enter the application through the controls on the display interface, and the back-end service can be understood as the module / code included in the function of the application to be implemented, which runs on the server.

[0052] Among them, the server 110 runs the backend service of the application. Optionally, the server also runs a database for storing the code files corresponding to the front-end application and the back-end service of the application. The terminal device 120 runs a client or browser corresponding to the application, which can render the front-end application of the application; at the same time, the terminal device also includes a display screen for displaying the display page 01 of the application. The display page 01 of the application includes the controls and windows in the front-end application of the application. The user operates and accesses the back-end service corresponding to the control or window in the display page 01 of the application displayed by the terminal device 120.

[0053] The present application embodiment provides a component deployment method for an application, which is suitable for Figure 3The application system shown. The server determines the permission information of the user according to the user information, that is, the components of the application that the user has the right to access. The server deploys the resource files of the components corresponding to the application that the user has the right to access on the server according to the permission information of the user, and sends the deployment information to the client of the user. The user client renders the front-end page of the application that the user has the right to access according to the deployment information. The method may specifically include that the server determines the permission information corresponding to the first user. The permission information is used to indicate the components corresponding to the application that the user has the right to access; the server determines the target component according to the permission information corresponding to the first user, and the target component may be one or more, which is not specifically limited here. The target component is the component of the application that the first user has the right to access, and includes a resource file. The server deploys the resource file of the target component to the server. The resource file is used to implement the function of the application corresponding to the target component, and includes a back-end service file and a front-end page file that implement the function. The server sends the deployment information to the client of the first user. The deployment information is generated when the resource file of the target component is deployed on the server. The deployment information is used for the client to render the front-end page of the application corresponding to the target component. When the first user's client device receives the deployment information, it renders the front-end page of the application corresponding to the target component according to the deployment information. The front-end page includes one or more application entrances, and the user can access the back-end service through the entrance. In the above method, the server deploys the resource files of the target component that the first user has the right to access on the server according to the permission information corresponding to the first user, and sends the deployment information to the client of the first user. The first user's client device can render the front-end page of the application that the first user has the right to access according to the deployment information, and can access the corresponding back-end service through the front-end page corresponding to the target component. Thereby, dynamic deployment and rendering according to the permission information of the first user is realized, that is, only the components corresponding to the applications that the first user has the right to access are deployed or rendered, which can prevent the first user from accessing or attacking the applications of components that he has no right to access from the source, reduce the risk of data leakage, and improve data security.

[0054] Secondly, the system architecture of the embodiment of the present application is exemplarily introduced.

[0055] Figure 4 FIG. 2 is a schematic diagram of an application system 200 provided in an embodiment of the present application. Figure 4 As shown, the application system 200 includes a management server 210, a business server 220 and a client device 230. The management server 210, the business server 220 and the client device 230 are connected to each other via a network.

[0056] The management server 210 is used to implement a method for deploying application components, which may specifically be a blade server, a high-density server, a rack server or a high-performance server. The management server 210 is used to determine permission information corresponding to the first user. The permission information is used to indicate the components corresponding to the application that the user has the right to access; and the target component is determined based on the permission information of the first user. The target component is a component of the application that the first user has the right to access, and includes a resource file. The management server 210 is also used to deploy the resource file of the target component to the business server 220. The resource file is used to implement the function of the application corresponding to the target component.

[0057] The management server 210 sends deployment information to the client of the first user, wherein the deployment information is generated when the management server 210 deploys the resource file of the target component to the business server 220, and the deployment information is used by the client to render the front-end page of the application corresponding to the target component.

[0058] The client device 230 can specifically be an electronic device such as a personal computer, a laptop, a desktop, a tablet or a mobile phone with a client or a browser installed, which is used to implement the rendering method of the application component. The client device 230 is used to respond to the target operation of the first user, and when the deployment information sent by the management server 210 is obtained, the front-end page of the application corresponding to the target component is rendered according to the deployment information. The deployment information is generated by the management server 210 when the resource file of the target component is deployed on the business server 220; the target component is the component corresponding to the application that the first user has the right to access. The user can access the back-end service of the target component through the front-end page of the application corresponding to the rendered target component.

[0059] The service server 220 is used to implement and provide application functions and services.

[0060] Optionally, the application system 200 also includes a database for storing resource files of components corresponding to the application. The management server 210 can obtain the resource files of the target components from the database and deploy the resource files to the business server 220. The database can run on the management server 210 or on a separate server, which is not limited here.

[0061] It should be noted that in the embodiment of the present application, the management server 210 and the business server 220 can be the same server 110 or different servers, which is not limited here.

[0062] Figure 5 A schematic diagram of a server hardware structure provided by an embodiment of the present application is shown. Figure 5As shown, the server 110 may be a blade server, a high-density server, a rack server or a high-performance server. The server 110 may include a central processing unit CPU 310, a memory 320 and a bus 330. The CPU 310 and the memory 320 are usually connected to each other via the bus 330, or are connected to each other in other ways.

[0063] Among them, CPU 310 is used to provide computing resources for server 110, and CPU 310 can determine the permission information corresponding to the first user. The permission information is used to indicate the component corresponding to the application that the user has the right to access; and the target component is determined according to the permission information of the first user. Among them, the target component is the component of the application that the first user has the right to access. CPU 310 can obtain the resource file of the target component and deploy the resource file of the target component to server 110. Among them, the resource file is used to implement the function of the application corresponding to the target component. CPU 310 sends the deployment information to the client of the first user, wherein the deployment information is generated when the resource file of the target component is deployed on the server; the deployment information is used for the client to render the front-end page of the target component.

[0064] The memory 320 may be hardware capable of implementing a storage function, specifically a volatile memory, a non-volatile memory, a hard disk or a flash drive, for storing resource files of components corresponding to the application and instructions or programs for implementing a deployment method of the components of the application.

[0065] It should be noted that in the embodiment of the present application, the business server is used to implement and provide application functions and services, and the hardware structure of the business server is the same as the hardware structure of the above-mentioned server 110.

[0066] Figure 6 A schematic diagram of a software architecture 300 of a method for deploying components of an application provided in an embodiment of the present application is shown. Figure 6 As shown, the software architecture 300 of the method for deploying components of an application includes a menu generator, a deployer, and a rendering engine.

[0067] The menu generator is a set of software tools used to determine the permission information corresponding to the first user. The menu generator can be applied to Figure 4In the management server 110 shown. Optionally, the menu generator can also obtain the identification information of the first user, and determine the permission information of the first user according to the identification information of the first user and the first mapping relationship. The first mapping relationship includes a mapping relationship between user identification information and permission information. Optionally, the menu generator can also generate a first permission menu according to the permission information of the first user; the first permission menu includes the number of controls corresponding to the application that the first user has the right to access, the entrance of the application, and the application name and the path information of the target component corresponding to the application.

[0068] A deployer is a software tool used to deploy and manage application components in a server environment. The deployer can be applied to Figure 4 In the business server 220 shown. The main functions of the deployer include effectively installing, configuring and starting the components of the developed application (such as web components, applications, services, libraries, etc.) on the server to ensure that these components can operate normally and provide corresponding services. In an embodiment of the present application, the deployer is used to obtain the resource files of the target component and deploy the resource files of the target component to the business server. Optionally, the deployer can also determine the path information of the target component and obtain the resource files of the target component from the database based on the path information. The resource files include front-end page files and back-end service files, and are used to implement the functions of the application corresponding to the target component.

[0069] The rendering engine is a software component that is responsible for converting HTML, CSS, and JavaScript codes of the front-end page file into a visual interface visible to the user in the browser. The rendering engine can be applied to Figure 4 The client device 230 shown. The main functions of the rendering engine include parsing HTML and CSS codes, determining the layout and style of page elements, processing JavaScript codes to achieve dynamic effects and interactive functions, and integrating this information to generate the final graphic page. In the embodiment of the present application, the front-end rendering engine is used to render the front-end page of the application corresponding to the target component according to the deployment information when the deployment information sent by the server is obtained.

[0070] It should be noted that the system architecture and application scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0071] For ease of understanding, the following is an exemplary introduction to the component deployment method of the application provided by the present application in conjunction with the accompanying drawings. The component deployment method of the application is as follows: Figure 3The server 110 shown executes the method, which includes:

[0072] Figure 7 A schematic diagram of a component deployment method for an application provided in an embodiment of the present application is shown. The component deployment method for the application is executed by a server and includes the following steps:

[0073] S101: Determine permission information corresponding to a first user.

[0074] In the embodiment of the present application, the backend service of the application adopts the software architecture of microservices, and the frontend page adopts the software architecture of micro-frontends. A component in the application includes a backend service and a frontend page; the backend service is used to implement the function of the component, and the frontend page is used to display the component page.

[0075] The permission information is used to indicate the components of the application that the user has the right to access.

[0076] Exemplarily, an application may correspond to N components, where N is a positive integer greater than 1. The permission information may include the number of components of the application that the user has the right to access and the path information of the components. If the number of components of the application indicated in the permission information is less than N, it means that the user needs or can access the components corresponding to the application.

[0077] For example, the permission information may include the name information, id information and path information of the target component, wherein the name information of the component corresponds to the id information one by one, and the path information is used to indicate the location information of the component in the database.

[0078] In a possible implementation manner, the server obtains a first access request from a first user, and determines permission information corresponding to the first user according to identification information of the first user.

[0079] The first access request includes identification information of the first user; the first access request is used to instruct the server to deploy a component corresponding to an application that the first user has the right to access.

[0080] Exemplarily, the first access request includes a login request of the first user, and the login request includes identification information. The server can obtain the identification information of the first user according to the login request of the first user, and determine the permission information corresponding to the first user according to the identification information of the first user, thereby determining the component corresponding to the application that the first user has the right to access.

[0081] In a possible implementation manner, the server determines the authority information corresponding to the first user according to the identification information of the first user and the first mapping relationship.

[0082] The first mapping relationship is a correspondence between identification information of an application user and permission information.

[0083] That is, the server determines the permission information corresponding to the first user according to the preset first mapping relationship between the user identification information and the permission information and the identification information of the first user.

[0084] For example, the first mapping relationship includes a correspondence between user information and roles, and different roles correspond to different permission information. The role is a classification of users who access the application by relevant technical personnel; the user identification information can be identification information such as a user role unique identifier or a user role name.

[0085] For example, in the application, the visiting users are pre-classified into three categories, namely, the administrator role, the ordinary user role, and the temporary user role. In the first mapping relationship, the user whose role unique identifier is 001 corresponds to the administrator role, the user whose role unique identifier is 002 corresponds to the ordinary user role, and the user whose role unique identifier is 003 corresponds to the temporary user role. The permission information corresponding to the administrator role is that the components corresponding to the accessible application include A1, A2, and A3, the permission information corresponding to the ordinary user role is that the components corresponding to the accessible application include B1, B2, and B3, and the permission information corresponding to the temporary user role is that the components corresponding to the accessible application include C1, C2, and C3. When the server obtains the first access request, it can obtain that the role unique identifier of the first user is 001. According to the first mapping relationship, the server can determine that the first user is the administrator role. Therefore, it can be determined that the permission information corresponding to the first user is that the components corresponding to the accessible application include A1, A2, and A3. Specifically, the permission information corresponding to the first user includes the name information, id information, and path information of the components A1, A2, and A3 corresponding to the application that the first user has the right to access, respectively corresponding to the application.

[0086] In a possible implementation manner, the server obtains a modification request; and updates permission information corresponding to at least one user in the first mapping relationship according to the modification request.

[0087] The modification request is used to indicate modification of the permission information corresponding to the user in the first mapping relationship.

[0088] Exemplarily, the modification request may include a deletion instruction or an addition instruction for a component corresponding to an application that the user has the right to access in the permission information corresponding to the user, and the server executes the deletion instruction or the addition instruction to add or delete the component in the permission information corresponding to the role information included in the first mapping relationship. When a component of the application is added or deleted, the permission information is updated.

[0089] For example, based on the user's unique role identifier, the server receives a modification request sent by the client device to instruct the deletion of the approval component A1 corresponding to the application that the user has the right to access in the permission information corresponding to the administrator role. In response to the modification request, the server deletes the approval component A1 corresponding to the application that the user has the right to access in the permission information corresponding to the administrator role. Similarly, in response to the modification request, the server can also add components corresponding to the application that the user has the right to access in the permission information.

[0090] From the above, it can be seen that the server can update the permission information by receiving and responding to modification requests, that is, dynamically assigning components corresponding to the applications that users have the right to access, which can improve the flexibility and scalability of the application component deployment, so that the application system can flexibly adapt to the permission requirements of different users.

[0091] In one possible implementation, the server has a built-in analysis model that intelligently analyzes the user behavior or usage pattern of the first user to determine the permission information of the first user.

[0092] The user behavior is used to indicate the history of the user's access to each component in the application; the usage mode is used to indicate the frequency of the user's access to each component in the application.

[0093] For example, the user behavior or usage pattern of the first user is collected through artificial intelligence technology to predict the components corresponding to the application that the user needs to access, thereby determining the corresponding permissions of the first user. This not only saves the labor cost of presetting the first mapping relationship, but also can further improve the flexibility and accuracy of determining user permission information.

[0094] S102: Acquire a target component according to permission information corresponding to the first user.

[0095] The target component is a component of an application that the first user has the right to access; the target component includes a resource file; and the resource file is used to implement the function of the application corresponding to the target component.

[0096] In an embodiment of the present application, a resource file is used to implement the function of an application corresponding to a component in the application.

[0097] In a possible implementation, the server determines the path information of the target component and obtains the resource file of the target component from a database.

[0098] The path information is used to indicate the location of the target component in the database; the resource files include the front-end page files and the back-end service files.

[0099] Exemplarily, the server determines the path information of the target component corresponding to the application that the first user has the right to access based on the permission information corresponding to the first user. The server accesses the database based on the path information and obtains the target component from the database. Since the target component includes a resource file, the resource file corresponding to the target component is obtained. The database is used to store and manage various components in the application.

[0100] For example, the first user's permission information includes path information. The server parses the permission information and obtains the path information of three target components corresponding to the application that the first user has the right to access, which are path 1, path 2, and path 3. The server obtains the three target components from the database according to path 1, path 2, and path 3, and obtains the resource files of the three target components.

[0101] Optionally, the target component may be a software package. One target component corresponds to one software package. The software package consists of an image file, a front-end page file, and a software package description file. Among them, the image file is the back-end service file of the application corresponding to the target component, the front-end page file is the front-end page file of the application corresponding to the target component, and the software package description file may include software package identification information, software package name, and address information corresponding to the image file and the front-end page file. Therefore, the server can obtain the image file and the front-end page of the software package according to the address information corresponding to the image file and the front-end page file in the software package description file.

[0102] S103, deploying the resource files of the target component to the server.

[0103] Among them, the resource file is used to implement the function of the application corresponding to the target component.

[0104] In a possible implementation, there are multiple target components, and the server determines the priority information of each target component, and deploys the resource files of the multiple target components to the server according to the priority order of the multiple target components.

[0105] The priority information is used to indicate the deployment order of each target component.

[0106] For example, the permission information corresponding to the administrator role is that the target components corresponding to the application accessible to the user include A1, A2 and A3; wherein the target component may be a software package, and optionally, the software package description file may include priority information. Therefore, the software package description files of the software packages A1, A2 and A3 may each include priority information of each deployment order.

[0107] For example, if the role corresponding to the first user is an administrator role, the target component corresponding to the application that the first user has access to can implement functions such as transfer, loan, and approval. The server determines that the priority information of the component corresponding to the application function transfer is the first priority, the priority information of the component corresponding to the application function loan is the second priority, and the priority order of the component corresponding to the application function approval is the third priority. The server deploys the resource files of the component corresponding to the transfer function, the resource files of the component corresponding to the loan function, and the resource files of the component corresponding to the approval function in the server in the order of the first priority, the second priority, and the third priority.

[0108] From the above, we can know that the server can obtain the priority information of the target component from the permission information, and deploy the resource files of each target component to the server in sequence according to the order indicated by the priority information to ensure that these target components can run normally and provide responsive services. In this way, the target components with high priority are deployed first, further optimizing the component deployment method of the application and meeting the personalized needs of users.

[0109] S104: Send the deployment information to the client of the first user, so that the client renders the front-end page of the application according to the deployment information.

[0110] The deployment information is generated when the resource files of the target component are deployed on the server; the deployment information is used by the client to render the front-end page of the application corresponding to the target component.

[0111] In the embodiment of the present application, after the server deploys the resource files corresponding to the target component to the server, it generates deployment information.

[0112] In a possible implementation, the deployment information includes routing information.

[0113] The routing information is used to indicate the address information of the resource file of the target component after it is deployed on the server.

[0114] For example, the server determines the routing information based on the address information and mapping relationship of the resource file of the target component after it is deployed to the server.

[0115] That is to say, the routing information is determined according to the mapping relationship between the address information and the address information. The server sends the deployment information to the client, which not only enables the client device to obtain the resource file of the target component according to the deployment information, thereby rendering the front-end page, but also avoids exposing the real address of the resource file to the client device, thereby improving data security.

[0116] In a possible implementation, the server obtains a second access request from the first user; responds to the second access request, and sends return information corresponding to the backend service to the client.

[0117] The second access request is used to request the backend service of the application corresponding to the target component.

[0118] Exemplarily, the server completes the deployment of the resource files of the target component corresponding to the application that the first user has the right to access, and sends the deployment information to the client of the first user, so that the client device of the first user can render the front-end page of the application corresponding to the target component. The first user sends a second access request to the server through the control or window in the front-end page displayed by the client device, requesting access to the back-end service of the application corresponding to the target component. The server obtains and responds to the second access request, and sends the return information of the back-end service corresponding to the current front-end page to the client device of the first user, thereby enabling the first user to access the application corresponding to the target component.

[0119] For example, when the deployment of the components of the application is completed according to the permission information of the first user, the client of the first user receives the deployment information and renders the front-end page of the application to obtain the corresponding front-end page. The first user can send a query request to the back-end service of the application corresponding to the loan through the query control displayed on the loan page of the client device. The query request is used to request to obtain the loan details. After receiving the query request, the server responds to the query request through the back-end service of the application corresponding to the loan, and returns the query result to the client device of the first user. The query result includes the loan details. The client device of the first user receives the loan details returned by the business server.

[0120] The above describes the component deployment method of the application from the perspective of the server. The component deployment method of the application can ensure that the resource files of the components corresponding to the application that the first user has the right to access are deployed on the server, and the deployment information is sent to the client of the first user, so that only the authorized first user can render the front-end page number of the application that he has the right to access and can access the specific application. That is, the first user's client only renders the front-end page of the application corresponding to the first user's permission information, and the second user's client only renders the front-end page of the application corresponding to the second user's permission information. Among them, the permission information corresponding to the first user is different from the permission information corresponding to the second user. Fundamentally avoiding the possibility of unauthorized parts of the application being attacked by access, greatly reducing the risk of unauthorized data leakage.

[0121] The embodiment of the present application also provides a method for rendering an application component. The method for rendering an application component is executed by a client device, which may be a personal computer, a laptop, a desktop, a tablet, a mobile phone, or other electronic device with a client or a browser installed. Figure 8 A schematic diagram showing a component rendering method process of an application provided by an embodiment of the present application is shown as follows: Figure 8 As shown, the component rendering method of the application includes:

[0122] S201: A client device responds to a target operation of a first user.

[0123] In the embodiment of the present application, the target operation is used to instruct the client device to request to obtain the resource file corresponding to the front-end page corresponding to the component of the application that has the right to access.

[0124] Exemplarily, the client may respond to a trigger operation or input loading request of the first user.

[0125] S202: When the deployment information sent by the server is obtained, the client device renders the front-end page of the application corresponding to the target component according to the deployment information.

[0126] The deployment information is generated when the resource file of the target component is deployed on the server; the target component is a component of the application that the first user has the right to access.

[0127] Exemplarily, the client device may obtain the deployment information sent by the server, obtain the resource file of the target component according to the deployment information, and render the front-end page of the application corresponding to the target component through a browser or a rendering engine.

[0128] Optionally, the deployment information includes routing information. The routing information is used to indicate the address information of the resource file of the target component after being deployed on the server.

[0129] For example, the client device creates a micro-frontend object, determines the address information of the resource file of the target component indicated by the routing information in the server according to the routing information and the mapping relationship between the routing information and the address information, obtains the front-end page file in the resource file according to the address information, and generates the front-end page by rendering the front-end page file in the resource file through the browser.

[0130] In a possible implementation manner, the client device saves the acquired deployment information according to the identification information of the first user.

[0131] That is to say, when the first user logs in or accesses next time, it is first determined whether there is any acquired routing information. If the routing information already exists, the client device can directly render it, which can improve the efficiency of the client device in rendering the front-end page.

[0132] In one possible implementation, without obtaining the deployment information sent by the server, the client device sends a first access request, so that the server determines the permission information of the first user based on the first access request, and obtains the resource file of the target component corresponding to the application that the first user has the right to access based on the permission information; and deploys the resource file of the target component to the server.

[0133] The permission information is used to indicate the components corresponding to the application that the user has the right to access; and the first request includes identification information of the first user.

[0134] Exemplarily, when the client device does not obtain the deployment information, the client device sends a first access request to the server. The first access request includes the identification information of the user. The server determines the permission information corresponding to the first user based on the identification information of the first user, and deploys the resource file of the target component corresponding to the application that the first user has the right to access on the server to generate the deployment information. Thus, the client device can obtain the deployment information sent by the server.

[0135] For example, the identification information of the first user includes a unique identifier of the role of the first user, where the role is a classification of users who access the application by relevant technical personnel. The client device sends a first access request to the server, and the server receives the first access request and determines that the first user is an administrator role based on the identification information of the first user. Among them, the functions of the target components corresponding to the applications that the administrator role has the right to access are transfer, loan, and approval. The server deploys the resource files of the target components corresponding to the functions of transfer, loan, and approval corresponding to the applications that the administrator role has the right to access on the server, and sends the deployment information to the client device. According to the deployment information, the client device renders the front-end page files of the applications corresponding to transfer, loan, and approval to generate each front-end page. At this time, the client device of the first user can access the corresponding application through each front-end page.

[0136] Optionally, the first user can access the application corresponding to the loan function through the client device and send a second access request to the server. The second access request is used to request to obtain loan details. After receiving the second access request, the business server responds to the second access request through the backend service of the application corresponding to the loan function and returns the query result to the client device of the first user. The query result includes the loan details. Therefore, the client device of the first user receives the loan details returned by the server and completes the access to the application corresponding to the loan function.

[0137] The following describes the component deployment and rendering method of the above application from the perspective of interaction between the server and the client device. Fig. 9A schematic diagram showing the process of a method for accessing a component of an application provided by an embodiment of the present application is shown as follows: Fig. 9 As shown, in the case where the management server and the business server are the same server, the method includes:

[0138] The client device sends a first access request to the server (S301). The first access request includes the identification information of the first user. The server determines the permission information corresponding to the first user according to the identification information of the first user (S302). The permission information is used to indicate the components corresponding to the application that the user has the right to access. Specifically, a menu generator is running in the server, and the access rights of the first user are determined by the menu generator. Optionally, the server determines the permission information corresponding to the first user according to the identification information of the first user and the first mapping relationship through the menu generator. For example, the menu generator determines that the first user is an administrator role according to the identification information of the first user, and can determine that the permission information corresponding to the first user is the administrator permission according to the preset correspondence between the role information and the permission information. Thus, a permission menu corresponding to the first user is generated. The permission menu may include the number of controls corresponding to the application that the first user has the right to access, the name of each application, and the path information of each component corresponding to each application. The server obtains the target component according to the permission information corresponding to the first user (S303). The target component is the component corresponding to the application that the first user has the right to access. Specifically, a deployer is running in the server, and the deployer obtains and parses the permission information, determines the path information of each target component, and thus obtains the resource file of each target component. Wherein, the target component is stored in a database, and the path information is used to indicate the location information of the target component in the database. Therefore, the server can obtain the resource files of each target component from the database according to the path information. At the same time, the resource files include front-end page files and back-end service files, which are used to implement the functions of the application corresponding to at least one target component. The server deploys the resource files corresponding to the target component to the server through the deployer (S304). Optionally, the target component information may also include priority information. The server deploys the resource files corresponding to the target component to the server according to the priority order of the target component. Wherein, the priority information is used to indicate the deployment order of each target component. The flexibility and personalization of component deployment can be improved.

[0139] The server sends the deployment information to the client device of the first user (S305). The deployment information is generated by the server after the resource file of the target component is deployed on the server. The client device of the first user receives the deployment information, and the client device of the first user renders the front-end page of the application corresponding to the target component according to the deployment information (S306). The deployment information includes routing information; the routing information is used to indicate the address information of the resource file of the target component after it is deployed on the server. Specifically, the client device of the first user runs a rendering engine, and the client device of the first user creates a micro-front-end object through the rendering engine, obtains the front-end page file corresponding to the target component according to the routing information, and renders the front-end page of the application corresponding to the target component. The first user can access the application corresponding to each target component through the control or window in the front-end page of each target component rendered by the client device. Specifically, the client device of the first user sends a second access request to the server through the front-end page of the application corresponding to the target component. After receiving the second access request, the server responds to the second access request through the back-end service of the application corresponding to the target component, and sends the return information corresponding to the second access request processed by the back-end service of the application corresponding to the target component to the client of the first user. Optionally, the client device of the first user saves the received deployment information, so that when the first user requests to obtain a page of the application component again, rendering efficiency can be improved.

[0140] For example, take the application as an online banking application. The online banking application uses a microservice architecture to provide different financial services and a micro-frontend architecture to implement pages for different financial services. A component includes corresponding backend services and frontend pages. The first user sends a first access request to the server, and the server determines that the first user is an administrator role based on the identification information of the first user. According to the preset mapping relationship, it can be determined that the permission information corresponding to the first user is the administrator's permission. Among them, the permission information is used to indicate the target component that has access rights, and the target component is the component of the application that the first user has access rights to. Specifically, the functions of the application corresponding to the component that the administrator has access rights to are account management, transfer management, and loan approval. The server can generate a permission menu based on the permission information of the first user. Among them, the permission menu includes the ID corresponding to the component whose application functions are transfer management and loan approval, the path information of each component, and the priority information of each component. For example, the permission menu corresponding to the administrator is shown in the following program:

[0141]

[0142]

[0143] Optionally, the server can obtain a modification request, and delete or add a target component in the above-mentioned administrator authority menu according to the modification request, and update the above-mentioned administrator authority menu.

[0144] The server determines the path information of each target component based on the above-mentioned permission menu, and obtains the resource files of each component of the application whose functions are transfer management and loan approval from the database. The server deploys the resource files of the components of the application whose functions are account management, transfer management, and loan approval on the server based on the priority information in the permission menu. For example, the components of the application whose functions are transfer management and loan approval can be software packages, that is, the server obtains the image files of each component based on the description files of each software package, and deploys each image file on the server. The image file indicates the backend service of each target component. The server sends the deployment information to the client device of the first user. The deployment information includes routing information, and the routing information is used to indicate the address information of the resource files of each component of the application whose functions are transfer management and loan approval in the server. For example, the deployment information is shown in the following program:

[0145]

[0146] When the client device receives the deployment information, it uses the rendering engine to render the pages corresponding to the front-end page files corresponding to the components of the application's functions of transfer management and loan approval according to the routing information in the deployment information. Specifically, the client device can create a micro-front-end object through the rendering engine, obtain the routing information of the components of the application's functions of transfer management and loan approval, which can be the URL in the above program, and generate each front-end page according to the URL rendering. The client device saves the deployment information, and when the first user logs in or accesses, it determines whether the deployment information exists. If the client device has already obtained the deployment information, it uses the rendering engine to render the pages corresponding to the front-end page files corresponding to the components according to the deployment information, thereby improving rendering efficiency and user experience.

[0147] In summary, an embodiment of the present application provides a method for deploying components of an application, which is executed by a server. The method includes: the server determines the permission information corresponding to the first user; and according to the permission information corresponding to the first user, obtains the target component. The permission information is used to indicate the component corresponding to the application that the user has the right to access, and the target component is the component of the application that the first user has the right to access. The server obtains the resource file of the target component, and the server deploys the resource file of the target component to the server. The resource file is used to implement the function of the application corresponding to the target component. The server sends the deployment information to the client of the first user. The deployment information is used by the client to render the front-end page of the application corresponding to the target component. When the client device of the first user receives the deployment information, it renders the front-end page of the application corresponding to the target component according to the deployment information. The first user can access the application corresponding to each target component through the control or window in the front-end page of the application rendered by the client device. In the above method, dynamic deployment and rendering are implemented for the permission information of different users, that is, the resource file corresponding to the target component that the first user has the right to access is deployed to the business server according to the permission of the first user, so that the client of the first user renders the front-end page corresponding to the application that the first user has the right to access. Similarly, according to the second user's permissions, the resource files of the components corresponding to the application that the second user has the right to access are deployed to the server, so that the second user's client renders the front-end page of the application that the second user has the right to access. This can prevent users from accessing or attacking the corresponding components of applications that they do not have the right to access, reduce the risk of data leakage, and improve data security.

[0148] The above mainly introduces the scheme of the embodiment of the present application from the perspective of the method. It is understandable that in order to realize the above functions, the component deployment device of the application includes at least one of the hardware structure and software modules corresponding to the execution of each function. It should be easily appreciated by those skilled in the art that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the embodiments of the present application.

[0149] The embodiment of the present application can divide the component deployment device of the application into functional units according to the above method example. For example, each functional unit can be divided according to each function, or two or more functions can be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of software functional units. It should be noted that the division of units in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation.

[0150] For example, Fig.10 A schematic diagram showing the structure of a component deployment device 400 for an application provided in an embodiment of the present application is shown.

[0151] like Fig.10 As shown, the component deployment device of the application can be applied to a server, and the component deployment device 400 of the application includes:

[0152] The processing module 401 is used to determine permission information corresponding to the first user, where the permission information is used to indicate components corresponding to the application that the user is authorized to access.

[0153] The acquisition module 402 is used to acquire the target component according to the permission information corresponding to the first user; the target component is a component of the application that the first user has the right to access; the target component includes a resource file; the resource file is used to implement the function of the application corresponding to the target component.

[0154] The deployment module 403 is used to deploy the resource files of the target component to the server.

[0155] The sending module 404 is used to send the deployment information to the client of the first user so that the client renders the front-end page of the application according to the deployment information; the deployment information is generated when the resource file of the target component is deployed on the server.

[0156] In a possible implementation, the processing module 401 is further used to determine path information of the target component, where the path information is used to indicate the location of the target component in the database.

[0157] In a possible implementation, the processing module 401 is further configured to determine permission information corresponding to the first user according to the identification information of the first user.

[0158] In one possible implementation, the processing module 401 is also used to determine the permission information corresponding to the first user based on the identification information of the first user and the first mapping relationship; the first mapping relationship is the correspondence between the identification information and permission information of the user of the application; the first user is the user in the first mapping relationship.

[0159] In a possible implementation manner, the processing module 401 is further configured to update the permission information corresponding to at least one user in the first mapping relationship according to the modification request.

[0160] In a possible implementation, the acquisition module 402 is further used to acquire resource files of the target component from a database, where the resource files include front-end page files and back-end service files.

[0161] In a possible implementation, the acquisition module 402 is further used to acquire a modification request; the modification request is used to indicate modification of the permission information corresponding to at least one user in the first mapping relationship.

[0162] In a possible implementation, the acquisition module 402 is further used to obtain a first access request from a first user; the first access request includes identification information of the first user; and the first access request is used to instruct the server to deploy a component corresponding to an application that the first user has the right to access.

[0163] In a possible implementation, the deployment module 403 is further used to determine priority information of each target component when there are multiple target components, and the priority information is used to indicate the deployment order of each target component;

[0164] According to the priority order of the multiple target components, resource files corresponding to the multiple target components are deployed to the server.

[0165] Optionally, the component deployment device 400 of the application can be applied to Figure 3 In the server 110 shown.

[0166] For a detailed description of the above optional methods, please refer to the above method embodiments, which will not be repeated here. In addition, the explanation of the component deployment device 400 of any application provided above and the description of the beneficial effects can refer to the above Figure 7 The corresponding method embodiments will not be described in detail.

[0167] The embodiment of the present application can divide the component rendering device of the application into functional units according to the above method example. For example, each functional unit can be divided corresponding to each function, or two or more functions can be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of software functional units. It should be noted that the division of units in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation.

[0168] For example, Fig.11 FIG. 8 is a schematic diagram showing the structure of a component rendering device 800 of an application provided in an embodiment of the present application. Fig.11As shown, the component rendering device of the application can be applied to a client device, and the component rendering device 800 of the application includes:

[0169] The processing module 801 is used to respond to a target operation of a first user.

[0170] The rendering module 802 is used to render the front-end page of the application corresponding to the target component according to the deployment information sent by the server when the deployment information is obtained; the deployment information is generated when the resource file of the target component is deployed on the server; the target component is the component of the application that the first user has the right to access.

[0171] In one possible implementation, the processing module 801 is also used to send a first access request when the deployment information sent by the server is not obtained, so that the server determines the permission information of the first user based on the first access request, obtains the resource file of the target component corresponding to the application that the first user has the right to access; deploys the resource file to the server; the permission information is used to indicate the component corresponding to the application that the user has the right to access; the first request includes identification information of the first user, and the identification information has a corresponding relationship with the permission information of the first user.

[0172] For a detailed description of the above optional methods, please refer to the above method embodiments, which will not be repeated here. Figure 8 The corresponding method embodiments will not be described in detail.

[0173] The present application embodiment also provides a computer program product including instructions, when the instructions are run on a computer, the computer executes the component deployment method of any one of the applications in the above embodiments. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website site, a computer, a server, or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server, or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server, a data center, etc. that includes one or more servers that can be integrated with the medium. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., an SSD), etc.

[0174] It should be noted that the above-mentioned device for storing computer instructions or computer programs provided in the embodiments of the present application, such as but not limited to, the above-mentioned memory, computer-readable storage medium and communication chip, etc., all have non-volatile (non-transitory). Those skilled in the art should be aware that in the above one or more examples, the functions described in the embodiments of the present application can be implemented with hardware, software, firmware or any combination thereof. When implemented using software, these functions can be stored in a computer-readable storage medium or transmitted as one or more instructions or codes on a computer-readable storage medium. Computer-readable storage media include computer storage media and communication media, wherein the communication medium includes any medium that is convenient for transmitting a computer program from one place to another. The storage medium can be any available medium that a general or special-purpose computer can access.

[0175] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A component deployment method for an application, characterized in that: The method is executed by a server and includes: Determining permission information corresponding to the first user, where the permission information is used to indicate components corresponding to the application that the user is authorized to access; According to the permission information corresponding to the first user, a target component is obtained; the target component is a component of the application that the first user has the right to access; the target component includes a resource file; the resource file is used to implement the function of the application corresponding to the target component; Deploy the resource files of the target component to the server; The deployment information is sent to the client of the first user so that the client renders the front-end page of the application according to the deployment information; the deployment information is generated when the resource file of the target component is deployed on the server.

2. The method according to claim 1, characterized in that Before deploying the resource file of the target component to the server, the method further includes: Determine path information of the target component, where the path information is used to indicate a location of the target component in a database; The resource files of the target component are obtained from the database, wherein the resource files include a front-end page file and a back-end service file.

3. The method according to claim 1, characterized in that The determining the authority information corresponding to the first user includes: Obtaining a first access request of the first user; the first access request includes identification information of the first user; the first access request is used to instruct the server to deploy a component corresponding to the application that the first user has the right to access; The permission information corresponding to the first user is determined according to the identification information of the first user.

4. The method according to claim 3, characterized in that The determining, according to the identification information of the first user, the permission information corresponding to the first user includes: According to the identification information of the first user and a first mapping relationship, the permission information corresponding to the first user is determined; the first mapping relationship is the correspondence between the identification information and permission information of the user of the application; the first user is the user in the first mapping relationship.

5. The method according to claim 4, characterized in that The method further comprises: Obtaining a modification request; the modification request is used to instruct to modify the permission information corresponding to the user in the first mapping relationship; According to the modification request, the authority information corresponding to the user in the first mapping relationship is updated.

6. The method according to any one of claims 1 to 5, characterized in that The deployment information includes routing information; the routing information is used to indicate address information of the resource file of the target component after being deployed on the server.

7. The method according to any one of claims 1 to 6, characterized in that There are multiple target components, and deploying resource files corresponding to the target components to the server includes: Determine priority information of each of the target components, where the priority information is used to indicate a deployment order of each of the target components; The resource files of the multiple target components are deployed to the server according to the priority order of the multiple target components.

8. A component rendering method for an application, characterized in that: The method is performed by a client device and includes: In response to the target operation of the first user, when the deployment information sent by the server is acquired, rendering the front-end page of the application corresponding to the target component according to the deployment information; The deployment information is generated when the resource file of the target component is deployed on the server; the target component is a component corresponding to the application that the first user has the right to access.

9. The method according to claim 8, characterized in that The method further comprises: In the case where the deployment information sent by the server is not obtained, sending a first access request, so that the server determines the permission information of the first user according to the first access request, and obtains the resource file of the target component corresponding to the application that the first user has the right to access according to the permission information; and deploys the resource file to the business server; The permission information is used to indicate the components corresponding to the application that the user has the right to access; the first request includes identification information of the first user, and the identification information has a corresponding relationship with the permission information of the first user.

10. The method according to claim 8 or 9, characterized in that: The deployment information includes routing information; the routing information is used to indicate address information of the resource file of the target component after being deployed on the server.

11. A server, characterized in that: The server comprises: a processor and a memory for storing instructions executable by the processor; The processor is configured to execute the instructions so that the server executes the component deployment method of the application according to any one of claims 1 to 7.

12. A client device, characterized in that: The client device includes: a processor and a memory for storing instructions executable by the processor; The processor is configured to execute the instruction so that the server executes the component rendering method of the application according to any one of claims 8 to 10.

Images