Methods, devices, equipment, storage media, and program products for scheduling backend data

Abstract

This invention relates to the field of cloud computing technology, and discloses a method, apparatus, device, storage medium, and program product for scheduling backend data. The backend data scheduling method includes: determining first modification information in response to a triggering of a button component; modifying a first modification object in a parent component data cluster according to the first modification information to obtain a second modification object; modifying a target interface in an interface cluster according to the second modification object, and obtaining backend data from the backend according to the target interface; updating the first cluster data corresponding to the first modification object in the parent component data cluster according to the backend data to obtain second cluster data; and updating the third cluster data corresponding to a third modification object in a child component data cluster according to the second cluster data. This invention clusters child components, parent components, and interface components, and schedules backend data through clustering, improving the interaction efficiency between the frontend and backend.

Description

Technical Field

[0001] This invention relates to the field of cloud computing technology, specifically to methods, apparatus, devices, storage media, and program products for scheduling backend data. Background Technology

[0002] With the popularization and development of cloud computing, many front-end frameworks and tools suitable for cloud environments have emerged in the front-end development field to adapt to cloud computing. For example, front-end frameworks such as React and Vue.js provide rich component libraries and tool libraries, enabling front-end developers to build user interfaces for cloud applications more efficiently.

[0003] Currently, the front-end / back-end separation architecture technology has been widely used in the cloud computing environment. This technology clearly separates the development responsibilities of the front-end (user interface-related development, such as webpage display and interaction) and the back-end (server-side business logic processing, data storage and management), allowing the front-end and back-end to be developed, deployed, and maintained independently. This separated architecture improves the flexibility of front-end development and enhances the maintainability of front-end code.

[0004] However, as cloud computing applications need to process large amounts of data and business logic becomes increasingly complex, the number of structures is growing exponentially. When dealing with large amounts of data and complex business, the front-end and back-end separation architecture technology requires the front-end development and back-end data to interact through multiple separate interfaces. During the front-end development process, a large number of interfaces need to be created, which slows down the response speed between the front-end development and back-end data and reduces the efficiency of interaction between the front-end and back-end. Summary of the Invention

[0005] In view of this, the present invention provides a method, apparatus, device, storage medium and program product for scheduling backend data, so as to solve the problem of low interaction efficiency between the frontend and the backend.

[0006] In a first aspect, the present invention provides a backend data scheduling method comprising: responding to a triggering of a button component, determining first modification information corresponding to the button component, the first modification information being used to characterize modifications to a parent component data cluster and an interface cluster; modifying a first modification object in the parent component data cluster corresponding to the first modification information according to the first modification information to obtain a second modification object; modifying a target interface in the interface cluster corresponding to the second modification object according to the second modification object, and obtaining backend data from the backend according to the target interface, wherein the cluster data in the parent component data cluster corresponds one-to-one with the interfaces in the interface cluster; updating the first cluster data corresponding to the first modification object in the parent component data cluster according to the backend data to obtain second cluster data; and updating the third cluster data corresponding to a third modification object in the child component data cluster according to the second cluster data.

[0007] In response to a button component trigger, this invention determines the first modification information corresponding to the button component, modifies the first modification object corresponding to the first modification information in the parent component data cluster to obtain a second modification object, modifies the target interface corresponding to the second modification object in the interface cluster according to the second modification object, and obtains backend data from the backend according to the target interface. The cluster data in the parent component data cluster corresponds one-to-one with the interfaces in the interface cluster. This invention clusters the parent component data and interfaces, making a one-to-one correspondence between the cluster data in the parent component data cluster and the interfaces in the interface cluster. When the parameters developed on the front end change, the parameters are modified through the relationship between the parent component data cluster and the port cluster, and backend data is obtained from the backend according to the target interface. This avoids the creation of a large number of interfaces, improves the transmission efficiency between modification information and interfaces, simplifies the code structure, and reduces maintenance costs. This invention, after acquiring backend data, updates the first cluster data corresponding to the first modified object in the parent component data cluster based on the backend data, obtaining the second cluster data; then, based on the second cluster data, it updates the third cluster data corresponding to the third modified object in the child component data cluster. This invention effectively integrates parent and child component data through clustered processing, reducing data fragmentation and effectively improving data utilization. Compared with related technologies, this invention, through clustered processing of child component data, parent component data, and interfaces, accelerates the response speed between frontend development and backend data, and improves the interaction efficiency between frontend development and backend data.

