A cloud-based JSON warehouse zero-code component dynamic supply system and method

Abstract

The application relates to a cloud JSON warehouse-based zero-code component dynamic supply system and method, and belongs to the technical field of visual programming, which comprises a control module, a storage module, an input module and a communication module which are electrically connected with each other, the storage module is used for storing a plurality of JSON components, the control module is used for counting a JSON component list in the storage module and giving a time stamp to each JSON component, the communication module is used for receiving a component request of a user end and sending the component request to the control module, and the control module instructs the storage module to transmit the JSON component to the user end through the communication module; the input module is used for sending instructions to the control module, the input module is used for loading an updated version of a certain JSON component or a certain brand-new JSON component and sending an updating instruction to the control module, and the control module loads the updated version of the JSON component or the certain brand-new JSON component into the storage module after receiving the updating instruction.

Description

Technical Field

[0001] This invention belongs to the field of visual programming technology, specifically relating to a zero-code component dynamic supply system and method based on a cloud-based JSON repository. Background Technology

[0002] For no-code programming platforms, various components need to be used or loaded. Different components are loaded according to different task requirements to achieve different functions.

[0003] Currently, common component management mainly includes embedded component architecture and static cloud component libraries. A specific solution for static cloud component libraries is, for example, a no-code SaaS-based enterprise application development and data management system and method disclosed in Chinese Patent CN119669562B. This system includes: acquiring user-inputted application development requirements; extracting input and output keywords from these requirements; acquiring subscription and development information for components on the SaaS platform; assigning keywords to components on the SaaS platform; selecting input and output components for the user; recommending execution components to the user; and allowing the user to develop the required application using the recommended components. In this solution, the user purchases and maintains the software, reducing resource consumption and maintenance burden; the user can quickly access and deploy applications without installation or configuration; and the system analyzes user needs and, combined with subscription information on the SaaS platform, recommends the most suitable SaaS application development components.

[0004] However, such solutions typically only enable simple component or software downloads. Components are stored on cloud servers in compressed packages, and component versions are deeply tied to platform versions, resulting in weak adaptability. Components need to be updated and adapted for different platforms, but such solutions often require downtime for maintenance, leading to low update efficiency. Therefore, a zero-code dynamic component provisioning system and method based on a cloud-based JSON repository is needed, which offers better adaptability and higher update efficiency. Summary of the Invention

[0005] To address the aforementioned problems in the existing technology, this invention provides a zero-code component dynamic supply system and method based on a cloud-based JSON repository, which features good adaptability and high update efficiency.

[0006] The objective of this invention can be achieved through the following technical solutions: A zero-code component dynamic supply system based on a cloud-based JSON repository includes a control module, a storage module, an input module, and a communication module that are electrically connected to each other. The storage module is used to store a number of JSON components. The control module is used to count the list of JSON components in the storage module and assign a timestamp to each JSON component. The communication module is used to receive component requests from the user and send the component requests to the control module. The control module instructs the storage module to transmit the JSON components to the user through the communication module. The input module is used to send instructions to the control module. The input module is used to load an updated version of a JSON component or a brand new JSON component and send an update instruction to the control module. After receiving the update instruction, the control module loads the updated version of the JSON component or the brand new JSON component into the storage module.

[0007] As a preferred embodiment of the present invention, the communication module further includes an output interface, which is used to render the JSON component in the storage module and send it to the user terminal.

[0008] As a preferred embodiment of the present invention, any of the JSON components includes JSON Schema configuration information.

[0009] As a preferred technical solution of the present invention, when the output interface renders the JSON component in the storage module and sends it to the user terminal, it simultaneously downloads the timestamps of several JSON components. The output interface compares the timestamp of the previous download with the timestamp of the current download to find the different timestamps, and synchronizes with the JSON components counted in the control module by comparing the timestamps.

[0010] As a preferred technical solution of the present invention, after receiving the update instruction, the control module is used to count the number of updated JSON components and the number of newly loaded JSON components, which are recorded as the number of updated components. The control module determines whether the number of updated components exceeds the threshold, and executes a delay procedure when the determination result is yes. During the execution of the delay procedure, the control module copies the current JSON component list and timestamp for synchronization with the output interface, and deletes the copied JSON component list and timestamp after the update instruction is completed.

