Cross-component data sharing method and device, equipment and storage medium
By building a centralized variable pool and Vuex state machine in the low-code development framework, the limitations of data sharing across components and event mechanism performance problems in the financial and insurance industry are solved, data management and network requests are optimized, and system performance and response are improved. efficiency.
Patent Information
- Application Number
- CN202411202462.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-29
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2044-08-29
AI Technical Summary
The low-code development framework has limitations in cross-component data sharing, performance problems caused by event mechanisms, and network overhead caused by duplicate requests in the financial and insurance industries, resulting in increased system complexity, performance degradation and extended response time.
Build a centralized variable pool and integrate a Vuex state machine. Use the business attribute collection plug-in to push data to the centralized variable pool, store and group it in a modular manner, define access permissions and cache policies, and optimize data requests and responses.
It realizes centralized management and sharing of cross-component business attribute data, reduces system complexity, avoids network request redundancy, and improves overall performance and response efficiency.
Smart Images

Figure CN119066681A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer technology, and in particular to a cross-component data sharing method, device, equipment and storage medium. Background Art
[0002] In the modern financial and insurance industries, as digital transformation deepens, more and more companies are beginning to adopt low-code development platforms (such as Bootstrap) to build their internal and external applications. These low-code platforms simplify the application development process and speed up the deployment of business systems by providing visual configuration tools and predefined component libraries. However, as the complexity of applications increases, the limitations of low-code frameworks are gradually emerging, especially in terms of data management and data sharing between components.
[0003] In a typical low-code development framework, metadata is usually managed at the component level. Although this approach can meet basic development needs, it has the following three main problems when dealing with complex business logic, especially in the financial and insurance industries:
[0004] Limitations of cross-component data sharing: In traditional low-code frameworks, each component usually manages its business attribute data independently, which means that the business attributes in component A cannot be directly referenced and used by component B. This limitation results in the inability to effectively share business attributes between different components, which in turn increases system complexity. In financial and insurance applications, it is often necessary to share key information between multiple components, such as customer data, policy information, or transaction records. Therefore, the lack of cross-component data sharing capabilities may limit the flexibility and scalability of the system.
[0005] Performance issues caused by the event mechanism: In order to solve the problem of data sharing between sibling components, low-code frameworks usually rely on the event mechanism, that is, to achieve data transmission through event triggering and monitoring. However, this mechanism is prone to cause a large amount of event overhead in large-scale applications, thereby reducing the efficiency of the browser JavaScript parser. For applications in the financial and insurance industries, processing large amounts of real-time data and complex business logic is a common requirement. If the event mechanism is used improperly, it may cause performance problems and even memory leaks, further affecting the stability and response speed of the system.
[0006] Network overhead caused by repeated requests: Since business attributes cannot be repeatedly referenced across components, the system may need to request the same business attribute data from the server multiple times in multiple components. This design leads to redundancy of network requests, which not only increases the network load, but also goes against the performance optimization principle of reducing the number of HTTP requests. In the financial and insurance industries, frequent network requests may lead to increased system response time, reduced user experience, and may cause more serious performance bottlenecks in high concurrency situations.
[0007] In summary, the current low-code development framework faces challenges such as the limitation of cross-component data sharing, performance issues caused by event mechanisms, and network overhead caused by repeated requests when dealing with complex financial and insurance business applications. Therefore, in response to these problems, there is an urgent need for a technical solution that can effectively realize the centralized management and sharing of business attribute data to improve the overall performance and stability of the system. Summary of the invention
[0008] The main purpose of the present invention is to provide a cross-component data sharing method, device, equipment and storage medium, aiming to solve the technical problem that business attribute data cannot be effectively shared and managed across components, resulting in increased system complexity, reduced performance and redundant network requests.
[0009] To achieve the above object, the present invention provides a cross-component data sharing method, comprising:
[0010] Build a centralized variable pool for centralized management and storage of business attribute data, and integrate the Vuex state machine in the centralized variable pool;
[0011] A business attribute collection plug-in is configured in the business component, and the business attribute data in the business component is pushed to the centralized variable pool through the business attribute collection plug-in;
[0012] The business attribute data pushed to the centralized variable pool is stored in the Vuex state machine in a modular manner. The modular storage includes classification and grouping of business attribute data, dividing the data into multiple modules according to different business logics, and defining access rights and cache strategies for each module;
[0013] The centralized variable pool is accessed through business components to achieve sharing of the business attribute data.
[0014] In one embodiment, pushing the business attribute data in the business component to the centralized variable pool through the business attribute collection plug-in includes:
[0015] Setting an anti-shake time threshold, when the service attribute collection plug-in receives a data collection instruction, starts an anti-shake mechanism;
[0016] If no new data collection instruction is received within the anti-shake time threshold, the business attribute data is pushed from the business component to the centralized variable pool through the business attribute collection plug-in;
[0017] If a new data collection instruction is received within the anti-shake time threshold, all received data collection instructions are aggregated and merged into one data collection task through the anti-shake mechanism;
[0018] After the anti-shake time threshold ends, the data collection task is executed through the business attribute collection plug-in, and the corresponding business attribute data is collected from the business component and pushed to the centralized variable pool.
[0019] In one embodiment, accessing the centralized variable pool through a business component to achieve sharing of the business attribute data includes:
[0020] Assigning priorities to business attribute data requests based on the importance of the business attribute data;
[0021] In the process of the business component initiating a business attribute data request to the centralized variable pool, the business attribute data request is divided into a plurality of stages according to the assigned priorities, and the business attribute data requests at different stages are processed in order of priority;
[0022] Before the business attribute data request of each stage is sent to the centralized variable pool, a corresponding data request task is generated, and the data request task manages and executes the business attribute data request according to the priority;
[0023] After the data request task of each stage is generated and sent to the centralized variable pool, the centralized variable pool receives and processes the business attribute data request of each stage, and returns the corresponding business attribute data to the business component.
[0024] In one embodiment, the business attribute data pushed to the centralized variable pool is stored in the Vuex state machine in a modular manner, including:
[0025] According to a preset time interval, the business attribute data collected in the centralized variable pool is divided into multiple bands, and business data access requests are sent to the server in sequence;
[0026] After receiving the service attribute data response returned by the server, the service attribute data is parsed and the service attribute data is grouped according to a predefined storage rule;
[0027] The grouped data is packaged into independent modules and stored in the Vuex state machine.
[0028] In one embodiment, parsing the business attribute data and grouping the business attribute data according to a predefined storage rule includes:
[0029] Parsing the business attribute data, identifying and extracting business fields in the business attribute data;
[0030] According to business requirements and predefined storage rules, a corresponding rule number is assigned to each business field, and the rule number is used to guide the grouping and storage of the business field;
[0031] The corresponding storage rules are applied according to the rule number of each business field to group the business fields in a modular manner.
[0032] In one embodiment, after the business fields are grouped in a modular manner, the following is further included:
[0033] Select rendering target and output format based on business needs or user instructions;
[0034] Extract the grouped and stored business field data from the Vuex state machine, and determine the corresponding rendering template according to the rendering target;
[0035] Binding the extracted business field data to the rendering template, filling the business field data into a specified position of the rendering template, and generating a preliminary rendering result;
[0036] The preliminary rendering result is formatted using the output format to obtain a target rendering result.
[0037] In one embodiment, the business attribute data collected in the centralized variable pool is divided into a plurality of bands according to a preset time interval, and business data access requests are sent to the server in sequence, including:
[0038] According to a preset time interval, the business attribute data collected in the centralized variable pool is divided into a plurality of bands;
[0039] Before sending each business data access request, dynamically adjust the sending frequency of the next business data access request according to the current load and network conditions;
[0040] Monitor I / O performance and network status in real time, and dynamically adjust the amount of business attribute data sent in each batch;
[0041] Categorize and prioritize business data access requests based on their urgency and importance;
[0042] The service data access request for each band is sent to the server in sequence according to the sending frequency of the service data access request, the quantity and priority of the service attribute data sent in each batch.
[0043] Furthermore, to achieve the above object, the present invention also provides a cross-component data sharing device, comprising:
[0044] Centralized variable pool module, building a centralized variable pool for centralized management and storage of business attribute data, and integrating the Vuex state machine in the centralized variable pool;
[0045] A business attribute collection plug-in module, which configures a business attribute collection plug-in in a business component, and pushes the business attribute data in the business component to the centralized variable pool through the business attribute collection plug-in;
[0046] The data storage and management module stores the business attribute data pushed to the centralized variable pool in the Vuex state machine in a modular manner. The modular storage includes classification and grouping of business attribute data, dividing the data into multiple modules according to different business logics, and defining the access rights and cache strategies of each module.
[0047] The data access and sharing module accesses the centralized variable pool through business components to achieve sharing of the business attribute data.
[0048] Furthermore, to achieve the above-mentioned purpose, the present invention also provides a cross-component data sharing device, which includes a memory, a processor, and a cross-component data sharing program stored in the memory and executable on the processor, and the cross-component data sharing program, when executed by the processor, implements the steps of the cross-component data sharing method as described above.
[0049] Furthermore, to achieve the above objectives, the present invention also provides a computer storage medium, on which a cross-component data sharing program is stored, and when the cross-component data sharing program is executed by a processor, the steps of the cross-component data sharing method as described above are implemented.
[0050] Beneficial effects: The present invention relates to a cross-component data sharing method, which aims to solve the problem that business attribute data cannot be effectively shared and managed among different components in the existing low-code development framework. The present invention realizes centralized management and modular storage of business attribute data by constructing a centralized variable pool and integrating the Vuex state machine therein. It includes configuring a business attribute collection plug-in in the business component to push the business attribute data to the centralized variable pool; storing the data in a modular manner, including classification and grouping of the data, and dividing it into multiple modules according to business logic, and defining the access rights and caching strategies of each module. Finally, the centralized variable pool is accessed through the business component to realize cross-component business attribute data sharing. The present invention effectively reduces the complexity of the system, avoids the redundancy of network requests, and improves the performance and response efficiency of the overall system. BRIEF DESCRIPTION OF THE DRAWINGS
[0051] The present invention will be further described below with reference to the accompanying drawings and embodiments, in which:
[0052] Figure 1 A schematic diagram of a flow chart of an embodiment of a cross-component data sharing method of the present invention;
[0053] Figure 2 A schematic diagram of functional modules of a preferred embodiment of the cross-component data sharing device of the present invention;
[0054] Figure 3 It is a structural diagram of the device hardware operating environment involved in the cross-component data sharing device embodiment of the present invention. DETAILED DESCRIPTION
[0055] It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not used to limit the present invention.
[0056] It should be noted that in the modern financial and insurance industries, with the deepening of digital transformation, more and more companies are beginning to adopt low-code development platforms (such as Bootstrap) to build their internal and external applications. These low-code platforms simplify the application development process and speed up the deployment of business systems by providing visual configuration tools and predefined component libraries. However, as the complexity of applications increases, the limitations of low-code frameworks are gradually emerging, especially in terms of data management and data sharing between components.
[0057] In a typical low-code development framework, metadata is usually managed at the component level. Although this approach can meet basic development needs, it has the following three main problems when dealing with complex business logic, especially in the financial and insurance industries:
[0058] Limitations of cross-component data sharing: In traditional low-code frameworks, each component usually manages its business attribute data independently, which means that the business attributes in component A cannot be directly referenced and used by component B. This limitation results in the inability to effectively share business attributes between different components, which in turn increases system complexity. In financial and insurance applications, it is often necessary to share key information between multiple components, such as customer data, policy information, or transaction records. Therefore, the lack of cross-component data sharing capabilities may limit the flexibility and scalability of the system.
[0059] Performance issues caused by the event mechanism: In order to solve the problem of data sharing between sibling components, low-code frameworks usually rely on the event mechanism, that is, to achieve data transmission through event triggering and monitoring. However, this mechanism is prone to cause a large amount of event overhead in large-scale applications, thereby reducing the efficiency of the browser JavaScript parser. For applications in the financial and insurance industries, processing large amounts of real-time data and complex business logic is a common requirement. If the event mechanism is used improperly, it may cause performance problems and even memory leaks, further affecting the stability and response speed of the system.
[0060] Network overhead caused by repeated requests: Since business attributes cannot be repeatedly referenced across components, the system may need to request the same business attribute data from the server multiple times in multiple components. This design leads to redundancy of network requests, which not only increases the network load, but also goes against the performance optimization principle of reducing the number of HTTP requests. In the financial and insurance industries, frequent network requests may lead to increased system response time, reduced user experience, and may cause more serious performance bottlenecks in high concurrency situations.
[0061] In summary, the current low-code development framework faces challenges such as the limitation of cross-component data sharing, performance issues caused by event mechanisms, and network overhead caused by repeated requests when dealing with complex financial and insurance business applications. Therefore, in response to these problems, there is an urgent need for a technical solution that can effectively realize the centralized management and sharing of business attribute data to improve the overall performance and stability of the system.
[0062] See also Figure 1 , Figure 1 This is a flow chart of an embodiment of a cross-component data sharing method provided by the present invention. It should be noted that although a logical sequence is shown in the flow chart, in some cases, the steps shown or described may be performed in a different order than that shown here.
[0063] like Figure 1 As shown, the cross-component data sharing method proposed by the present invention includes the following steps:
[0064] S10, building a centralized variable pool for centralized management and storage of business attribute data, and integrating the Vuex state machine in the centralized variable pool;
[0065] In this embodiment, the centralized variable pool is a core module for data storage and management, which is designed to centrally manage business attribute data from multiple business components. Through centralized management, the centralized variable pool can eliminate the problem of data islands between components and ensure that data can be efficiently shared and accessed between components. For example, in a financial management system, each business component may involve data such as customer information, transaction records, and credit scores. By centrally storing these business attribute data in a centralized variable pool, the system can ensure that different modules (such as customer service, risk control, credit approval, etc.) can share and access the same data source, reduce duplicate requests, and optimize system performance.
[0066] The Vuex state machine is a centralized storage for managing the shared state of all components in an application. Integrating the Vuex state machine in a centralized variable pool ensures that data changes can be updated synchronously in all components that rely on this data to maintain data consistency. The Vuex state machine also provides functions such as time travel debugging, state snapshot saving and rollback, which improves the flexibility and reliability of data management. For example, in a financial scenario, suppose a credit approval system needs to update a customer's credit score data at any time. If the data is managed in a centralized variable pool and synchronized to relevant components through the Vuex state machine, when the credit score changes, the approval system, customer service system and other related modules can immediately obtain the latest data to ensure the consistency and accuracy of decision-making.
[0067] In one specific implementation, in a risk assessment system of a financial institution, a centralized variable pool is designed to centrally manage customers' credit scores and transaction history data. The Vuex state machine is not only used for data synchronization, but also extended to have the function of historical version management, enabling the system to trace back data versions at different time points and support more refined risk assessment. At the same time, the business attribute collection plug-in is extended to include data validation and filtering functions to ensure the high quality of data pushed to the centralized variable pool. In terms of data storage, modular storage adds data priority and storage cycle management functions, so that key data can be prioritized and kept up to date. Finally, when business components access the centralized variable pool, role-based access control is also combined to ensure data security.
[0068] In another specific implementation, in the insurance company's claims system, a centralized variable pool is used to centrally store customer policy information and claims application data. The Vuex state machine is extended to support real-time data stream processing, which can automatically update the policy risk score when data flows in. The business attribute collection plug-in increases the processing capabilities of heterogeneous data sources, can integrate structured and unstructured data, and unify the conversion format for storage. Modular storage adds automated lifecycle management capabilities, so that inactive data can be automatically migrated to cold storage areas to optimize storage resources. During the data sharing process, the system supports automatic triggering of interactions with external systems based on predefined rules, such as automatically sending data requests to reinsurance companies.
[0069] In other specific implementations, in the bank's cross-departmental collaboration system, the centralized variable pool is expanded into a data exchange platform to support cross-departmental transactional data operations and ensure data consistency among all relevant departments. The business attribute collection plug-in adds a real-time event response function, which can collect and push relevant data instantly when an event occurs. Modular storage automatically adjusts data grouping and storage strategies through machine learning to improve data access efficiency. When accessing the centralized variable pool, business components can also automatically generate data analysis reports to support high-level business decisions.
[0070] Through the above steps, by building a centralized variable pool and integrating the Vuex state machine, centralized management and real-time synchronization of business attribute data across components are achieved, which significantly improves the consistency, security and performance of the system.
[0071] S20, configuring a business attribute collection plug-in in the business component, and pushing the business attribute data in the business component to the centralized variable pool through the business attribute collection plug-in;
[0072] In this embodiment, the business attribute collection plug-in is a specially designed module that can be integrated into different business components. Its main function is to automatically monitor and collect business attribute data within the component, such as customer information, transaction data, etc. The plug-in can be configured to adapt to different business needs to ensure that it can work effectively in various scenarios. For example, in a financial service application, the collection plug-in can be configured to monitor the loan application form filled out by the user. When the user completes the form, the plug-in will automatically collect the customer information, loan amount, term and other data in the form, and prepare to push it to the centralized variable pool.
[0073] Once the business attribute collection plug-in collects the data in the business component, it will pre-process the data (such as data format conversion, verification, etc.) and then push it to the centralized variable pool. The push process can be synchronous or asynchronous, depending on the design requirements of the system. Through this centralized push method, it ensures that the data of all components can be uniformly stored and shared among other components in the system.
[0074] In one specific implementation, in a loan approval system, the business attribute collection plug-in is not only responsible for pushing the loan application data to the centralized variable pool, but is also extended to support data preprocessing and automated scoring functions. Before pushing the data, the plug-in will perform a preliminary score on the applicant's credit information, income data, and loan amount according to predefined rules. The scoring result is pushed to the centralized variable pool along with other application information as part of the business attribute data. This extension enables the system to perform preliminary analysis before the data enters centralized storage, speeding up the subsequent loan approval process. In addition, the plug-in also adds a data compression function. When the data volume is large, the plug-in will compress the data to reduce the burden of network transmission and ensure that the data can be pushed to the centralized variable pool quickly and securely.
[0075] In another specific implementation, in the insurance claims processing system, the functionality of the business attribute collection plug-in is extended to support asynchronous data collection and batch push. In this scenario, the claim application submitted by the customer may contain multiple files and complex data entries. The plug-in first collects this data asynchronously, processes each data submitted by the customer separately, and gradually completes the verification and cleanup of the data in the background. After completion, the plug-in pushes all data entries in batches to the centralized variable pool and automatically generates a summary record for use by the claims review team. This extension reduces the system's waiting time during data collection, improves the user experience, and ensures the integrity and consistency of the data when it is pushed.
[0076] By configuring the business attribute collection plug-in, the data in the business components can be automatically collected and centrally pushed, which effectively improves the real-time and accuracy of the data, ensures the data consistency and system response speed across components, and improves the flexibility and scalability of the overall system.
[0077] S30, storing the business attribute data pushed to the centralized variable pool in the Vuex state machine in a modular manner, wherein the modular storage includes classification and grouping of business attribute data, dividing the data into multiple modules according to different business logics, and defining access rights and cache strategies for each module;
[0078] In this embodiment, modular storage refers to classifying and grouping business attribute data according to certain logical standards to make the storage of data in the Vuex state machine more structured and efficient. Through modularization, the system can package related data into independent modules for subsequent management and access.
[0079] Classification and grouping are the basic steps of modular storage. By classifying business attribute data, the system can group data into independent modules according to different business logics. For example, classification and grouping can be performed according to dimensions such as data type, business process, and user role.
[0080] On the basis of modular storage, the system needs to define access rights and caching strategies for each data module. Access rights determine which users or system components can access specific data modules, while caching strategies determine how this data is cached in the system to improve access efficiency and reduce server load. For example, in a banking system, senior managers can access data in all modules, while ordinary employees may only have access to the modules they need for their work. At the same time, frequently used data modules can be set to short-term cache to reduce the number of database queries, while infrequently used data modules can be set to long-term cache or no cache to reduce system burden.
[0081] In one specific implementation, in the risk control system of a financial institution, after the business attribute data is pushed to the centralized variable pool, it is first classified according to different dimensions of the business. For example, the system divides all credit risk-related data into one module and market risk-related data into another module. Each module is stored independently in the Vuex state machine, and different access rights are defined according to the user role. For example, risk assessors can access data from all risk modules, while general employees can only access data from specific modules. In order to improve the response speed of the system, frequently accessed risk modules will be set to short-term cache, while historical risk data will not be cached and will be directly obtained from the database.
[0082] Through modular storage and refined classification processing, efficient management of business attribute data in the Vuex state machine is achieved, which ensures the accessibility and security of system data, improves the system's response speed and resource utilization efficiency, and makes data management more flexible and reliable.
[0083] S40, accessing the centralized variable pool through business components to achieve sharing of the business attribute data.
[0084] In this embodiment, business components can access data in the centralized variable pool through interfaces or method calls. This means that each business component does not need to store and manage all business data separately, but can directly obtain the required data from the centralized storage pool. This process usually involves sending data requests, receiving responses, and using the data within the component.
[0085] By allowing business components to access the centralized variable pool, the system can achieve cross-component data sharing. Each business component can access shared data resources, avoiding data redundancy and inconsistency issues. Data sharing can be synchronous or asynchronous, depending on the system design and requirements.
[0086] In one specific implementation, in the bank's loan approval system, the business component realizes the sharing of loan application data and customer credit scores by accessing the centralized variable pool. The system introduces a dynamic data caching mechanism. Specifically, when the loan approval component needs to obtain the customer's credit score, the system first checks whether the data is in the local cache. If there is valid data in the cache, it is used directly, otherwise the latest data is obtained from the centralized variable pool and the cache is updated. This extension reduces the number of direct accesses to the centralized variable pool and improves the system response speed. At the same time, the system sets different cache validity periods for different data modules. For example, the cache validity period of customer credit scores is shorter, while the cache validity period of historical loan records is longer. This extension ensures the real-time nature of the data and the efficient operation of the system.
[0087] In other specific embodiments, in the financial trading platform, the business components share transaction data and market data by accessing the centralized variable pool, but the system further expands the asynchronous data loading mechanism. In order to cope with high-concurrency transaction requests, the system is designed with asynchronous data loading and processing functions. After the business component initiates a data request, the system immediately returns a data request task ID, and the component can asynchronously obtain the data result based on the ID. This extension allows the business component to continue processing other tasks while waiting for the data to be returned, improving the throughput and response speed of the system. In addition, the system has also expanded the data priority processing function. Different types of transaction data are assigned different priorities according to their urgency. High-priority data requests will be processed first and the results will be returned to ensure that key transactions can be executed in a timely manner.
[0088] By accessing the centralized variable pool through business components, data sharing across components is achieved, data redundancy and inconsistency are reduced, system coordination and response speed are improved, and each business component is ensured to have access to the latest shared data, thereby improving the overall efficiency of the system and business processing capabilities.
[0089] The present invention relates to a cross-component data sharing method, which aims to solve the problem that business attribute data in the existing low-code development framework cannot be effectively shared and managed among different components. The present invention realizes centralized management and modular storage of business attribute data by constructing a centralized variable pool and integrating the Vuex state machine therein. It includes configuring a business attribute collection plug-in in the business component to push the business attribute data to the centralized variable pool; storing the data in a modular manner, including classification and grouping of the data, and dividing it into multiple modules according to business logic, and defining the access rights and caching strategies of each module. Finally, the centralized variable pool is accessed through the business component to realize cross-component business attribute data sharing. The present invention effectively reduces the complexity of the system, avoids the redundancy of network requests, and improves the performance and response efficiency of the overall system.
[0090] In one embodiment, in the above S20, pushing the business attribute data in the business component to the centralized variable pool through the business attribute collection plug-in includes:
[0091] S201, setting an anti-shake time threshold, when the service attribute collection plug-in receives a data collection instruction, starting an anti-shake mechanism;
[0092] S202: If no new data collection instruction is received within the anti-shake time threshold, push the business attribute data from the business component to the centralized variable pool through the business attribute collection plug-in;
[0093] S203, if a new data collection instruction is received within the anti-shake time threshold, aggregating all received data collection instructions through the anti-shake mechanism and merging them into one data collection task;
[0094] S204, after the anti-shake time threshold ends, the data collection task is executed by the business attribute collection plug-in, corresponding business attribute data is collected from the business component and pushed to the centralized variable pool.
[0095] In this embodiment, the anti-shake time threshold is used to determine whether the data collection instruction needs to be executed immediately within a certain period of time. The anti-shake mechanism avoids triggering data push every time in the frequent data collection instruction intervals through the set time threshold. This mechanism is activated based on the first received data collection instruction.
[0096] When new data collection instructions are received within the anti-shake time threshold, the anti-shake mechanism aggregates these instructions into a data collection task. This means that the system only performs a data push operation once within a certain period of time, including all collected data. This process optimizes the system's resource usage and reduces the overhead of repeated data transmission.
[0097] After the anti-shake time threshold ends, the system performs the aggregated data collection task through the business attribute collection plug-in. At this time, the system collects all corresponding business attribute data from the business components and pushes it to the centralized variable pool. This mechanism ensures the timeliness and accuracy of data push, while reducing the impact of frequent push operations on the system.
[0098] In one specific implementation, in a financial transaction system, the anti-shake mechanism is extended to a dynamic adjustment mechanism based on the transaction type. The system dynamically sets the anti-shake time threshold according to the urgency and importance of the user's transaction. For example, for high-frequency small transactions, the system will set a shorter anti-shake time threshold to ensure that the transaction data can be quickly pushed to the centralized variable pool for subsequent risk control components to analyze immediately. For large or complex transactions, the system will set a longer anti-shake time threshold to aggregate more transaction data for batch processing. This extension allows the system to flexibly adjust data collection and push strategies according to different types of transactions, optimizing system performance and security.
[0099] In another specific implementation, in the insurance company's claims processing system, the anti-shake mechanism is extended to an intelligent anti-shake mechanism based on user behavior analysis. Based on historical data and user behavior patterns, the system predicts whether the user is likely to submit multiple claims applications in a short period of time. If the system detects that the user is likely to submit multiple claims requests in a short period of time, the anti-shake time threshold will be automatically extended to aggregate more instructions for combined processing. On the contrary, if the user behavior appears to be a one-time operation, the anti-shake time threshold will be shortened and data push will be executed immediately. This user behavior-based extension improves the system's adaptability to user operations and ensures the best balance between user experience and system efficiency.
[0100] By introducing an anti-shake mechanism, this embodiment can effectively reduce unnecessary frequent push operations in the process of collecting business attribute data. It optimizes data transmission by aggregating multiple instructions, improves the system's response speed and resource utilization efficiency, and ensures the accuracy and timeliness of data push, thereby improving the stability of the overall system and user experience.
[0101] In one embodiment, the above S40 includes:
[0102] S401, assigning a priority to a business attribute data request according to the importance of the business attribute data;
[0103] S402, in the process of the business component initiating a business attribute data request to the centralized variable pool, the business attribute data request is divided into a plurality of stages according to the assigned priorities, and the business attribute data requests of different stages are processed in order of priority;
[0104] S403, before the business attribute data request of each stage is sent to the centralized variable pool, a corresponding data request task is generated, and the data request task manages and executes the business attribute data request according to the priority;
[0105] S404, after the data request task of each stage is generated and sent to the centralized variable pool, the centralized variable pool receives and processes the business attribute data request of each stage, and returns the corresponding business attribute data to the business component.
[0106] In this embodiment, the system assigns different priorities to each data request based on the importance of the business attribute data. This process is usually performed before the business component initiates a data request to ensure that data with higher importance can be processed and responded to first. For example, in a banking system, a customer's account balance query request may be assigned a high priority, while a non-urgent historical transaction record query request may be assigned a low priority. In this way, the system can process high-priority requests first to ensure the response speed of key businesses.
[0107] The priority allocation rules can be: highest priority: used for urgent and critical business requests, such as large-value fund transfers and emergency system alarms, which are processed immediately and take precedence over all other requests; high priority: used for important but non-urgent business requests, such as core data processing and important customer inquiries, which are processed as soon as possible and take precedence over medium and low priorities; medium priority: used for routine business requests, such as ordinary account inquiries and daily data processing, which are processed after high-priority tasks; low priority: used for low-impact business requests, such as historical data inquiries and log backups, which are processed when system resources are idle; lowest priority: used for non-critical background tasks, such as data archiving and system maintenance, which are executed after all other requests are processed.
[0108] When a business component initiates a data request, the system divides the data request into multiple stages according to the assigned priority. The system processes data requests at different stages in order of priority to ensure that high-priority requests are responded to first.
[0109] Before sending data requests at each stage, the system generates a corresponding data request task, which is responsible for managing and executing data requests according to priority and ensuring that data requests are processed in the expected priority order.
[0110] After the data request task is generated and sent at each stage, the centralized variable pool is responsible for receiving and processing these requests. The system will process the data in sequence according to the priority of the request and return the corresponding business attribute data to the business component to meet business needs.
[0111] In one specific implementation, in a bank's multi-account management system, the system assigns different priorities to data requests based on account type and transaction type. For example, requests involving large-amount fund transfers are assigned the highest priority, while small-amount consumption record inquiries are assigned a lower priority. When processing these requests, the system first divides the requests into multiple stages based on priority, and high-priority requests are processed and responded to immediately. The extended technical feature is that when high-priority requests are processed, the system monitors changes in account status in real time and dynamically adjusts the processing order of low-priority requests. For example, if an account anomaly is found during the processing of a high-priority request, the system will prioritize the termination of low-priority requests and re-evaluate their processing priority. In this way, the system ensures the security and accuracy of critical operations.
[0112] In another specific implementation, in the risk assessment system of an insurance company, the system assigns priorities to data requests based on the risk level of the customer. Data requests from high-risk customers (such as credit scores, historical default records) are assigned high priority, while data requests from low-risk customers are assigned low priority. The technical feature of the extension is that the system introduces a parallel processing mechanism in the data request stage. When high-priority data requests are processed in stages, the system will process the associated medium and low priority requests in parallel to reduce the overall response time. For example, when processing a credit score query for a high-risk customer, the system will also process requests for its historical default records in parallel. This extension enables the system to improve the overall data processing efficiency while ensuring rapid response to high-priority requests.
[0113] Through priority management and phased processing of data requests, this embodiment can effectively ensure priority response to key data when the system processes multiple business requests, thereby improving the processing efficiency and response speed of the system, while ensuring consistency and stability in the data sharing process.
[0114] In one embodiment, in the above S30, the business attribute data pushed to the centralized variable pool is stored in the Vuex state machine in a modular manner, including:
[0115] S301, dividing the business attribute data collected in the centralized variable pool into multiple bands according to a preset time interval, and sending business data access requests to the server in sequence;
[0116] S302, after receiving the service attribute data response returned by the server, parsing the service attribute data, and grouping the service attribute data according to a predefined storage rule;
[0117] S303, packaging the grouped data into independent modules and storing them in the Vuex state machine.
[0118] In this embodiment, the system divides the business attribute data collected from the centralized variable pool into multiple bands at preset time intervals. These data bands are organized according to a certain logic and order, and the data in each band represents a data set. The system will send data access requests to the server in turn to obtain and process the data. For example, in a financial system, the system can collect customer transaction data every 5 minutes, divide it into multiple bands, and send data requests to the server in sequence, so as to gradually obtain and process the data to ensure the real-time and integrity of the data.
[0119] When the system receives the business attribute data returned by the server, it will immediately parse the data. The parsing process includes data format conversion, verification, etc. The system groups the parsed data according to predefined storage rules for subsequent modular storage.
[0120] After the system completes the data grouping process, it will package the grouped data into independent modules. Each module corresponds to a specific data set, and these modularized data will be stored in the Vuex state machine to ensure data sharing and access between different components.
[0121] In one specific implementation, in a bank's multi-account management system, the system divides business attribute data into multiple bands based on account type and transaction frequency. Unlike the basic implementation method, the system in this method dynamically adjusts the time interval of the bands. For example, for transaction data of high-frequency accounts, the system will shorten the time interval and collect and process data more frequently; for low-frequency accounts, the time interval will be appropriately extended. The system then sends these band data to the server in sequence, and parses and groups the data according to the transaction amount and risk level. Finally, the grouped data will be packaged into modules and stored in the Vuex state machine, allowing the system to respond quickly during high-frequency transactions while optimizing the efficiency of data storage and access.
[0122] In another specific implementation, in the insurance company's claims system, the system divides the business attribute data into multiple bands according to the complexity and urgency of the claims case. The extended technical feature is that the system will combine the artificial intelligence (AI) model to preliminarily classify the claims data. For example, AI is used to determine the complexity of the claims case and adjust the processing order of the data bands accordingly. For complex or urgent claims cases, the system will give priority to processing and parsing these data, grouping the data according to different stages of the case (such as preliminary review and review), and packaging them into independent modules and storing them in the Vuex state machine. In this way, the system can process and respond to the needs of urgent cases in real time, while effectively managing and storing complex claims data.
[0123] This embodiment processes the business attribute data according to predetermined rules and time intervals to ensure that the data can be organized and stored in a modular form, which not only improves the organization and manageability of the system, but also optimizes the access speed and storage efficiency of the data.
[0124] In one embodiment, in the above S302, parsing the business attribute data and grouping the business attribute data according to a predefined storage rule includes:
[0125] S3021, parsing the business attribute data, identifying and extracting business fields in the business attribute data;
[0126] S3022, assigning a corresponding rule number to each business field according to business requirements and predefined storage rules, wherein the rule number is used to guide grouping and storage of the business fields;
[0127] S3023, applying a corresponding storage rule according to the rule number of each business field, and grouping the business fields in a modular manner.
[0128] In this embodiment, the system first parses the received business attribute data and identifies the various business fields in the data. This step involves formatting, field identification and extraction of data to ensure that the data can be correctly understood and processed. For example, in an insurance claim system, when receiving claim application data, the system will parse the data and identify various key fields, such as "customer name", "policy number", "claim amount", etc. Through parsing, the system can extract these fields and prepare for subsequent grouping and storage.
[0129] The system assigns a rule number to each identified business field based on business requirements and predefined storage rules. This number is used to guide subsequent grouping and storage, ensuring that each field can be accurately classified and managed. For example, in a bank's customer management system, the system may assign the number 001 to "customer identity information", the number 002 to "account information", and the number 003 to "transaction records". Through this numbering, the system can group related fields and store them in corresponding modules for quick access and processing.
[0130] After identification and numbering, the system applies predefined storage rules according to the assigned rule numbers to group business fields in a modular manner. Each grouping corresponds to an independent storage module, and these modular data are ultimately stored in the system for subsequent use. For example, in a financial trading system, the system may store "high-frequency trading data" and "low-frequency trading data" separately in different modules according to the rule numbers, which can optimize the access speed of data and improve the processing efficiency of the system.
[0131] In one specific implementation, in the customer relationship management (CRM) system of a bank, the system parses and groups business attribute data based on the customer's transaction history and account type. The system introduces an adaptive parsing mechanism that can dynamically adjust the depth and accuracy of data parsing according to the complexity of customer behavior. For high-net-worth customers, the system will perform more fine-grained parsing, such as identifying detailed information such as the customer's investment preferences and transaction frequency, and assigning more precise rule numbers to these data. Then, based on these numbers, the system modularly groups the data according to dimensions such as investment product type and risk preference, thereby providing account managers with a more comprehensive and personalized customer portrait. This expansion not only improves the accuracy of data parsing, but also enhances the system's service capabilities for high-value customers.
[0132] In another specific implementation, in the insurance company's claims management system, the system will parse the business attribute data according to different claims types and risk levels. The system adopts a multi-level rule numbering system to assign multi-level rule numbers to each business field. For example, for a claim application, the system first assigns a first-level number according to the claim type (such as 001 for auto insurance and 002 for health insurance), and then assigns a second-level number according to the claim amount (such as A for large amounts and B for small amounts). In the data grouping stage, the system not only groups the data according to the first-level number, but also performs more detailed modular storage according to the second-level number. For example, the system will store large auto insurance claims data in a separate module, and small health insurance claims data in another module. This multi-level numbering and grouping method can better support complex claims processing processes and ensure the structuring and efficient management of data.
[0133] By analyzing the business attribute data and identifying the fields, the system can accurately manage and group the data, thereby improving the structured degree of data storage and access efficiency. The method of assigning rule numbers and modular grouping according to storage rules not only simplifies the data management process, but also ensures that the system can quickly respond to different business needs, improving the flexibility and processing performance of the overall system.
[0134] In one embodiment, in the above S3023, after the business fields are grouped in a modular manner, the following step is further included:
[0135] S3024, selecting a rendering target and an output format according to business requirements or user instructions;
[0136] S3025, extracting the grouped and stored business field data from the Vuex state machine, and determining a corresponding rendering template according to the rendering target;
[0137] S3026, binding the extracted business field data to the rendering template, filling the business field data into a specified position of the rendering template, and generating a preliminary rendering result;
[0138] S3027, formatting the preliminary rendering result using the output format to obtain a target rendering result.
[0139] In this embodiment, the system selects a suitable rendering target and output format according to specific business needs or user instructions. The rendering target refers to the type of content that is finally presented, such as a report, chart, or user interface, while the output format involves a specific presentation method, such as PDF, HTML, or image file. For example, in a banking system, a customer manager may need to generate a customer credit assessment report, the rendering target is a credit report, and the output format is selected as PDF format for easy printing and sharing.
[0140] The system extracts the business field data that has been grouped and stored in a modular manner from the Vuex state machine, and then determines the corresponding rendering template based on the selected rendering target. The rendering template is a predefined format structure that contains rules for how the data is displayed in the final output.
[0141] The system binds the extracted business field data to the rendering template and fills the data into the specified position of the template to generate a preliminary rendering result. This step ensures that the data is presented in a structured manner. For example, in a financial transaction system, the system may generate a transaction history report. The transaction data will be bound to specific positions in the report template, such as the timeline, amount column, etc., to generate a preliminary rendering result that displays the customer's transaction history.
[0142] After generating the preliminary rendering results, the system will further format the results according to the specified output format to ensure that the final output rendering results meet the expected format standards and business requirements.
[0143] In one specific implementation, in the bank's loan approval system, the system needs to generate different types of approval reports. The system supports multi-target rendering, that is, generating different rendering targets on the same data set. For example, the system can extract customer loan application data from the Vuex state machine, and then choose to generate two different rendering targets, "Loan Risk Assessment Report" and "Customer Credit Summary". The system will select a suitable rendering template for binding and filling, and after generating the preliminary rendering results, format the results into PDF and HTML formats respectively to meet different business needs. Multi-target rendering expands the application scope of the system, enabling it to more flexibly handle multiple display requirements of the same data set.
[0144] In this embodiment, through the selection of rendering targets and the templated binding of data, the system can generate structured rendering results that meet format requirements according to business needs. This modular rendering process improves the efficiency and customizability of data display, ensuring the high quality and business relevance of the output content. At the same time, the system significantly improves the speed and consistency of data output through automated formatting processing, meeting the diverse needs of different business scenarios.
[0145] In one embodiment, the above S301 includes:
[0146] S3011, dividing the business attribute data collected in the centralized variable pool into a plurality of bands according to a preset time interval;
[0147] S3012, before sending each service data access request, dynamically adjust the sending frequency of the next service data access request according to the current load and network status;
[0148] S3013, real-time monitoring of I / O performance and network status, and dynamic adjustment of the amount of service attribute data sent in each batch;
[0149] S3014, classifying and prioritizing the business data access request according to the urgency and importance of the business data access request;
[0150] S3015: Send the service data access request for each band to the server in sequence according to the sending frequency of the service data access request, the quantity and priority of the service attribute data sent in each batch.
[0151] In this embodiment, the system divides the business attribute data collected in the centralized variable pool into multiple bands according to preset time intervals. These bands represent the data accumulated in a certain period of time, and the system will process and send data access requests for these bands in sequence. For example, in a financial system, the system can divide the customer's transaction records into a band every 10 minutes, so as to gradually process the data and ensure that the system is not impacted by a sudden large amount of data.
[0152] Before sending a business data access request, the system will first dynamically adjust the frequency of the next request based on the current system load and network conditions. If the system load is high or the network conditions are poor, the system may reduce the frequency of requests to prevent excessive use of system resources.
[0153] The system monitors I / O performance and network conditions in real time, and dynamically adjusts the amount of business attribute data sent in each batch based on these monitoring results. In this way, the system can maximize data transmission efficiency without affecting performance. For example, in an insurance claims system, the system may increase the amount of claims data sent in each batch when the network conditions are good, thereby speeding up the claims process; when the network conditions are poor, the amount of data is reduced to ensure stable system operation.
[0154] The system categorizes business data access requests based on their urgency and importance, and sets a priority for each request. High-priority requests are processed first to ensure that critical business data can be responded to quickly. For example, in a banking system, requests involving large fund transfers may be assigned a high priority, while ordinary account query requests are assigned a low priority. The system will prioritize high-priority requests to ensure that fund transfers can be completed in a timely manner.
[0155] The system sends service data access requests for each band to the server in turn according to the transmission frequency, data volume and priority. In this way, the system ensures the orderliness and efficiency of data access requests.
[0156] In one specific implementation, in a bank's real-time transaction monitoring system, the system divides business attribute data into multiple bands based on the frequency and importance of transactions. The system introduces an adaptive time interval adjustment mechanism, which dynamically adjusts the preset time interval based on the intensity of transaction activities. For example, during peak trading hours, the system will shorten the time interval to collect and process transaction data more frequently to ensure that key transactions can be monitored in a timely manner. At the same time, before sending each data request, the system dynamically adjusts the sending frequency based on the current server load and network conditions to prevent system overload. Under high load conditions, the system will give priority to high-priority transaction requests and postpone other requests until the system load is reduced.
[0157] In another specific implementation, in the insurance company's claims processing system, the system divides the data into bands according to the complexity and urgency of the claims cases. The system introduces a predictive scheduling mechanism that predicts future system load and network conditions by analyzing historical data and the characteristics of current cases, and adjusts the sending frequency and data volume in advance. For example, for a large number of claims applications that are expected to be processed, the system will reduce the sending frequency of non-urgent data requests in advance to reserve more resources for important claims data requests. At the same time, the system will monitor the I / O performance in real time, and dynamically adjust the amount of claims data sent in each batch based on the monitoring results to ensure that the system can stably handle claims requests during peak periods.
[0158] This embodiment dynamically adjusts the sending frequency and data volume of data requests, combined with real-time monitoring of system load and network conditions. This method can optimize data transmission efficiency and system resource utilization, while ensuring priority processing of critical business data, thereby improving the stability and response speed of the system in a high-load environment, and ensuring the timeliness and reliability of data access requests.
[0159] The present invention also provides a cross-component data sharing device, referring to Figure 2 , Figure 2 This is a functional module diagram of a preferred embodiment of a cross-component data sharing device of the present invention. The cross-component data sharing device comprises:
[0160] Centralized variable pool module, building a centralized variable pool for centralized management and storage of business attribute data, and integrating the Vuex state machine in the centralized variable pool;
[0161] A business attribute collection plug-in module, which configures a business attribute collection plug-in in a business component, and pushes the business attribute data in the business component to the centralized variable pool through the business attribute collection plug-in;
[0162] The data storage and management module stores the business attribute data pushed to the centralized variable pool in the Vuex state machine in a modular manner. The modular storage includes classification and grouping of business attribute data, dividing the data into multiple modules according to different business logics, and defining the access rights and cache strategies of each module.
[0163] The data access and sharing module accesses the centralized variable pool through business components to achieve sharing of the business attribute data.
[0164] The specific implementation of the cross-component data sharing device of the present invention is basically the same as the various embodiments of the cross-component data sharing method described above, and will not be repeated here.
[0165] The present invention also provides a cross-component data sharing device, such as Figure 3As shown, the cross-component data sharing device may include: a processor 1001, such as a CPU, a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 may be a high-speed RAM memory, or a stable memory (non-volatile memory), such as a disk memory. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.
[0166] Those skilled in the art will understand that Figure 3 The hardware structure of the cross-component data sharing device shown in the figure does not constitute a limitation of the cross-component data sharing device, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.
[0167] like Figure 3 As shown, the memory 1005 as a storage medium may include an operating system, a network communication module, a user interface module, and a cross-component data sharing program. The operating system is a program for managing and controlling cross-component data sharing devices and software resources, and supports the operation of the network communication module, the user interface module, the cross-component data sharing program, and other programs or software; the network communication module is used to manage and control the network interface 1004; and the user interface module is used to manage and control the user interface 1003.
[0168] exist Figure 3 In the cross-component data sharing device hardware structure shown, the network interface 1004 is mainly used to connect to the background server and communicate data with the background server; the user interface 1003 is mainly used to connect to the client and communicate data with the client; the processor 1001 can call the cross-component data sharing program stored in the memory 1005 and perform the same operations as the cross-component data sharing method.
[0169] The specific implementation of the cross-component data sharing device of the present invention is basically the same as the various embodiments of the above-mentioned cross-component data sharing method, and will not be repeated here.
[0170] In addition, an embodiment of the present invention further proposes a computer storage medium on which a cross-component data sharing program is stored. When the cross-component data sharing program is executed by a processor, the steps of the cross-component data sharing method described above are implemented.
[0171] The specific implementation of the computer storage medium of the present invention is basically the same as the above-mentioned embodiments of the cross-component data sharing method, and will not be repeated here.
[0172] The embodiments of the present invention are described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the enlightenment of the present invention, ordinary technicians in this field can also make many forms without departing from the scope of protection of the present invention and the claims. All equivalent structures or equivalent process changes made using the contents of the specification and drawings of the present invention, or directly or indirectly used in other related technical fields, are protected by the present invention.
[0173] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to the multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or the flowchart, and the combination of boxes in the block diagram and / or the flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.
[0174] In addition, each functional module in each embodiment of the present application can be integrated together to form an independent part, or each module can exist separately, or two or more modules can be integrated to form an independent part. If the function is implemented in the form of a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, RandomAccess Memory), a disk or an optical disk.
[0175] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.
[0176] The above are only various implementations of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
Claims
1. A cross-component data sharing method, characterized in that: The following steps are involved: Build a centralized variable pool for centralized management and storage of business attribute data, and integrate the Vuex state machine in the centralized variable pool; A business attribute collection plug-in is configured in the business component, and the business attribute data in the business component is pushed to the centralized variable pool through the business attribute collection plug-in; The business attribute data pushed to the centralized variable pool is stored in the Vuex state machine in a modular manner. The modular storage includes classification and grouping of business attribute data, dividing the data into multiple modules according to different business logics, and defining access rights and cache strategies for each module; The centralized variable pool is accessed through business components to achieve sharing of the business attribute data.
2. The cross-component data sharing method according to claim 1, characterized in that: Pushing the business attribute data in the business component to the centralized variable pool through the business attribute collection plug-in includes: Setting an anti-shake time threshold, when the service attribute collection plug-in receives a data collection instruction, starts an anti-shake mechanism; If no new data collection instruction is received within the anti-shake time threshold, the business attribute data is pushed from the business component to the centralized variable pool through the business attribute collection plug-in; If a new data collection instruction is received within the anti-shake time threshold, all received data collection instructions are aggregated and merged into one data collection task through the anti-shake mechanism; After the anti-shake time threshold ends, the data collection task is executed through the business attribute collection plug-in, and the corresponding business attribute data is collected from the business component and pushed to the centralized variable pool.
3. The cross-component data sharing method according to claim 1, characterized in that: Accessing the centralized variable pool through business components to achieve sharing of the business attribute data includes: Assigning priorities to business attribute data requests based on the importance of the business attribute data; In the process of the business component initiating a business attribute data request to the centralized variable pool, the business attribute data request is divided into a plurality of stages according to the assigned priorities, and the business attribute data requests at different stages are processed in order of priority; Before the business attribute data request of each stage is sent to the centralized variable pool, a corresponding data request task is generated, and the data request task manages and executes the business attribute data request according to the priority; After the data request task of each stage is generated and sent to the centralized variable pool, the centralized variable pool receives and processes the business attribute data request of each stage, and returns the corresponding business attribute data to the business component.
4. The cross-component data sharing method according to claim 1, characterized in that: The business attribute data pushed to the centralized variable pool is stored in the Vuex state machine in a modular manner, including: According to a preset time interval, the business attribute data collected in the centralized variable pool is divided into multiple bands, and business data access requests are sent to the server in sequence; After receiving the service attribute data response returned by the server, the service attribute data is parsed and the service attribute data is grouped according to a predefined storage rule; The grouped data is packaged into independent modules and stored in the Vuex state machine.
5. The cross-component data sharing method as claimed in claim 4, characterized in that: Parsing the business attribute data and grouping the business attribute data according to a predefined storage rule includes: Parsing the business attribute data, identifying and extracting business fields in the business attribute data; According to business requirements and predefined storage rules, a corresponding rule number is assigned to each business field, and the rule number is used to guide the grouping and storage of the business field; The corresponding storage rules are applied according to the rule number of each business field to group the business fields in a modular manner.
6. The cross-component data sharing method according to claim 5, characterized in that: After grouping the business fields in a modular way, it also includes: Select rendering target and output format based on business needs or user instructions; Extract the grouped and stored business field data from the Vuex state machine, and determine the corresponding rendering template according to the rendering target; Binding the extracted business field data to the rendering template, filling the business field data into a specified position of the rendering template, and generating a preliminary rendering result; The preliminary rendering result is formatted using the output format to obtain a target rendering result.
7. The cross-component data sharing method according to claim 4, characterized in that: According to a preset time interval, the business attribute data collected in the centralized variable pool is divided into multiple bands, and business data access requests are sent to the server in sequence, including: According to a preset time interval, the business attribute data collected in the centralized variable pool is divided into a plurality of bands; Before sending each business data access request, dynamically adjust the sending frequency of the next business data access request according to the current load and network conditions; Monitor I / O performance and network status in real time, and dynamically adjust the amount of business attribute data sent in each batch; Categorize and prioritize business data access requests based on their urgency and importance; The service data access request for each band is sent to the server in sequence according to the sending frequency of the service data access request, the quantity and priority of the service attribute data sent in each batch.
8. A cross-component data sharing device, characterized in that: The cross-component data sharing device comprises: Centralized variable pool module, building a centralized variable pool for centralized management and storage of business attribute data, and integrating the Vuex state machine in the centralized variable pool; A business attribute collection plug-in module, which configures a business attribute collection plug-in in a business component, and pushes the business attribute data in the business component to the centralized variable pool through the business attribute collection plug-in; The data storage and management module stores the business attribute data pushed to the centralized variable pool in the Vuex state machine in a modular manner. The modular storage includes classification and grouping of business attribute data, dividing the data into multiple modules according to different business logics, and defining the access rights and cache strategies of each module. The data access and sharing module accesses the centralized variable pool through business components to achieve sharing of the business attribute data.
9. A cross-component data sharing device, characterized in that: The cross-component data sharing device includes a memory, a processor, and a cross-component data sharing program stored in the memory and executable on the processor. When the cross-component data sharing program is executed by the processor, the steps of the cross-component data sharing method as described in any one of claims 1 to 7 are implemented.
10. A computer storage medium, characterized in that: The storage medium stores a cross-component data sharing program, which, when executed by a processor, implements the steps of the cross-component data sharing method according to any one of claims 1 to 7.
Citation Information
Patent Citations
Front-end rendering method and device
CN112579939A
Plug-in type development system and method based on VUE
CN116414386A
Data sharing system based on Vuex architecture
CN116450249A
Component dynamic loading method and device, electronic equipment and storage medium
CN117435262A
Cited By
Low-code platform data exchange method and system based on Web variable pool, medium and equipment
CN120743236A
Component center isolation sharing device based on containerized packaging and operation method
CN122310516A
