Front-end engineering service and resource management method, device, equipment and medium

Abstract

The invention relates to a front-end engineering service and resource management method and device, equipment and a medium. The method comprises the following steps: receiving an interaction request sent by at least one controlled front-end application development VUE project, and obtaining a timestamp corresponding to the moment when the interaction request is received; wherein the interaction request is generated by responding to operation triggering of a user on a page of the VUE project after the VUE project is successfully started; for each interaction request, in response to the interaction request, obtaining the use state of the corresponding VUE project according to the project identifier in the interaction request, and updating the latest time of the corresponding use state of the corresponding VUE project to the timestamp corresponding to the interaction request; for each VUE project, determining the idle duration of the VUE project according to a preset time interval and the latest time of the use state corresponding to the VUE project; and closing the first VUE project of which the idle duration exceeds the preset duration, and clearing the cache data of the first VUE project. According to the method and the device, storage resources of idle projects can be recycled.

Description

Technical Field

[0001] The present application relates to the field of application development technology, and in particular to a front-end engineering service and resource management method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] As digital transformation accelerates, low-code platforms, as efficient, flexible, and easy-to-use software development platforms, are increasingly favored by businesses and developers. By providing pre-built components, modules, and a visual development interface, low-code platforms significantly lower the barrier to entry for software development, enabling even non-professional developers to quickly build feature-rich applications.

[0003] The process of developing front-end applications using low-code platforms consists of two phases: the first phase involves developing the front-end application development project, or "Web" (World Wide Web) in English, on the low-code platform; the second phase involves developing the front-end application within the front-end application development project. Because low-code platforms typically support rapid iteration and frequent deployment, this process generates a large number of temporary files, which consumes significant storage resources. Summary of the Invention

[0004] Based on this, it is necessary to provide a front-end engineering service and resource management method, device, equipment and medium that can recycle storage resources of idle projects in response to the above technical problems.

[0005] In a first aspect, the present application provides a front-end engineering service and resource management method, which is applied to a management node, including:

[0006] Receive an interaction request sent by at least one controlled front-end application development VUE project, and obtain a timestamp corresponding to the moment of receiving the interaction request; wherein the interaction request is triggered and generated in response to a user operation on a page of the VUE project after the VUE project is successfully started; the request carries a project identifier of the VUE project;

[0007] For each interaction request, in response to the interaction request, obtain the usage status of the corresponding VUE project according to the project identifier in the interaction request, and update the latest time of the usage status of the corresponding VUE project to the timestamp corresponding to the interaction request;

[0008] For each VUE project, determining the idle time of the VUE project according to the latest time of the corresponding usage status of the VUE project at a preset time interval;

[0009] A first VUE project whose idle time exceeds a preset time is closed, and cached data of the first VUE project is cleared.

[0010] In one embodiment, the method further includes: after closing the first VUE project, if the first VUE project is not started within a first preset time period after being closed, clearing disk data corresponding to the first VUE project.

[0011] In one embodiment, the method further includes: obtaining a second VUE project that fails to start and a second VUE project that succeeds in starting and is not closed, and obtaining a third VUE project that has cached data; when the second VUE project is inconsistent with the third VUE project, processing the second VUE project and / or the third VUE project so that the processed second VUE project corresponds one-to-one to the third VUE project.

[0012] In one embodiment, when the second VUE project is inconsistent with the third VUE project, processing the second VUE project and / or the third VUE project includes: selecting a fourth VUE project other than the third VUE project from the second VUE project, and closing the fourth VUE project.

[0013] In one embodiment, when the second VUE project is inconsistent with the third VUE project, processing the second VUE project and / or the third VUE project includes: selecting a fifth VUE project other than the second VUE project from the third VUE project, and clearing cache data corresponding to the fifth VUE project.

[0014] In one embodiment, the method further includes: when the number of control failures corresponding to at least one VUE project controlled within a second preset time period reaches a preset number threshold, taking the VUE control function in the management node offline, and after monitoring that the VUE control function has been repaired, bringing the VUE control function in the management node online.

[0015] In a first aspect, the present application provides a front-end engineering service and resource management device, which is applied to a management node and includes:

[0016] A request receiving module, configured to receive an interaction request sent by at least one controlled front-end application development VUE project, and obtain a timestamp corresponding to the moment of receiving the interaction request; wherein the interaction request is generated after the VUE project is successfully started, in response to a user's operation on the page of the VUE project; the request carries the project identifier of the VUE project;