[0008] In one optional implementation, the first modification information includes first modification data and a first modification object in the parent component data cluster; modifying the first modification object corresponding to the first modification information in the parent component data cluster according to the first modification information to obtain a second modification object includes: updating the data included in the first modification object to the first modification data to obtain the second modification object.

[0009] The first modification information of the present invention includes first modification data and a first modification object in the parent component data cluster. The data included in the first modification object is directly updated to the first modification data to obtain the second modification object. There is no need to query the first modification object in the parent component data cluster again, thereby improving the modification efficiency of the first modification object.

[0010] In one optional implementation, the second modification object includes first modification data and a target interface identifier; modifying the target interface in the interface cluster corresponding to the second modification object according to the second modification object includes: selecting a target interface from multiple interfaces in the interface cluster according to the target interface identifier; and modifying the attribute parameters corresponding to the target interface to the first modification data.

[0011] The second modification object of the present invention includes first modification data and target interface identifier. Based on the target interface identifier, a target interface is selected from multiple interfaces in the interface cluster, and the attribute parameters corresponding to the target interface are modified to the first modification data. The present invention improves the transmission efficiency of the second modification object and the modification efficiency of attribute parameters by clustering the parent component data and interface, associating the parent component data cluster and the interface cluster.

[0012] In one optional implementation, the target interface includes a location identifier for backend data; obtaining backend data from the backend according to the target interface includes: constructing a request-response function based on a second modified object, and configuring parameters of the request-response function to obtain a target request-response function; and calling the target request-response function to obtain the backend data according to the location identifier of the backend data.

[0013] This invention reduces the use of numerous interfaces and improves the efficiency of acquiring backend data by clustering the interfaces.

[0014] In one optional implementation, updating the third cluster data corresponding to the third modified object in the sub-component data cluster according to the second cluster data includes: performing attribute transformation on the second cluster data based on a preset response function to obtain fourth cluster data; the preset response function is used to convert the reactive attributes of the second cluster data corresponding to the parent component data cluster into non-responsive attributes; and updating the third cluster data corresponding to the third modified object in the sub-component data cluster according to the fourth cluster data.

[0015] In one optional implementation, after updating the third cluster data corresponding to the third modified object in the sub-component data cluster according to the second cluster data, the method further includes: passing the fourth cluster data to the image drawing component, controlling the image drawing component to draw the image to obtain the target image; and controlling the parent component data cluster to update the page by referencing the target image.

[0016] Secondly, the present invention provides a backend data scheduling device, comprising: a first modification information determination module, configured to determine first modification information corresponding to the button component in response to triggering the button component, the first modification information being used to characterize modifications to a parent component data cluster and an interface cluster; a second modification object determination module, configured to modify a first modification object in the parent component data cluster corresponding to the first modification information according to the first modification information, to obtain a second modification object; a backend data acquisition module, configured to modify a target interface in the interface cluster corresponding to the second modification object according to the second modification object, and to acquire backend data from the backend according to the target interface, wherein the cluster data in the parent component data cluster corresponds one-to-one with the interfaces in the interface cluster; a second cluster data determination module, configured to update the first cluster data corresponding to the first modification object in the parent component data cluster according to the backend data, to obtain second cluster data; and a third cluster data update module, configured to update the third cluster data corresponding to the third modification object in the child component data cluster according to the second cluster data.

[0017] Thirdly, the present invention provides a computer device, comprising: a memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the computer instructions to perform the backend data scheduling method of the first aspect or any corresponding embodiment described above.

[0018] Fourthly, the present invention provides a computer-readable storage medium storing computer instructions for causing a computer to execute the backend data scheduling method of the first aspect or any corresponding embodiment described above.

[0019] Fifthly, the present invention provides a computer program product, including computer instructions for causing a computer to execute the backend data scheduling method of the first aspect or any corresponding embodiment described above. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the specific embodiments or related technologies of the present invention, the drawings used in the description of the specific embodiments or related technologies will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0021] Figure 1 This is a flowchart illustrating a backend data scheduling method according to an embodiment of the present invention;

[0022] Figure 2This is a flowchart illustrating another backend data scheduling method according to an embodiment of the present invention;

[0023] Figure 3 This is a flowchart illustrating another backend data scheduling method according to an embodiment of the present invention;

[0024] Figure 4 This is a schematic diagram illustrating the process of drawing and referencing sub-component images according to an embodiment of the present invention;

[0025] Figure 5 This is a schematic diagram of the clustered front-end development method based on the Yunxiao intelligent computing platform according to an embodiment of the present invention;

[0026] Figure 6 This is a structural block diagram of a backend data scheduling device according to an embodiment of the present invention;