[0011] As a preferred embodiment of the present invention, the control module calculates the comprehensive update parameters based on the number and size of the update components and determines whether the comprehensive update parameters exceed the threshold. If the parameters exceed the threshold, the execution time of the suspended program is extended, and if the parameters are below the threshold, the execution time of the suspended program is reduced.

[0012] As a preferred technical solution of the present invention, the control module calculates the comprehensive update parameter Z based on the number of update components N and the average size of the update components D. The control module adjusts the pause program execution time to T, where T=(k1×N / N0+k2×D / D0) / (k1+k2), where k1=1-k2, k2=K, and K is the current bandwidth utilization rate of the control module. A method for dynamically provisioning no-code components based on a cloud-based JSON repository, applicable to the aforementioned system for dynamically provisioning no-code components based on a cloud-based JSON repository, further includes the following steps: Step 1: Load several JSON components into the storage module and write JSON Schema configuration information for any JSON component; Step 2: The control module compiles a list of JSON components in the storage module and assigns a timestamp to each JSON component, thus completing the component deployment; Step 3: The user uses the no-code programming platform to output the JSON components in the rendering storage module, forming a component list and sending it to the user's end; Step 4: Build the target interface required by the user by dragging and dropping components from the component list.

[0013] The beneficial effects of this invention are as follows: (1) By setting up storage modules and control modules separately, the component data storage and the core management platform are decoupled at the physical layer. When upgrading the core management platform, the interaction between the storage module and the outside world is not affected. Unlike traditional platforms, the entire platform does not need to be shut down for upgrades. This improves the hot update function and increases update efficiency. (2) By enabling the control module to load the updated version of the JSON component or a brand new JSON component into the storage module after receiving the update instruction, the individual component can be updated independently without having to shut down the entire platform for upgrades as in traditional platforms. This further improves the hot update function and thus further improves the update efficiency. (3) By enabling any JSON component to include JSON Schema configuration information, a standardized protocol is established for each JSON component, thereby improving multi-platform compatibility; (4) When the control module determines that the number of updated components exceeds the threshold, a delay procedure is executed. During the delay procedure, the control module copies the current JSON component list and timestamp for synchronization with the output interface. The copied JSON component list and timestamp are deleted after the update instruction is completed, so as to avoid the list chaos when the user calls the components at the same time as a large number of updates. (5) By having the control module calculate the comprehensive update parameter Z based on the number of update components N and the average size of the update components D, the control module adjusts the pause program execution time to T, where T=(k1×N / N0+k2×D / D0) / (k1+k2), where k1=1-k2, k2=K, and K is the current bandwidth utilization rate of the control module. Attached Figure Description

[0014] To facilitate understanding by those skilled in the art, the present invention will be further described below with reference to the accompanying drawings.

[0015] Figure 1 This is a schematic diagram illustrating the communication steps at each level of the present invention; Figure 2 This is a schematic diagram of the structure of the present invention. Detailed Implementation

[0016] To further illustrate the technical means and effects of the present invention in achieving its intended purpose, the following detailed description of the specific implementation methods, structures, features, and effects of the present invention, in conjunction with the accompanying drawings and preferred embodiments, is provided.

[0017] Please see Figure 1-2 A zero-code component dynamic supply system based on a cloud-based JSON repository includes a control module, a storage module, an input module, and a communication module that are electrically connected to each other. The storage module is used to store several JSON components. The control module is used to count the list of JSON components in the storage module and assign a timestamp to each JSON component. The communication module is used to receive component requests from the user and send the component requests to the control module. The control module instructs the storage module to transmit JSON components to the user through the communication module. The input module is used to send instructions to the control module. The input module is used to load an updated version of a JSON component or a brand new JSON component and send an update instruction to the control module. After receiving the update instruction, the control module loads the updated version of the JSON component or a brand new JSON component into the storage module. like Figure 1 As shown, in actual use, when the user develops the interface through the main program of the zero-code development platform, the main program obtains the component list from the control module, then filters the required components from the component list, and queries the storage module for valid components. Subsequently, the main program retrieves component details from the control module and downloads the target component from the storage module, completing the component query, filtering, and download.