[0017] A time updating module is configured to, for each interaction request, obtain the usage status of the corresponding VUE project according to the project identifier in the interaction request in response to the interaction request, and update the latest time corresponding to the usage status of the corresponding VUE project to the timestamp corresponding to the interaction request;

[0018] A duration determination module is used to determine, for each VUE project, an idle duration of the VUE project according to the latest time of the corresponding usage status of the VUE project at a preset time interval;

[0019] The project processing module is used to close a first VUE project whose idle time exceeds a preset time and clear cache data of the first VUE project.

[0020] In a third aspect, the present application further provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the front-end engineering service and resource management method provided in the first aspect when executing the computer program.

[0021] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the front-end engineering service and resource management method provided in the first aspect.

[0022] In a fifth aspect, the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the front-end engineering service and resource management method provided in the first aspect.

[0023] In the above-mentioned front-end engineering service and resource management method, apparatus, device, and medium, after receiving an interaction request sent by a VUE project, the management node updates the latest time of the VUE project's usage status corresponding to the project identifier in the interaction request to the timestamp corresponding to the interaction request. In this way, for each VUE project, the idle time of the VUE project is determined based on the latest time of the VUE project's corresponding usage status at a preset time interval, thereby screening out the first VUE project whose idle time exceeds the preset time, and then shutting down the first VUE project. This can reduce the system resources occupied by the first VUE project. Furthermore, the cached data of the first VUE project is cleared to recycle the cached resources of the first VUE project, thereby improving the performance of the management node. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0025] Figure 1 A flowchart of a front-end engineering service and resource management method in one embodiment;

[0026] Figure 2 A flowchart of a front-end engineering service and resource management method in one embodiment;

[0027] Figure 3 A flowchart of a front-end engineering service and resource management method in one embodiment;

[0028] Figure 4 is a structural block diagram of a front-end engineering service and resource management device in one embodiment;

[0029] Figure 5 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0030] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0031] Currently, when users develop VUE projects on low-code platforms, they often debug the code online multiple times. When the VUE project is developed, many temporary files will be generated. Temporary files will not only occupy more cache resources, but may also cause performance degradation.

[0032] In order to improve the above problems, in an exemplary embodiment, a front-end engineering service and resource management method is provided, which is applied to the management node. Figure 1 , the method comprises the following steps:

[0033] S110, receiving an interaction request sent by at least one controlled front-end application development VUE project, and obtaining a timestamp corresponding to the moment when the interaction request is received; wherein the interaction request is triggered and generated in response to a user operation on a page of the VUE project after the VUE project is successfully started; the request carries a project identifier of the VUE project.

[0034] In actual scenarios, there are multiple management nodes in the cluster, and a project management system is deployed on each management node. The role of the project management system is to control the startup and shutdown of VUE projects. It can be seen that VUE management and control functions can be implemented based on the project management system. A project management system can control the startup and shutdown of one or more VUE projects. The VUE projects controlled by the project management system are scheduled by the scheduling service system, that is, the scheduling service system is responsible for selecting the project management system that controls the startup and shutdown of the VUE project.

[0035] It is understood that after a VUE project is successfully launched, it becomes a front-end application, and users can develop other front-end applications as needed on the VUE project. For the sake of distinction, whether a VUE project becomes a front-end application or not is referred to as a VUE project. The front-end application in this embodiment refers to other front-end applications developed on the VUE project.

[0036] Interaction requests are requests that the VUE project needs to interact with the backend management node to obtain the required information. For example, a user performs a resource acquisition operation on the VUE project page, and the VUE project generates a resource acquisition request, which is then sent to the backend management node.

[0037] In order for the backend management node to determine the source of the interaction request, the interaction request generated by the VUE project is added with the project ID of the VUE project. The project ID is the unique identifier of the VUE project. In order to facilitate the subsequent determination of the idle time, when receiving the interaction request, the system timestamp corresponding to the current moment is obtained as the timestamp corresponding to the interaction request.

[0038] The VUE project is a front-end application development project based on the Node.js framework. It covers a series of standardized development processes, technology selection, and engineering practices, aiming to improve development efficiency, code quality, and project maintainability. The Node.js framework is an open-source, cross-platform JavaScript runtime environment.