[0027] Figure 7 This is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. Detailed Implementation

[0028] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0029] Currently, with the popularization and development of cloud computing, many front-end frameworks and tools suitable for cloud environments have emerged in the front-end development field to adapt to this development. For example, front-end frameworks such as React and Vue.js provide rich component libraries and tool libraries, enabling front-end developers to build user interfaces for cloud applications more efficiently. The front-end / back-end separation architecture technology has also been widely used in the cloud computing environment. This technology clearly separates the development responsibilities of the front-end (user interface-related development, such as webpage display and interaction) and the back-end (server-side business logic processing, data storage and management), allowing the front-end and back-end to be developed, deployed, and maintained independently. This separated architecture improves the flexibility of front-end development and enhances the maintainability of front-end code.

[0030] However, front-end development in cloud computing environments also faces performance optimization challenges. Because cloud computing requires processing massive amounts of data and business logic is becoming increasingly complex, the number of structures is growing exponentially. When handling large amounts of data and complex business logic, the front-end / back-end separation architecture requires multiple separate interfaces for interaction between the front-end and back-end. This necessitates creating numerous interfaces during front-end development. If the parameters used by the front-end change, it may be necessary to recreate the interfaces to retrieve the corresponding back-end data. This results in slow response times between the front-end and back-end, and low interaction efficiency.

[0031] This invention provides a backend data scheduling method that improves the interaction efficiency between the frontend and backend by clustering interfaces.

[0032] According to an embodiment of the present invention, a method for scheduling backend data is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0033] This embodiment provides a backend data scheduling method that can be used in computer equipment. Figure 1 This is a flowchart of a backend data scheduling method according to an embodiment of the present invention, such as... Figure 1 As shown, the process includes the following steps:

[0034] Step S101: In response to the triggering of the button component, determine the first modification information corresponding to the button component. The first modification information is used to characterize the modification of the parent component's data cluster and interface cluster.

[0035] A button component is a graphical user interface element, typically presented as a clickable area of ​​a rectangle or other shape. Users trigger actions bound to the button component by clicking with a mouse, touching the screen (on mobile devices), or using the Enter key on the keyboard (if the button component is set to be keyboard-operable). Examples include modifying parameters, submitting a form, opening a new window, or executing a script. For instance, different button components may represent different backend data retrieval times, such as 5 minutes, 15 minutes, 30 minutes, 1 hour, or 2 hours.

[0036] In some optional implementations, in response to triggering the button component, determining the first modification information corresponding to the button component includes: in response to triggering the button component, determining the button component identifier, and generating the first modification information based on the button component identifier.

[0037] For example, when the button component represents the time of backend data retrieval, in response to the triggering of the button component, if the modification parameter corresponding to the button component identifier is determined to be 5 minutes, then the first modification information is generated. The first modification information includes the first modification data and the first modification object in the parent component data cluster. The first modification data is 5 minutes, and the first modification object is the time variable in the parent component data cluster.

[0038] In some optional implementations, after determining the first modification information corresponding to the button component in response to the triggering of the button component, the backend data scheduling method further includes: passing the first modification information to the child component data cluster, and controlling the child component data cluster to pass the first modification information to the parent component data cluster.

[0039] In some alternative implementations, the first modification information is passed to the parent component's data cluster according to a first transfer function, which is used to pass the child component's data to the parent component.

[0040] The data clusters are categorized into three groups: a sub-component data cluster, a parent component data cluster, and an interface cluster. The sub-component data cluster corresponds one-to-one with the parent component data cluster, and the parent component data cluster corresponds one-to-one with the interfaces in the interface cluster.

[0041] Step S102: Modify the first modified object in the parent component data cluster corresponding to the first modified information according to the first modified information to obtain the second modified object.

[0042] In some optional implementations, the first modification information includes first modification data and a first modification object in the parent component data cluster. Modifying the first modification object in the parent component data cluster corresponding to the first modification information according to the first modification information to obtain a second modification object includes: updating the data included in the first modification object to the first modification data to obtain the second modification object.

[0043] For example, when the first modified data is 5 minutes and the first modified object is the time variable in the parent component's data cluster, the data included in the time variable in the parent component's data cluster is modified to 5 minutes, which means that the time to obtain the backend data from the backend is 5 minutes.

[0044] The first modification information in this embodiment of the invention includes first modification data and a first modification object in the parent component data cluster. The data included in the first modification object is directly updated to the first modification data to obtain the second modification object. There is no need to query the first modification object in the parent component data cluster again, which improves the modification efficiency of the first modification object.