[0018] By setting up separate storage and control modules, the component data storage and the core management platform are decoupled at the physical layer. Upgrading the core management platform does not affect the interaction between the storage module and the outside world. Unlike traditional platforms, there is no need to shut down the entire platform for upgrades. This improves the hot update function and increases update efficiency. Meanwhile, by enabling the control module to load the updated version of the JSON component or a completely new JSON component into the storage module after receiving the update command, the individual components can be updated independently without having to shut down the entire platform for upgrades as in traditional platforms. This further improves the hot update function and thus further enhances update efficiency.

[0019] The communication module also includes an output interface, which is used to render the JSON component in the storage module and send it to the user terminal.

[0020] Each JSON component contains JSON Schema configuration information; By enabling any JSON component to include JSON Schema configuration information, standardized protocols are established among the JSON components, improving multi-platform compatibility. When the output interface renders the JSON component in the storage module and sends it to the user, it simultaneously downloads the timestamps of several JSON components. The output interface compares the timestamp of the previous download with the timestamp of the current download to find the different timestamps, and synchronizes them with the JSON components counted in the control module by comparing the timestamps.

[0021] After receiving the update command, the control module counts the number of updated JSON components and the number of newly loaded JSON components, which is recorded as the number of updated components. The control module determines whether the number of updated components exceeds the threshold, and if the result is yes, it executes a pause procedure. During the execution of the pause procedure, the control module copies the current list of JSON components and timestamps for synchronization with the output interface. The copied list of JSON components and timestamps are deleted after the update command is completed.

[0022] When the number of updated components exceeds a threshold, the control module executes a pause procedure. During the pause procedure, the control module copies the current JSON component list and timestamps for synchronization with the output interface. The copied JSON component list and timestamps are deleted after the update command is completed, thus avoiding list chaos when users call components simultaneously during a large number of updates. The control module calculates the comprehensive update parameters based on the number and size of the updated components and determines whether the comprehensive update parameters exceed the threshold. If the parameters exceed the threshold, the execution time of the suspended program is extended; if the parameters are below the threshold, the execution time of the suspended program is reduced.

[0023] The control module calculates the comprehensive update parameter Z based on the number of update components N and the average size of the update components D. The control module adjusts the pause program execution time to T, where T=(k1×N / N0+k2×D / D0) / (k1+k2), where k1=1-k2, k2=K, and K is the current bandwidth utilization rate of the control module, 0%≤K≤100%. The unit for the number of updated components is "pieces", and the unit for the average size of the updated components is "kb". When bandwidth utilization is high, the average size D of the update component, which is more sensitive to bandwidth performance, has a greater impact on the excess update time. At this time, it is necessary to give more consideration to the impact of the average size of the update component on the excess update time and increase the weight of the average size D of the update component in the calculation of T. When D is large, the value of T needs to be increased to a greater extent. When K is large, k2 is large, thus completing the increase of the weight of D. When bandwidth utilization is low, the transfer of a large number of small files can cause the transfer speed to be much lower than the theoretical value. In this case, the impact on the excess update time depends more on the number of update components N, where k1 = 1 - k2. By having the control module calculate the comprehensive update parameter Z based on the number of updated components N and the average size of the updated components D, the control module adjusts the pause program execution time to T, where T=(k1×N / N0+k2×D / D0) / (k1+k2), where k1=1-k2, k2=K, and K is the current bandwidth utilization rate of the control module.