[0039] S120 , for each interaction request, in response to the interaction request, obtaining the usage status of the corresponding VUE project according to the project identifier in the interaction request, and updating the latest time corresponding to the usage status of the corresponding VUE project to the timestamp corresponding to the interaction request.

[0040] That is, after receiving each interactive request, the back-end management node obtains the timestamp corresponding to the current moment, parses the interactive request, and obtains the project identifier of the interactive request. Based on the project identifier, the usage status of the corresponding VUE project can be obtained, and then the latest time of the usage status of the corresponding VUE project is updated to the timestamp corresponding to the interactive request.

[0041] The latest time of the usage status of the VUE project is a timestamp used in the process of the most recent time update of the usage status of the VUE project.

[0042] S130 , for each VUE project, determining the idle time of the VUE project according to the latest time of the corresponding usage status of the VUE project at a preset time interval.

[0043] The preset time interval can be set as needed, for example, 30 minutes, 1 hour, etc.

[0044] In an optional implementation, for each VUE project, the duration between the current time and the latest time of the corresponding usage status of the VUE project is calculated as the idle duration of the VUE project.

[0045] S140 , closing the first VUE project whose idle time exceeds a preset time, and clearing the cached data of the first VUE project.

[0046] The preset duration can be set as needed, for example, 2 hours.

[0047] Specifically, if a VUE project's idle time exceeds a preset duration, the VUE project is considered idle. For ease of distinction, the idle project is referred to as the first VUE project. The management node shuts down the first VUE project, thereby reducing system resources, such as RAM, used by the first VUE project. Furthermore, the cached data of the first VUE project is cleared, thereby reclaiming the cached resources of the first VUE project.

[0048] It is understandable that the actual project status of the VUE project includes the use status and the idle status, but in the application scenario, only one project status is marked for the VUE project: the use status, and the latest time of the use status is marked. Therefore, when the project status of the VUE project is marked as the use status, the VUE project may be in the use status or the idle status. However, by calculating the time between the current moment and the latest time of the use status of the VUE project, the idle time of the VUE project can be obtained, and thus whether the VUE project is an idle project can be determined based on the idle time of the VUE project. In this way, there is no need to set the project status of the VUE project from the idle state to the use status every time the VUE project is started, nor is there any need to set the project status of the VUE project to the idle state after being idle for a long time or after closing the VUE project, thereby simplifying the operation of the management node.

[0049] It can be seen that after receiving the interaction request sent by the VUE project, the management node updates the latest time of the usage status of the VUE project corresponding to the project identifier in the interaction request to the timestamp corresponding to the interaction request. In this way, for each VUE project, the idle time of the VUE project is determined according to the latest time of the corresponding usage status of the VUE project at a preset time interval, thereby screening out the first VUE project whose idle time exceeds the preset time, and then shutting down the first VUE project, which can reduce the system resources occupied by the first VUE project. In addition, the cache data of the first VUE project is cleared to realize the recovery of the cache resources of the first VUE project and improve the performance of the management node.

[0050] Furthermore, this embodiment recycles idle projects, not only aligning with the efficient and flexible development philosophy of low-code platforms, but also meeting the urgent needs of enterprises for resource optimization, performance improvement, and security assurance. Furthermore, manual cleanup is unnecessary, improving resource recovery efficiency and reducing the probability of errors.

[0051] Based on the technical solutions of the above embodiments, multiple embodiments are introduced below.

[0052] In one embodiment, the front-end engineering service and resource management method further includes:

[0053] After the first VUE project is closed, if the first VUE project is not started within a first preset time period after being closed, the disk data corresponding to the first VUE project is cleared.

[0054] The first preset time period can be set as needed, for example, to three days.

[0055] It can be seen that the first VUE project has not been started within the first preset time period after being closed, indicating that the first VUE project is not used frequently. Its disk data can be cleared to recycle the disk resources of the first VUE project. This is a disk cleanup strategy.

[0056] In one embodiment, see Figure 2 , the front-end engineering service and resource management method shown also includes:

[0057] S210, obtaining a second VUE project that fails to start and a second VUE project that succeeds and is not closed, and obtaining a third VUE project that has cached data.

[0058] Among them, the results of the management node controlling the startup of the VUE project include: startup failure and startup success. The cache data of the closed VUE project will be cleared in a timely manner during the process of closing the VUE project. The VUE project that successfully started and was not closed should have corresponding cache data. The VUE project that failed to start should not have cache data. To distinguish them, the VUE projects that failed to start and those that successfully started and were not closed are both called second VUE projects.