[0045] Step S103: Modify the target interface in the interface cluster corresponding to the second modification object according to the second modification object, and obtain backend data from the backend according to the target interface. The cluster data in the parent component data cluster corresponds one-to-one with the interface in the interface cluster.

[0046] Specifically, the second modified object is passed from the parent component's data cluster to the interface cluster via the interface passing function.

[0047] In some optional implementations, the second modification object includes the first modification data and the target interface identifier; modifying the target interface in the interface cluster corresponding to the second modification object according to the second modification object includes: selecting the target interface from multiple interfaces in the interface cluster according to the target interface identifier; and modifying the attribute parameters corresponding to the target interface to the first modification data.

[0048] In this process, after updating the data included in the first modified object to the first modified data, a second modified object is obtained. The second modified object includes the first modified data. Since the cluster data in the parent component data cluster corresponds one-to-one with the interfaces in the interface cluster, the second modified object includes the target interface identifier in the interface cluster corresponding to the second modified object.

[0049] For example, when the first modified data is 5 minutes and the first modified object is a time variable in the parent component's data cluster, the second modified object includes the first modified data of 5 minutes and the second modified object includes a target interface identifier corresponding to the second modified object. Based on the target interface identifier, a target interface is selected from multiple interfaces in the interface cluster, and the time variable corresponding to the target interface is modified to 5 minutes, which means that the time to obtain backend data from the backend is 5 minutes.

[0050] In some alternative implementations, a target interface corresponds to multiple backend data in the backend, and the target interface includes location identifiers for multiple backend data. When retrieving backend data from the backend according to the target interface, the data is retrieved according to the location identifiers.

[0051] The second modification object in this embodiment of the invention includes first modification data and a target interface identifier. Based on the target interface identifier, a target interface is selected from multiple interfaces in the interface cluster, and the attribute parameters corresponding to the target interface are modified to the first modification data. This embodiment of the invention improves the transmission efficiency of the second modification object and the modification efficiency of attribute parameters by clustering the parent component data and interface, associating the parent component data cluster and the interface cluster.

[0052] Step S104: Based on the backend data, update the first cluster data corresponding to the first modified object in the parent component data cluster to obtain the second cluster data.

[0053] After obtaining the backend data, the backend data is passed to the parent component's data cluster through an interface passing function.

[0054] For example, the backend data represents data obtained from the backend with a time of 5 minutes. The first cluster data corresponding to the time variable in the parent component's data cluster is updated to the backend data.

[0055] Step S105: Update the third cluster data corresponding to the third modified object in the sub-component data cluster based on the second cluster data.

[0056] In this system, the cluster data in the parent component's data cluster corresponds one-to-one with the cluster data in the child component's data cluster.

[0057] In some optional implementations, updating the third cluster data corresponding to the third modified object in the sub-component data cluster according to the second cluster data includes: performing attribute transformation on the second cluster data based on a preset response function to obtain the fourth cluster data; the preset response function is used to convert the reactive attributes of the second cluster data corresponding to the parent component data cluster into non-reactive attributes; and updating the third cluster data corresponding to the third modified object in the sub-component data cluster according to the fourth cluster data.

[0058] The default response function can be the toRefs function, which is a utility function in Vue.js that is mainly used to convert a reactive object (e.g., an object created by the reactive function) into a regular object.

[0059] In some optional implementations, updating the third cluster data corresponding to the third modified object in the subcomponent data cluster according to the fourth cluster data includes: replacing the third cluster data corresponding to the third modified object in the subcomponent data cluster with the fourth cluster data.

[0060] The backend data scheduling method provided in this embodiment responds to the triggering of a button component, determines the first modification information corresponding to the button component, modifies the first modification object corresponding to the first modification information in the parent component data cluster to obtain a second modification object, modifies the target interface corresponding to the second modification object in the interface cluster according to the second modification object, and obtains backend data from the backend according to the target interface. The cluster data in the parent component data cluster corresponds one-to-one with the interfaces in the interface cluster. This embodiment of the invention clusters the parent component data and interfaces, and makes the cluster data in the parent component data cluster correspond one-to-one with the interfaces in the interface cluster. When the parameters developed in the front-end change, the parameters are modified through the relationship between the parent component data cluster and the port cluster, and backend data is obtained from the backend according to the target interface. This avoids the creation of a large number of interfaces, improves the transmission efficiency between modification information and interfaces, simplifies the code structure, and reduces maintenance costs. In this embodiment of the invention, after acquiring backend data, the first cluster data corresponding to the first modified object in the parent component data cluster is updated based on the backend data to obtain the second cluster data. Then, the third cluster data corresponding to the third modified object in the child component data cluster is updated based on the second cluster data. This embodiment effectively integrates parent and child component data through clustered processing, reducing data fragmentation and effectively improving data utilization. Compared with related technologies, this embodiment accelerates the response speed between frontend development and backend data and improves the interaction efficiency between frontend development and backend data by clustering child component data, parent component data, and interfaces.