[0024] This invention also provides a method for dynamically provisioning no-code components based on a cloud-based JSON repository, applicable to the aforementioned system for dynamically provisioning no-code components based on a cloud-based JSON repository, and further includes the following steps: Step 1: Load several JSON components into the storage module and write JSON Schema configuration information for any JSON component; Step 2: The control module compiles a list of JSON components in the storage module and assigns a timestamp to each JSON component, thus completing the component deployment; Step 3: The user uses the no-code programming platform to output the JSON components in the rendering storage module, forming a component list and sending it to the user's end; Step 4: Build the target interface required by the user by dragging and dropping components from the component list; Specifically, step one also includes the following sub-steps: Step 1a: Write the JSON component and its JSON Schema configuration information; Step 1b: Put the JSON component icon key into the JSON Schema; Step 1c: Write the dependency declarations applied by the component; Step two also includes the following sub-steps: Step 2a: Write scripts for adding, publishing, and deleting components; Step 2b: Publish the accompanying scripts for the component to facilitate developer use; Step three also includes the following sub-steps: Step 3a: When the zero-code editor is opened, the component list will be obtained through the contract. The component list and component information are in JSON script format, and the components will be registered as specific components required by the canvas. Step 3b: Compare the timestamps of the user's local terminal and the server terminal. Identify components with timestamp differences between the user terminal and the control module, and perform add, delete, or modify operations on the components with timestamp differences.

[0025] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention in any way. Although the present invention has been disclosed above with reference to preferred embodiments, it is not intended to limit the present invention. Any person skilled in the art can make some modifications or alterations to the above-disclosed technical content to create equivalent embodiments without departing from the scope of the present invention. Any simple modifications, equivalent changes and alterations made to the above embodiments based on the technical essence of the present invention without departing from the scope of the present invention shall still fall within the scope of the present invention.

Claims

1. A zero-code component dynamic provisioning system based on a cloud-based JSON repository, characterized in that: The system includes a control module, a storage module, an input module, and a communication module that are electrically connected to each other. The storage module is used to store several JSON components. The control module is used to count the list of JSON components in the storage module and assign a timestamp to each JSON component. The communication module is used to receive component requests from the user and send the component requests to the control module. The control module instructs the storage module to transmit the JSON components to the user through the communication module. The input module is used to send instructions to the control module. The input module is used to load an updated version of a JSON component or a brand new JSON component and send an update instruction to the control module. After receiving the update instruction, the control module loads the updated version of the JSON component or a brand new JSON component into the storage module. After receiving the update command, the control module is used to count the number of updated JSON components and the number of newly loaded JSON components, which is recorded as the number of updated components. The control module determines whether the number of updated components exceeds the threshold, and executes a delay procedure when the determination result is yes. During the execution of the delay procedure, the control module copies the current list of JSON components and timestamps for synchronization with the output interface until the update command is completed and then deletes the copied list of JSON components and timestamps. The control module calculates the comprehensive update parameters based on the number and size of the update components and determines whether the comprehensive update parameters exceed the threshold. If the parameters exceed the threshold, the execution time of the suspended program is extended; if the parameters are below the threshold, the execution time of the suspended program is reduced.

2. The zero-code component dynamic supply system based on a cloud-based JSON repository according to claim 1, characterized in that: The communication module also includes an output interface, which is used to render the JSON component in the storage module and send it to the user terminal.

3. The zero-code component dynamic supply system based on a cloud-based JSON repository according to claim 1, characterized in that: Each of the JSON components contains JSON Schema configuration information.

4. A zero-code component dynamic supply system based on a cloud-based JSON repository as described in claim 2, characterized in that: When the output interface renders the JSON component in the storage module and sends it to the user terminal, it simultaneously downloads the timestamps of several JSON components. The output interface compares the timestamp of the previous download with the timestamp of the current download to find the different timestamps, and synchronizes them with the JSON components counted in the control module by comparing the timestamps.

5. A method for dynamically provisioning zero-code components based on a cloud-based JSON repository, characterized in that: The zero-code component dynamic provisioning system based on a cloud-based JSON repository, as described in claim 4, further includes the following steps: Step 1: Load several JSON components into the storage module and write JSON Schema configuration information for any JSON component; Step 2: The control module compiles a list of JSON components in the storage module and assigns a timestamp to each JSON component, thus completing the component deployment; Step 3: The user uses the no-code programming platform to output the JSON components in the rendering storage module, forming a component list and sending it to the user's end; Step 4: Build the target interface required by the user by dragging and dropping components from the component list.

Images