[0059] It is worth noting that there is a special case: the cached data of a VUE project that is successfully started and not closed is lost, so the VUE project actually does not have corresponding cached data. A VUE project that fails to start should not have cached data, but in fact some cached data may be generated during the startup process. The VUE project that actually has cached data is called the third VUE project.

[0060] S220 , when the second VUE project is inconsistent with the third VUE project, processing the second VUE project and / or the third VUE project so that the processed second VUE project corresponds to the third VUE project one-to-one.

[0061] It is understandable that if the second VUE project is consistent with the third VUE project, that is, the second VUE project corresponds to the third VUE project one-to-one, then there is no problem of cached data loss at this time, and there is no problem of cached data in the VUE project that failed to start and was not cleared in time.

[0062] It is understood that if the second VUE project is inconsistent with the third VUE project, that is, the second VUE project and the third VUE project are not in a one-to-one correspondence, it means that there is a problem of cache data loss, or the cache data of the VUE project that failed to start was not cleared in time. To solve the above problem, the second VUE project and / or the third VUE project are processed to ensure that the processed second VUE project corresponds to the third VUE project.

[0063] Furthermore, in one embodiment, when the second VUE project and the third VUE project are inconsistent in S220 , processing the second VUE project and / or the third VUE project may include: selecting a fourth VUE project excluding the third VUE project from the second VUE project, and closing the fourth VUE project.

[0064] It is understandable that if there are other VUE projects in addition to the third VUE project in the second VUE project, the other VUE project is called the fourth VUE project, which means that the fourth VUE project is a VUE project with cache loss. At this time, the fourth VUE project is closed to avoid abnormal operation of the fourth VUE project due to the absence of cache data.

[0065] Furthermore, in one embodiment, when the second VUE project and the third VUE project are inconsistent in S220, processing the second VUE project and / or the third VUE project may include: selecting a fifth VUE project other than the second VUE project from the third VUE project, and clearing cache data corresponding to the fifth VUE project.

[0066] It is understandable that if there are other VUE projects in addition to the second VUE project in the third VUE project, and the other VUE projects are called the fifth VUE project, then it means that the fifth VUE project is the VUE project that failed to start, and the VUE project has cached data and has not been cleared in time. At this time, the cached data corresponding to the fifth VUE project is cleared, thereby releasing the cache resources of the VUE project that failed to start.

[0067] For example, see Figure 3 After the VUE project on the control front end is started, the user can debug the VUE project online on the front end, and a large number of temporary files will be generated during the online debugging process. When the user operates on the page of the VUE project, an interactive request is generated and sent to the management node on the back end. The management node updates the latest time of the usage status of the VUE project corresponding to the project identifier in the interactive request to the timestamp corresponding to the interactive request. Then, according to the preset time interval, it is determined whether the idle time of the VUE project exceeds the preset time. If it exceeds, the VUE project is closed, the cached data is cleared, and the disk cleanup policy is enabled. In the case that the second VUE project and the third VUE project are inconsistent, if the VUE project includes a fourth VUE project in addition to the third VUE project, the fourth VUE project is closed.

[0068] In one embodiment, the front-end engineering service and resource management method further includes:

[0069] When the number of control failures corresponding to at least one VUE project controlled within the second preset time period reaches a preset threshold, the VUE control function in the management node is taken offline, and after monitoring that the VUE control function has been repaired, the VUE control function in the management node is brought online.

[0070] The second preset time period can be set as needed, for example, 5 minutes or 10 minutes.

[0071] The preset number threshold can be set as needed, for example, 3 times or 5 times.

[0072] In actual scenarios, there may be situations where the management node fails to control the startup of the VUE project using the VUE control function due to environmental problems, etc. If, within a second preset time period, the total number of times a management node fails to control the startup or shutdown of the VUE project using the VUE control function reaches a preset threshold, the VUE control function on the management node is considered to have failed, and the VUE control function can be marked as failed and taken offline. The operation and maintenance personnel can also be notified so that the operation and maintenance personnel can perform repairs. When the management node monitors that the VUE control function has been repaired, the VUE control function is brought online, so that the VUE control function can continue to be used to control the startup or shutdown of the VUE project.