[0061] This embodiment provides a backend data scheduling method that can be used in computer equipment. Figure 2 This is a flowchart of another backend data scheduling method according to an embodiment of the present invention, such as... Figure 2 As shown, the process includes the following steps:

[0062] Step S201: In response to the triggering of the button component, determine the first modification information corresponding to the button component. The first modification information is used to characterize the modification of the parent component's data cluster and interface cluster. For details, please refer to [link to details]. Figure 1 Step S101 of the illustrated embodiment will not be described again here.

[0063] Step S202: Modify the first modified object in the parent component data cluster corresponding to the first modified information according to the first modified information to obtain the second modified object.

[0064] Specifically, step S202 includes:

[0065] Step S2021: Update the data included in the first modified object to the first modified data to obtain the second modified object.

[0066] Step S203: Modify the target interface in the interface cluster corresponding to the second modification object according to the second modification object, and obtain backend data from the backend according to the target interface. The cluster data in the parent component data cluster corresponds one-to-one with the interface in the interface cluster.

[0067] Specifically, step S203 includes:

[0068] Step S2031: Select the target interface from multiple interfaces in the interface cluster based on the target interface identifier.

[0069] Step S2032: Modify the attribute parameters corresponding to the target interface to the first modified data.

[0070] Step S2033: Construct a request-response function based on the second modified object, and configure the parameters of the request-response function to obtain the target request-response function.

[0071] Step S2034: Call the target request-response function to obtain the backend data according to the location identifier of the backend data.

[0072] The request and response functions can be either request or response functions. Parameters for the request and response functions can be configured, including: baseURL (basic Uniform Resource Locator) settings, timeout settings, headers (request and response header information) settings, withCredentials (attributes used for cross-origin requests) settings, and paramsSerializer (functions used for serializing query parameters) settings.

[0073] In this embodiment of the invention, the backend data scheduling method further includes: setting interceptors for requests and responses, and performing related processing such as adding request headers, modifying request parameters, and judging response status codes on the request and response functions in the request interceptor and response interceptor.

[0074] In front-end development, it is often necessary to add some common header information to each request and response function. For example, a user identity token needs to be added to the request header. By using a request interceptor, this header information can be added to all requests in a unified manner, avoiding the need to repeatedly write the code to add the header information in each request and response function.

[0075] The functions of a response interceptor include data preprocessing and cached data processing. Data preprocessing involves processing the backend data returned by the backend before delivering it to the business logic layer. For example, the backend data might be compressed; the response interceptor can decompress it. Or, if the date format of the backend data doesn't meet the frontend's display requirements, the response interceptor can modify the date format to conform to the frontend's display requirements. Cached data processing determines whether to cache the backend data based on the target request's response function. For example, if the backend's response header contains a Cache-Control field indicating that the backend data is cached, the response interceptor will store the backend data locally.

[0076] In some alternative implementations, the target request-response function is invoked, the backend data is retrieved according to the location identifier of the backend data, the backend data and the default configuration data are merged, a request instance is created, the response interceptor is configured, and the request instance is returned to pass the backend data to the parent component data cluster.

[0077] Step S204: Based on the backend data, update the first cluster data corresponding to the first modified object in the parent component's data cluster to obtain the second cluster data. For details, please refer to [link to relevant documentation]. Figure 1 Step S104 of the illustrated embodiment will not be described again here.

[0078] Step S205: Update the third cluster data corresponding to the third modified object in the sub-component data cluster based on the second cluster data.

[0079] Specifically, step S205 includes:

[0080] Step S2051: Based on the preset response function, perform attribute transformation on the second cluster data to obtain the fourth cluster data; the preset response function is used to convert the reactive attributes of the second cluster data corresponding to the parent component data cluster into non-reactive attributes.

[0081] Step S2052: Update the third cluster data corresponding to the third modified object in the sub-component data cluster according to the fourth cluster data.

[0082] Step S206: Pass the fourth cluster data to the image drawing component and control the image drawing component to draw the image to obtain the target image.

[0083] Step S207: Control the parent component's data cluster to update the page by referencing the target image.

[0084] In some alternative implementations, the page is displayed after the parent component's data cluster references the target image to update the page.

[0085] The backend data scheduling method provided in this embodiment reduces the use of numerous interfaces and improves the efficiency of backend data acquisition when acquiring various types of backend data by clustering the interfaces. This embodiment controls the sub-component data cluster to draw the target image and controls the parent component data cluster to reference the target image to update the page. When there are many sub-component data clusters that need to draw images, the sub-component data clusters draw the target image, and the parent component data cluster only needs to reference the target image to update the page, improving image drawing efficiency and thus increasing page update speed.

[0086] This embodiment provides a backend data scheduling method that can be used in computer equipment. Figure 3 This is a flowchart of another backend data scheduling method according to an embodiment of the present invention, such as... Figure 3 As shown, the process includes:

[0087] The button component is triggered, and the corresponding button component is identified based on its ID (Identification). The cluster data corresponding to the button component is then determined and passed to the corresponding cluster data in the parent component. Specifically, the child component passes its cluster data to the parent component via a function.

[0088] The parent component receives the cluster data corresponding to the button component and modifies the object in the data cluster that corresponds to the interface cluster, that is, it assigns a value to the time variable in the parent component's data cluster.

[0089] When the interface component is called, the parent component's data cluster is assigned to the interface cluster, and the interface component's parameters are assigned, that is, the time parameter is passed to the interface cluster through the interface function. When the interface function receives the obtained time parameter, it calls the target request response function again to obtain the backend data from the backend.

[0090] The parent component receives backend data from the API function, updates its data cluster, and then passes the data from the parent component's data cluster to the child component via a function. The child component parses the parent component's data cluster and assigns values ​​to its own data cluster based on the parsed data. In other words, the parent component passes the corresponding child component data cluster data from its data cluster to the child component. Then, the child component uses the `toRefs` method to parse the data object passed from the parent component's data cluster and assigns the parsed data to the corresponding object in the child component's data cluster.

[0091] The child component passes data to the image rendering component to draw the image, and the parent component references the image to update the page. The updated data from the child component's cluster is then passed to the image rendering component. The parent component references the child component, and based on the object identifier in the parent component's data cluster, the image drawn from the child component's cluster data is displayed.

[0092] In some alternative implementations, such as Figure 4 The diagram illustrates the process of drawing and referencing images in a child component. When the parent component's data cluster is initialized and updated via an interface, the updated data in the parent component's data cluster is passed to the child component via a function. The child component parses the parent component's data cluster, assigns values ​​to the child component's data cluster based on the parsed data, and passes the data to the image drawing component for image drawing. The parent component then applies the image to update the page.

[0093] In some alternative implementations, such as Figure 5 The diagram shows a flowchart of a clustered front-end development method based on the Yunxiao Intelligent Computing Platform. This invention can be used on the Yunxiao Intelligent Computing Platform and includes sub-components, parent components, and interfaces. The sub-components include a sub-component data cluster, a button component, and a drawing image. The parent component includes a parent component data cluster. The interfaces include an interface cluster. Ajax (Asynchronous JavaScript and XML, a technology for creating fast and dynamic web pages) requests backend data.

[0094] The specific implementation process is as follows: A button component is triggered in the child component. The button component method passes the time parameter to the child component's data cluster and modifies the data corresponding to the time parameter in the child component's data cluster. The child component's data cluster then passes the updated data to the parent component via the button component method. The parent component receives the data from the child component and passes it to its own data cluster. The parent component's data cluster calls the corresponding interface method according to the directory and passes the data to the interface cluster. The interface cluster retrieves different backend data according to the interface directory and returns the backend data to the parent component. The parent component saves the backend data in the data directory via the interface method and passes the backend data to the child component via the method of passing the child component's data. The child component parses the backend data and passes the parsed backend data to the child component's data cluster. The child component then passes the backend data to the image drawing component for image drawing. The parent component uses the drawn image to update its own data cluster.

[0095] This embodiment also provides a backend data scheduling device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0096] This embodiment provides a backend data scheduling device, such as... Figure 6 As shown, it includes:

[0097] The first modification information determination module 601 is used to determine the first modification information corresponding to the button component in response to the triggering of the button component. The first modification information is used to characterize the modification of the parent component's data cluster and interface cluster.

[0098] The second modification object determination module 602 is used to modify the first modification object corresponding to the first modification information in the parent component data cluster according to the first modification information, so as to obtain the second modification object.