[0073] It can be seen that the above process is a self-check method of the VUE control function, that is, a method of checking whether the VUE control function is faulty through the management node where the VUE control function is located. The VUE control function is implemented by the engineering management system.

[0074] In actual scenarios, since the engineering management system on each management node is scheduled by the scheduling service system, the scheduling service system can also be used to perform health detection to comprehensively detect whether the VUE control function on each management node is faulty.

[0075] In one optional implementation, the dispatch service system sends health detection instructions to each management node at preset time intervals (e.g., every five seconds). After receiving the health detection instructions, each management node performs a health check on its own VUE control function. If the test result is healthy, a healthy response is sent to the dispatch service system; if the test result is unhealthy, an unhealthy response is sent to the dispatch service system. If the dispatch service system does not receive a response from the management node within a preset time (e.g., five minutes), or if the number of unhealthy responses received from the management node reaches a preset number (e.g., five times) within a preset time (e.g., five minutes), the VUE control function on the management node is determined to be faulty, and the VUE control function on the management node is then taken offline. Operations and maintenance personnel may also be notified so that they can perform repairs. When it is detected that the VUE control function of the management node has been repaired, the VUE control function of the management node is brought online.

[0076] It can be seen that by detecting whether the VUE control function of the management node is faulty through live detection, and handling the fault in a timely manner if it is faulty, it can reduce security risks, reduce the maintenance cost of the cluster, and improve the stability and high availability of the control VUE project. It is of great significance to promote the sustainable development of the low-code platform and improve the efficiency of the digital transformation of enterprises.

[0077] Based on the same inventive concept, the embodiments of the present application also provide a front-end engineering service and resource management device for implementing the front-end engineering service and resource management method involved above. The implementation solution provided by this device is similar to the implementation solution described in the above method. Therefore, the specific limitations in one or more front-end engineering service and resource management device embodiments provided below can be found in the above-mentioned limitations on the front-end engineering service and resource management method, and will not be repeated here.

[0078] In an exemplary embodiment, Figure 4 As shown, a front-end engineering service and resource management device is provided, which is applied to a management node and includes: a request receiving module 410, a time updating module 420, a duration determining module 430 and an engineering processing module 440, wherein:

[0079] A request receiving module, configured to receive an interaction request sent by at least one controlled front-end application development VUE project, and obtain a timestamp corresponding to the moment of receiving the interaction request; wherein the interaction request is generated after the VUE project is successfully started, in response to a user's operation on the page of the VUE project; the request carries the project identifier of the VUE project;

[0080] A time updating module is configured to, for each interaction request, obtain the usage status of the corresponding VUE project according to the project identifier in the interaction request in response to the interaction request, and update the latest time corresponding to the usage status of the corresponding VUE project to the timestamp corresponding to the interaction request;

[0081] A duration determination module is used to determine, for each VUE project, an idle duration of the VUE project according to the latest time of the corresponding usage status of the VUE project at a preset time interval;

[0082] The project processing module is used to close a first VUE project whose idle time exceeds a preset time and clear cache data of the first VUE project.

[0083] In one embodiment, the apparatus further comprises:

[0084] The disk clearing module is configured to clear the disk data corresponding to the first VUE project if the first VUE project is not started within a first preset time period after the first VUE project is closed.

[0085] In one embodiment, the apparatus further comprises:

[0086] The project acquisition module is used to obtain the second VUE project that failed to start and successfully started but was not closed, and to obtain the third VUE project with cached data;

[0087] The consistency processing module is used to process the second VUE project and / or the third VUE project when the second VUE project is inconsistent with the third VUE project, so that the processed second VUE project corresponds to the third VUE project one by one.

[0088] In one embodiment, the consistency processing module is specifically configured to: select a fourth VUE project excluding the third VUE project from the second VUE project, and close the fourth VUE project.

[0089] In one embodiment, the consistency processing module is specifically configured to: select a fifth VUE project excluding the second VUE project from the third VUE project, and clear cache data corresponding to the fifth VUE project.

[0090] In one embodiment, the apparatus further comprises:

[0091] The online and offline module is used to offline the VUE control function in the management node when the number of control failures corresponding to at least one VUE project controlled within a second preset time period reaches a preset number threshold, and to online the VUE control function in the management node after monitoring that the VUE control function has been repaired.

[0092] Each module in the front-end engineering service and resource management device can be implemented in whole or in part through software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in hardware form, or can be stored in a computer device memory in software form, so that the processor can call and execute the corresponding operations of each module.