[0099] The backend data acquisition module 603 is used to modify the target interface in the interface cluster corresponding to the second modification object according to the second modification object, and to acquire backend data from the backend according to the target interface. The cluster data in the parent component data cluster corresponds one-to-one with the interfaces in the interface cluster.

[0100] The second cluster data determination module 604 is used to update the first cluster data corresponding to the first modified object in the parent component data cluster based on the backend data to obtain the second cluster data.

[0101] The third cluster data update module 605 is used to update the third cluster data corresponding to the third modified object in the sub-component data cluster based on the second cluster data.

[0102] In some optional implementations, the second modification object determination module 602 includes:

[0103] The second modification object determination unit is used to update the data included in the first modification object with the first modification data to obtain the second modification object.

[0104] In some alternative implementations, the backend data acquisition module 603 includes:

[0105] The target interface selection unit is used to select a target interface from multiple interfaces in the interface cluster based on the target interface identifier.

[0106] The attribute parameter modification unit is used to modify the attribute parameters corresponding to the target interface to the first modified data.

[0107] The request-response function configuration unit is used to construct a request-response function based on the second modified object, and to configure the parameters of the request-response function to obtain the target request-response function.

[0108] The backend data retrieval unit is used to call the target request response function and retrieve backend data according to the location identifier of the backend data.

[0109] In some optional implementations, the third cluster data update module 605 includes:

[0110] The fourth cluster data determination unit is used to perform attribute transformation on the second cluster data based on a preset response function to obtain the fourth cluster data; the preset response function is used to convert the reactive attributes of the second cluster data corresponding to the parent component data cluster into non-reactive attributes.

[0111] The third cluster data update unit is used to update the third cluster data corresponding to the third modified object in the sub-component data cluster according to the fourth cluster data.

[0112] In some alternative implementations, the backend data scheduling apparatus further includes:

[0113] The image rendering module is used to pass the fourth cluster data to the image rendering component, control the image rendering component to render the image, and obtain the target image.

[0114] The page update module is used to control the parent component's data cluster to reference the target image and update the page.

[0115] Further functional descriptions of the above modules and units are the same as those in the corresponding embodiments described above, and will not be repeated here.

[0116] In this embodiment, the backend data scheduling device is presented in the form of a functional unit. Here, a unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that execute one or more software or fixed programs, and / or other devices that can provide the above functions.

[0117] This invention also provides a computer device having the above-described features. Figure 6 The device shown is a backend data scheduling device.

[0118] Please see Figure 7 , Figure 7 This is a schematic diagram of the structure of a computer device provided in an optional embodiment of the present invention, such as... Figure 7As shown, the computer device includes one or more processors 10, memory 20, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The components communicate with each other via different buses and can be mounted on a common motherboard or otherwise installed as needed. The processors can process instructions executed within the computer device, including instructions stored in or on memory to display graphical information of a GUI on external input / output devices (such as display devices coupled to the interfaces). In some alternative implementations, multiple processors and / or multiple buses can be used with multiple memories and multiple memory modules, if desired. Similarly, multiple computer devices can be connected, each providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multiprocessor system). Figure 7 Take a processor 10 as an example.

[0119] Processor 10 may be a central processing unit, a network processor, or a combination thereof. Processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The programmable logic device may be a complex programmable logic device (CAMP), a field-programmable gate array (FPGA), a general-purpose array logic (GDA), or any combination thereof.

[0120] The memory 20 stores instructions executable by at least one processor 10 to cause the at least one processor 10 to perform the method shown in the above embodiments.

[0121] The memory 20 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the computer device. Furthermore, the memory 20 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some alternative embodiments, the memory 20 may optionally include memory remotely located relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0122] The memory 20 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as flash memory, hard disk or solid-state drive; the memory 20 may also include a combination of the above types of memory.

[0123] The computer device also includes a communication interface 30 for communicating with other devices or communication networks.

[0124] This invention also provides a computer-readable storage medium. The methods described above according to embodiments of the invention can be implemented in hardware or firmware, or implemented as computer code that can be recorded on a storage medium, or implemented as computer code downloaded via a network and originally stored on a remote storage medium or a non-transitory machine-readable storage medium and then stored on a local storage medium. Thus, the methods described herein can be processed by software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. The storage medium can be a magnetic disk, optical disk, read-only memory, random access memory, flash memory, hard disk, or solid-state drive, etc.; further, the storage medium can also include combinations of the above types of memory. It is understood that computers, processors, microprocessor controllers, or programmable hardware include storage components capable of storing or receiving software or computer code, which, when accessed and executed by the computer, processor, or hardware, implements the methods shown in the above embodiments.

[0125] A portion of this invention can be applied as a computer program product, such as computer program instructions, which, when executed by a computer, can invoke or provide the methods and / or technical solutions according to the invention through the operation of the computer. Those skilled in the art will understand that the forms in which computer program instructions exist in a computer-readable medium include, but are not limited to, source files, executable files, installation package files, etc. Correspondingly, the ways in which computer program instructions are executed by a computer include, but are not limited to: the computer directly executing the instructions, or the computer compiling the instructions and then executing the corresponding compiled program, or the computer reading and executing the instructions, or the computer reading and installing the instructions and then executing the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to a computer.

[0126] Although embodiments of the invention have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations all fall within the scope defined by the appended claims.

Claims

1. A method for scheduling backend data, characterized in that, The method includes: In response to a triggering of the button component, first modification information corresponding to the button component is determined, wherein the first modification information is used to characterize the modification of the parent component data cluster and interface cluster; Based on the first modification information, the first modification object corresponding to the first modification information in the parent component data cluster is modified to obtain the second modification object; Modify the target interface in the interface cluster corresponding to the second modification object according to the second modification object, and obtain backend data from the backend according to the target interface. The cluster data in the parent component data cluster corresponds one-to-one with the interface in the interface cluster. Based on the backend data, the first cluster data corresponding to the first modified object in the parent component data cluster is updated to obtain the second cluster data; The third cluster data corresponding to the third modified object in the sub-component data cluster is updated based on the second cluster data.

2. The method according to claim 1, characterized in that, The first modification information includes first modification data and a first modification object in the parent component data cluster; the step of modifying the first modification object corresponding to the first modification information in the parent component data cluster according to the first modification information to obtain a second modification object includes: The data included in the first modified object is updated to the first modified data to obtain the second modified object.

3. The method according to claim 1 or 2, characterized in that, The second modification object includes first modification data and a target interface identifier; the step of modifying the target interface in the interface cluster corresponding to the second modification object according to the second modification object includes: Based on the target interface identifier, select the target interface from multiple interfaces in the interface cluster; Modify the attribute parameters corresponding to the target interface to the first modified data.

4. The method according to claim 1 or 2, characterized in that, The target interface includes a location identifier for the backend data; obtaining the backend data from the backend according to the target interface includes: A request-response function is constructed based on the second modified object, and parameters are configured for the request-response function to obtain the target request-response function; The target request-response function is invoked to retrieve the backend data according to the location identifier of the backend data.

5. The method according to claim 1 or 2, characterized in that, The step of updating the third cluster data corresponding to the third modified object in the sub-component data cluster based on the second cluster data includes: Based on a preset response function, the second cluster data is transformed to obtain the fourth cluster data; the preset response function is used to convert the reactive attributes of the second cluster data corresponding to the parent component data cluster into non-reactive attributes. The third cluster data corresponding to the third modified object in the sub-component data cluster is updated according to the fourth cluster data.

6. The method according to claim 5, characterized in that, After updating the third cluster data corresponding to the third modified object in the sub-component data cluster based on the second cluster data, the method further includes: The fourth cluster data is passed to the image rendering component, which is then controlled to render the image to obtain the target image. The parent component's data cluster is controlled to update the page by referencing the target image.

7. A backend data scheduling device, characterized in that, The device includes: The first modification information determination module is used to determine the first modification information corresponding to the button component in response to the triggering of the button component. The first modification information is used to characterize the modification of the parent component data cluster and interface cluster. The second modification object determination module is used to modify the first modification object corresponding to the first modification information in the parent component data cluster according to the first modification information, so as to obtain the second modification object; The backend data acquisition module is used to modify the target interface in the interface cluster corresponding to the second modification object according to the second modification object, and to acquire backend data from the backend according to the target interface. The cluster data in the parent component data cluster corresponds one-to-one with the interfaces in the interface cluster. The second cluster data determination module is used to update the first cluster data corresponding to the first modified object in the parent component data cluster based on the backend data to obtain the second cluster data. The third cluster data update module is used to update the third cluster data corresponding to the third modified object in the sub-component data cluster based on the second cluster data.

8. A computer device, characterized in that, include: A memory and a processor are communicatively connected, the memory stores computer instructions, and the processor executes the computer instructions to perform the backend data scheduling method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing the computer to execute the backend data scheduling method according to any one of claims 1 to 6.

10. A computer program product, characterized in that, Includes computer instructions for causing a computer to execute the backend data scheduling method according to any one of claims 1 to 6.

Images