[0093] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 5As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, abbreviated as I / O) and a communication interface. The processor, memory and input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. 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, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store relevant data. 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 through a network connection. When the computer program is executed by the processor, a front-end engineering service and resource management method is implemented.

[0094] The above-mentioned computer device is specifically a management node.

[0095] Those skilled in the art will understand that Figure 5 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 shown in the figure, or combine certain components, or have a different component arrangement.

[0096] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the front-end engineering service and resource management method provided in the first aspect is implemented.

[0097] The above-mentioned computer device is specifically a management node.

[0098] In an exemplary embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the front-end engineering service and resource management method provided in the first aspect is implemented.

[0099] In an exemplary embodiment, a computer program product is provided, including a computer program, which, when executed by a processor, implements the front-end engineering service and resource management method provided in the first aspect.

[0100] Those skilled in the art will understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. In particular, any reference to memory, database, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The databases involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the various embodiments provided herein may be, but are not limited to, general-purpose processors, central processing units (CPUs), graphics processing units (GPUs), digital signal processors (DSPs), programmable logic devices (PLDs), quantum computing-based data processing logic devices, artificial intelligence (AI) processors, and the like.

[0101] The technical features of the above embodiments can be combined arbitrarily. In order 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 application.

[0102] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A front-end engineering service and resource management method, characterized in that: Applicable to management nodes, including: Receive an interaction request sent by at least one controlled front-end application development VUE project, and obtain a timestamp corresponding to the moment of receiving the interaction request; wherein the interaction request is triggered and generated in response to a user operation on a page of the VUE project after the VUE project is successfully started; the request carries a project identifier of the VUE project; For each interaction request, in response to the interaction request, obtain the usage status of the corresponding VUE project according to the project identifier in the interaction request, and update the latest time of the usage status of the corresponding VUE project to the timestamp corresponding to the interaction request; For each VUE project, determining the idle time of the VUE project according to the latest time of the corresponding usage status of the VUE project at a preset time interval; A first VUE project whose idle time exceeds a preset time is closed, and cached data of the first VUE project is cleared.

2. The method according to claim 1, characterized in that Also includes: After the first VUE project is closed, if the first VUE project is not started within a first preset time period after being closed, the disk data corresponding to the first VUE project is cleared.

3. The method according to claim 1, characterized in that Also includes: Get the second VUE project that failed to start and successfully started but was not closed, and get the third VUE project with cached data; In the case that the second VUE project is inconsistent with the third VUE project, the second VUE project and / or the third VUE project are processed so that the processed second VUE project corresponds to the third VUE project one-to-one.

4. The method according to claim 3, characterized in that When the second VUE project is inconsistent with the third VUE project, processing the second VUE project and / or the third VUE project includes: A fourth VUE project excluding the third VUE project is selected from the second VUE project, and the fourth VUE project is closed.

5. The method according to claim 3, characterized in that When the second VUE project is inconsistent with the third VUE project, processing the second VUE project and / or the third VUE project includes: A fifth VUE project excluding the second VUE project is selected from the third VUE project, and cache data corresponding to the fifth VUE project is cleared.

6. The method according to claim 1, characterized in that Also includes: When the number of control failures corresponding to at least one VUE project controlled within the second preset time period reaches a preset threshold, the VUE control function in the management node is taken offline, and after monitoring that the VUE control function has been repaired, the VUE control function in the management node is put online.

7. A front-end engineering service and resource management device, characterized in that: Applicable to management nodes, including: A request receiving module, configured to receive an interaction request sent by at least one controlled front-end application development VUE project, and obtain a timestamp corresponding to the moment of receiving the interaction request; wherein the interaction request is generated after the VUE project is successfully started, in response to a user's operation on the page of the VUE project; the request carries the project identifier of the VUE project; A time updating module is configured to, for each interaction request, obtain the usage status of the corresponding VUE project according to the project identifier in the interaction request in response to the interaction request, and update the latest time corresponding to the usage status of the corresponding VUE project to the timestamp corresponding to the interaction request; A duration determination module is used to determine, for each VUE project, an idle duration of the VUE project according to the latest time of the corresponding usage status of the VUE project at a preset time interval; The project processing module is used to close a first VUE project whose idle time exceeds a preset time and clear cache data of the first VUE project.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

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

10. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images