Back-end system serving front end, data processing method and device, equipment and storage medium
By distributing the BFF execution module across different business servers and managing it uniformly using the BFF management module, the problem of high maintenance costs in the BFF middleware layer is solved, achieving the effects of reducing maintenance costs and improving system stability.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CHENGDU GUANGHEXINHAO TECH CO LTD
- Filing Date
- 2024-11-05
- Publication Date
- 2026-05-08
AI Technical Summary
The BFF middleware layer, as a newly added independent service, needs to be developed and deployed separately, resulting in high operation and maintenance costs.
The BFF execution module is deployed in a distributed manner on different business servers and managed uniformly through the BFF management module, reducing the maintenance requirements of the BFF middleware layer.
This reduces the maintenance cost of the BFF intermediate layer and improves the stability and reliability of the BFF system.
Smart Images
Figure CN121996248A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of data processing, and more particularly to a back-end system, data processing method, apparatus, device, and storage medium that serves a front-end. Background Technology
[0002] In software development, BFF (Backend For Frontend) is an architectural pattern used to solve the problem of interaction and collaboration between clients and business servers. In this architecture, the client does not communicate directly with the business server. Instead, it interacts with the business server through a BFF middleware layer specifically designed for the client to obtain the necessary data. This not only reduces unnecessary data transmission and processing, thereby improving performance, but also keeps the client and business server independent, reducing coupling.
[0003] Currently, the BFF middleware layer is a newly added independent service, requiring separate development and deployment, and maintaining the BFF middleware layer also requires high operation and maintenance costs. Summary of the Invention
[0004] In order to solve the above-mentioned technical problems, or at least partially solve the above-mentioned technical problems, this disclosure provides a back-end system, data processing method, apparatus, device and storage medium for serving the front end.
[0005] In a first aspect, this disclosure provides a backend system that serves the frontend. The system includes a backend BFF management module that serves the frontend and at least one BFF execution module, wherein the at least one BFF execution module is distributed and deployed on different business servers.
[0006] The BFF management module is used to compile the BFF source code submitted by the user to obtain compiled BFF code, and then send the compiled BFF code to the BFF execution module deployed on the target business server; wherein, the BFF source code is generated based on the data processing requirements information of the business client corresponding to the target business server;
[0007] The BFF execution module is used to process data processing requests from the business client by executing the compiled BFF code.
[0008] In one optional implementation, the BFF execution module is equipped with a front-end code executor, which is used to execute the compiled BFF code in the code environment of the target business server.
[0009] In one optional implementation, the BFF execution module is equipped with a code update module, which is used to send a BFF code update request to the BFF management module.
[0010] The BFF management module is specifically used to send the BFF code to be updated to the BFF execution module after receiving the BFF code update request, if it is determined that there is BFF code to be updated.
[0011] In one optional implementation, the BFF management module is specifically used to send the compiled BFF code to the BFF execution module deployed on the target business server when the preset code distribution conditions are met.
[0012] In one optional implementation, the BFF management module is further configured to store the compiled BFF code to a target storage space; wherein the target storage space includes a target database or a target cache.
[0013] In one optional implementation, the target business server includes multiple business servers, each of which is equipped with a BFF execution module.
[0014] In one optional implementation, the BFF execution module is specifically used to obtain the business processing result obtained by the target business server after processing the data processing request from the business client, and then to perform preset logic processing on the business processing result by executing the compiled BFF code to obtain the BFF processing result; wherein, the BFF processing result is used to respond to the data processing request from the business client.
[0015] Secondly, this disclosure provides a data processing method applied to a backend system serving a frontend. The system includes a BFF management module and at least one BFF execution module, wherein the at least one BFF execution module is distributed and deployed on different business servers. The method includes:
[0016] After receiving the BFF source code submitted by the user, the BFF management module compiles the BFF source code to obtain the compiled BFF code, and sends the compiled BFF code to the BFF execution module deployed on the target business server.
[0017] The BFF execution module is invoked to process data processing requests from the business client by executing the compiled BFF code.
[0018] Thirdly, this disclosure provides a data processing apparatus applied to a backend system serving a frontend. The system includes a BFF management module and at least one BFF execution module, wherein the at least one BFF execution module is distributed across different business servers. The apparatus includes:
[0019] The first calling module is used to call the BFF management module to compile the BFF source code submitted by the user after receiving it, and then send the compiled BFF code to the BFF execution module deployed on the target business server.
[0020] The second calling module is used to call the BFF execution module to process data processing requests from the business client by executing the compiled BFF code.
[0021] Fourthly, embodiments of this disclosure also provide an electronic device, the electronic device comprising: a processor; a memory for storing executable instructions of the processor; the processor being configured to read the executable instructions from the memory and execute the instructions to implement the data processing method provided in embodiments of this disclosure.
[0022] Fifthly, embodiments of this disclosure also provide a computer-readable storage medium storing instructions that, when executed on a terminal device, cause the terminal device to implement the data processing method provided in embodiments of this disclosure.
[0023] Sixthly, this disclosure provides a computer program product comprising a computer program / instructions that, when executed by a processor, implement the above-described method.
[0024] The technical solution provided in this disclosure has the following advantages compared with the prior art:
[0025] This disclosure provides a backend system serving a frontend. The system includes a BFF management module and at least one BFF execution module. The at least one BFF execution module is distributed and deployed on different business servers. The BFF management module is used to compile the BFF source code submitted by the user to obtain compiled BFF code, and send the compiled BFF code to the BFF execution module deployed on the target business server. The BFF source code is generated based on the data processing requirements of the business client corresponding to the target business server. The BFF execution module is used to process the data processing requests from the business client by executing the compiled BFF code.
[0026] In the BFF system provided in this disclosure, each BFF execution module in the backend system serving the frontend is distributed and deployed on different business service terminals. At the same time, the BFF management module is used to uniformly manage each BFF execution module. Compared with the architecture implementation method of deploying the BFF middleware layer as an independently deployed service, this disclosure embodiment does not require separate maintenance of the BFF middleware layer, thus reducing maintenance costs. Attached Figure Description
[0027] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.
[0028] Figure 1 A schematic diagram of a BFF architecture pattern provided in an embodiment of this disclosure;
[0029] Figure 2 A schematic diagram of a backend BFF system serving the frontend, provided as an embodiment of this disclosure;
[0030] Figure 3 This disclosure provides a data processing interaction diagram between a business server and a BFF execution module.
[0031] Figure 4 This is a schematic diagram of the structure of a BFF management module provided in an embodiment of the present disclosure;
[0032] Figure 5 A flowchart of a data processing method provided in this disclosure embodiment;
[0033] Figure 6 This is a schematic diagram of the structure of a data processing apparatus provided in an embodiment of the present disclosure;
[0034] Figure 7 This is a schematic diagram of the structure of a data processing device provided in an embodiment of the present disclosure. Detailed Implementation
[0035] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.
[0036] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.
[0037] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.
[0038] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.
[0039] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".
[0040] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.
[0041] In software development, BFF (Backend For Frontend) is an architectural pattern used to solve the problem of interaction and collaboration between clients and business servers. In this architecture, the client does not communicate directly with the business server. Instead, it interacts with the business server through a BFF middleware layer specifically designed for the client to obtain the necessary data. This not only reduces unnecessary data transmission and processing, thereby improving performance, but also keeps the client and business server independent, reducing coupling.
[0042] like Figure 1 The diagram illustrates a BFF (Browser Forwarding) architecture pattern in related technologies. In this BFF architecture, the BFF service is deployed as a new, independent service between the client and the business server to facilitate interaction between them. However, due to the diverse data processing needs between the business client and the business server, the aforementioned BFF architecture pattern requires high operational costs.
[0043] To this end, this disclosure provides a backend system serving a frontend. The system includes a backend BFF management module and at least one BFF execution module, which are distributed across different business servers. The BFF management module, upon receiving BFF source code submitted by a user, compiles the source code to obtain compiled BFF code and sends the compiled BFF code to the BFF execution module deployed on the target business server. The BFF source code is generated based on the data processing requirements of the business client corresponding to the target business server. The BFF execution module processes data processing requests from the business client by executing the compiled BFF code.
[0044] In the BFF system provided in this disclosure, each BFF execution module in the backend system serving the frontend is distributed and deployed on different business service terminals. At the same time, the BFF management module is used to uniformly manage each BFF execution module. Compared with the architecture implementation method of deploying the BFF middleware layer as an independently deployed service, this disclosure embodiment does not require separate maintenance of the BFF middleware layer, thus reducing maintenance costs.
[0045] Based on this, the present disclosure provides a backend BFF system that serves the frontend, referencing... Figure 2 This is a schematic diagram of the structure of a backend system serving a frontend, provided in an embodiment of this disclosure. Figure 2 Taking this as an example, we will introduce the architecture of the backend system that serves the frontend provided in this disclosure.
[0046] Among them, business client 201 can refer to the initiator of data requests and the data consumer. This business client can be deployed on terminals such as smartphones, tablets, and desktop computers.
[0047] The backend system 202 that serves the frontend includes a BFF management module 205 and at least one BFF execution module, such as BFF execution module 206 and BFF execution module 207.
[0048] The BFF management module receives BFF source code submitted by users. Upon receiving the source code, it compiles it to obtain compiled BFF code and sends it to the BFF execution module deployed on the target business server. The BFF source code is generated based on the data processing requirements of the corresponding business client. In other words, the BFF source code is generated using a code editor for the target business client. In practice, developers can write BFF source code based on the business client's data processing requirements and submit it to the BFF management module. Furthermore, the submitted BFF source code can include an identifier for the target business server to identify the business server where the BFF source code needs to be deployed.
[0049] In addition, when the data processing requirements of the business client corresponding to the target business server change, the BFF source code can be updated and resubmitted to the BFF management module. The BFF management module can then compile the BFF source code and send it to the BFF execution module of the target business server. By distributing the compiled BFF code through the BFF management module, the impact on the target business server can be reduced.
[0050] In one optional implementation, the BFF management module is also used to centrally manage the compiled BFF code, so that when there is a deployment requirement in the BFF middleware layer, the compiled BFF code can be easily sent to the BFF execution module of the target business server. By centrally managing the compiled BFF code to be deployed in each BFF execution module through the BFF management module, the reliability of the BFF code can be improved, and code updates and backtracking can be facilitated in the event of subsequent anomalies.
[0051] The target business server can include one or more business servers, each with a corresponding BFF execution module deployed within it. In other words, different business servers handle different business processes, and therefore have different internally deployed BFF execution modules. These BFF execution modules can be pre-deployed as needed, either as an SDK or a plugin. The business server receives data processing requests from business clients and performs business logic processing based on these requests. This business logic processing can include data processing procedures such as permission checks, security interception, and parameter processing.
[0052] In this embodiment, the BFF execution module is distributed and deployed on different business servers, which realizes that the BFF execution modules of each business server are independent of each other and do not interfere with each other, thereby improving the stability and reliability of the BFF middleware function to a certain extent.
[0053] In the above Figure 2 In the middle, the backend system 202, which serves the frontend, contains multiple BFF execution modules. Each BFF execution module is deployed in a different business server, such as... Figure 2 As shown, BFF execution module 206 is deployed in business server 203, and BFF execution module 207 is deployed in business server 204.
[0054] The BFF execution module, also known as the BFF client, is used to process data processing requests from business clients by executing compiled BFF code. That is, when the target business server receives a data processing request from a business client, the BFF execution module processes that request; it does not need to directly handle data processing requests from the business client. This BFF execution module can be deployed on the business server as a plugin or SDK.
[0055] The BFF execution module deployed on the business server in this embodiment can process the data after the business server has processed the data processing request from the business client. That is, the BFF execution module performs post-processing on the data processing request, such as data cleaning and data format conversion. Alternatively, it can process the data processing request from the business client before the business server performs business logic processing. That is, the BFF execution module performs pre-processing, such as data verification. The specific processing flow can be set according to specific requirements.
[0056] In one optional implementation, the BFF execution module can be used to obtain the business processing result obtained by the target business server after processing the data processing request from the business client, and then execute the compiled BFF code to perform preset logic processing on the business processing result to obtain the BFF processing result. The aforementioned BFF execution module performs post-processing.
[0057] The BFF processing result is used to respond to data processing requests from business clients.
[0058] like Figure 3The diagram shown illustrates a data processing interaction between a business server and a BFF execution module according to an embodiment of this disclosure. When the business server receives a data processing request from a business client, it performs pre-processing of the data request, business logic processing, and other business processing procedures. Then, it sends the business processing result to the BFF execution module, which performs corresponding data processing on the business processing result and returns the BFF processing result to the business client.
[0059] In one alternative implementation, in order to push the compiled BFF code to the BFF execution module of the corresponding target server, a corresponding business identifier can be set when the user develops the BFF source code, and then the BFF source code can be submitted to the BFF management module.
[0060] In one optional implementation, to reduce the impact of the backend system serving the frontend on users, preset code delivery conditions can be set in the BFF management module. Specifically, after receiving the BFF source code submitted by the user and compiling it to obtain the compiled BFF code, the BFF management module sends the compiled BFF code to the BFF execution module deployed on the target business server when it determines that the compiled code meets the preset code delivery conditions. The preset code delivery condition can be the code release time, which can be a relatively idle time for the backend system serving the frontend, such as 24:00 every night.
[0061] In one optional implementation, to facilitate code backtracking, the BFF management module included in the backend system serving the frontend can also set up a storage function for the compiled BFF code to facilitate problem location and code rollback. Specifically, a target storage space is set in the BFF management module, and the compiled BFF code is stored in the target storage space. The target storage space includes a target database or a target cache.
[0062] To facilitate understanding of the BFF management module, a structural diagram of a BFF management module is provided for an embodiment of this disclosure, referencing... Figure 4 Developers develop BFF source code based on the data processing requirements of the business client and submit it to the BFF management module 401. After receiving the BFF source code submitted by the user, the BFF management module compiles and stores the BFF source code. When the compiled BFF code meets the preset code distribution conditions, the module publishes the compiled BFF code and pushes it to the BFF execution module 402 on the target business server.
[0063] In one alternative implementation, since the compiled BFF code is developed using a front-end language, a front-end code executor can be deployed in the BFF execution module to execute the compiled BFF code in the code environment of the target business server.
[0064] In one optional implementation, to ensure that the BFF execution module can execute the latest compiled BFF code, a code update module can also be deployed in the BFF execution module. The code update module is used to send BFF code update requests to the BFF management module, that is, to update the edited BFF code in a timely manner by actively pulling the code.
[0065] In an optional implementation, based on the above embodiments, the BFF management module may also have a query function. Specifically, after receiving a BFF code update request, the BFF management module queries whether there is BFF code to be updated. If it is determined that there is BFF code to be updated, the BFF code to be updated is sent to the BFF execution module.
[0066] To facilitate understanding of the above embodiments, please refer to the above... Figure 4 The BFF execution module 402 includes a code update module and a front-end code executor. The code update module sends a BFF code update request to the BFF management module 401. Upon receiving the code update request from the BFF execution module 402, the BFF management module checks whether there is BFF code to be updated. If it is determined that there is BFF code to be updated, it pushes the BFF code to be updated to the BFF execution module of the target business server.
[0067] This disclosure provides a backend system serving a frontend, comprising a backend BFF management module and at least one BFF execution module, wherein the at least one BFF execution module is distributed and deployed on different business servers. The BFF management module, upon receiving BFF source code submitted by a user, compiles the BFF source code to obtain compiled BFF code, and sends the compiled BFF code to the BFF execution module deployed on the target business server. The BFF source code is generated based on the data processing requirements of the business client corresponding to the target business server. The BFF execution module processes data processing requests from the business client by executing the compiled BFF code.
[0068] In the BFF system provided in this disclosure, each BFF execution module in the backend system serving the frontend is distributed and deployed on different business service terminals. At the same time, the BFF management module is used to uniformly manage each BFF execution module. Compared with the architecture implementation method of deploying the BFF middleware layer as an independently deployed service, this disclosure embodiment does not require separate maintenance of the BFF middleware layer, thus reducing maintenance costs.
[0069] Correspondingly, this disclosure also provides a data processing method, for reference Figure 5 This is a flowchart of a data processing method provided in an embodiment of the present disclosure. The method is applied to a backend system serving a frontend. The system includes a BFF management module and at least one BFF execution module, wherein the at least one BFF execution module is distributed and deployed on different business servers. The method includes:
[0070] S501: After receiving the BFF source code submitted by the user, the BFF management module compiles the BFF source code to obtain the compiled BFF code, and sends the compiled BFF code to the BFF execution module deployed on the target business server.
[0071] The BFF source code is generated based on the data processing requirements of the business client corresponding to the target business server.
[0072] In this embodiment of the disclosure, the target business server may include one or more business servers, each of which has a corresponding BFF execution module deployed. That is, different business servers handle different businesses, and their internally deployed BFF execution modules are different. The BFF execution modules in different business servers can be pre-deployed according to requirements, and the BFF execution modules can be pre-deployed in the corresponding business server in the form of SDK or plugin.
[0073] The BFF execution module, also known as the BFF client, is used to process data processing requests from business clients by executing compiled BFF code. That is, when the business server receives a data processing request from a business client, the BFF execution module processes that request; it does not need to directly handle the data processing requests from the business client. This BFF execution module can be deployed on the business server as a plugin or SDK.
[0074] S502: The BFF execution module is invoked to process the data processing request from the business client by executing the compiled BFF code.
[0075] In practical applications, the BFF execution module can be invoked to perform pre-processing or post-processing of data processing requests from the business client by executing the compiled BFF code.
[0076] In one optional implementation, after the target business server processes the data processing request from the business client and obtains the business processing result, it calls the BFF execution module to retrieve the business processing result. The BFF processing result is then obtained by executing the compiled BFF code to perform preset logic processing on the business processing result. This is post-processing.
[0077] Since the compiled BFF code is developed using a front-end language, to enable the execution of this compiled BFF code in the business server's code environment, the BFF execution module in this embodiment can also deploy a front-end code executor for executing the compiled BFF code in the target business server's code environment. Specifically, the front-end code executor in the BFF execution module executes the compiled BFF code to process data processing requests from the business client.
[0078] In this embodiment of the disclosure, the BFF execution module can also be deployed with a code update module. Specifically, the code update module in the BFF execution module is called to send a BFF code update request to the BFF management module.
[0079] Based on the above embodiments, the BFF management module in this disclosure also has a query function. Specifically, when the BFF management module receives a BFF code update request, it queries whether there is BFF code to be updated. If it is determined that there is BFF code to be updated, the BFF code to be updated is sent to the BFF execution module.
[0080] In one optional implementation, to reduce the impact of backend systems serving the frontend on users, preset code distribution conditions can be set for code deployment. Specifically, preset code distribution conditions are set in the BFF management module. After receiving the BFF source code submitted by the user, the BFF management module compiles the BFF source code to obtain compiled BFF code. When it is determined that the compiled code meets the preset code distribution conditions, the BFF management module sends the compiled BFF code to the BFF execution module deployed on the target business server.
[0081] The preset code distribution condition can be the code release time, which can be a relatively idle time for the backend system serving the frontend, such as 24:00 every night.
[0082] In one optional implementation, to facilitate code backtracking, the BFF management module can also be configured with a storage function for the compiled BFF code, facilitating problem location and code rollback. Specifically, a target storage space is set in the BFF management module, and the module is invoked to store the compiled BFF code in the target storage space. The target storage space may include a target database or a target cache.
[0083] The data processing method provided in this embodiment is first applied to a backend system serving a frontend. The system includes a BFF management module and at least one BFF execution module, wherein the at least one BFF execution module is distributed and deployed on different business servers. The method includes: calling the BFF management module to compile the BFF source code submitted by the user to obtain compiled BFF code, and sending the compiled BFF code to the BFF execution module deployed on the target business server; and calling the BFF execution module to process the data processing request from the business client by executing the compiled BFF code.
[0084] In the BFF system provided in this disclosure, each BFF execution module in the backend system serving the frontend is distributed and deployed on different business service terminals. At the same time, the BFF management module is used to uniformly manage each BFF execution module. Compared with the architecture implementation method of deploying the BFF middleware layer as an independently deployed service, this disclosure embodiment does not require separate maintenance of the BFF middleware layer, thus reducing maintenance costs.
[0085] Based on the above method embodiments, this disclosure also proposes a data processing apparatus. Figure 6 This is a schematic diagram of a data processing device provided in an embodiment of the present disclosure. The device can be implemented by software and / or hardware and is generally integrated into an electronic device. This data processing device is applied to a backend system serving a frontend. The system includes a BFF management module and at least one BFF execution module, which is distributed across different business servers. Figure 6 As shown, the device includes:
[0086] The first calling module 601 is used to call the BFF management module to compile the BFF source code submitted by the user after receiving it, and to send the compiled BFF code to the BFF execution module deployed on the target business server.
[0087] The second calling module 602 is used to call the BFF execution module to process data processing requests from the business client by executing the compiled BFF code.
[0088] In one optional implementation, a front-end code executor is deployed in the BFF execution module, and the device further includes:
[0089] The third calling module is used to call the front-end code executor in the BFF execution module to execute the compiled BFF code in the code environment of the target business server.
[0090] In one optional implementation, the BFF execution module deploys a code update module, and the apparatus further includes:
[0091] The fourth calling module is used to call the code update module in the BFF execution module to send a BFF code update request to the BFF management module;
[0092] The fifth calling module is used to call the BFF management module to send the BFF code to be updated to the BFF execution module after receiving the BFF code update request and determining that there is BFF code to be updated.
[0093] In one optional embodiment, the apparatus further includes:
[0094] The sixth calling module is used to call the BFF management module to send the compiled BFF code to the BFF execution module deployed on the target business server when the preset code distribution conditions are met.
[0095] In one optional embodiment, the apparatus further includes:
[0096] The seventh calling module is used to call the BFF management module to store the compiled BFF code to the target storage space; wherein, the target storage space includes a target database or a target cache.
[0097] In one optional implementation, the target business server includes multiple business servers, each of which is equipped with a BFF execution module.
[0098] In one optional embodiment, the apparatus further includes:
[0099] The eighth calling module is used to call the BFF execution module to execute the compiled BFF code to perform preset logic processing on the business processing result obtained by the target business server after processing the data processing request from the business client, so as to obtain the BFF processing result; wherein, the BFF processing result is used to respond to the data processing request from the business client.
[0100] In the data processing apparatus provided in this embodiment, after receiving the BFF source code submitted by the user, the BFF management module compiles the BFF source code to obtain compiled BFF code, and sends the compiled BFF code to the BFF execution module deployed on the target business server; the BFF execution module then processes the data processing request from the business client by executing the compiled BFF code.
[0101] In the BFF system provided in this disclosure, each BFF execution module in the backend system serving the frontend is distributed and deployed on different business service terminals. At the same time, the BFF management module is used to uniformly manage each BFF execution module. Compared with the architecture implementation method of deploying the BFF middleware layer as an independently deployed service, this disclosure embodiment does not require separate maintenance of the BFF middleware layer, thus reducing maintenance costs.
[0102] The data processing apparatus provided in this disclosure can execute the document image processing method provided in any embodiment of this disclosure, and has the corresponding functional modules and beneficial effects for executing the method.
[0103] To implement the above embodiments, this disclosure also proposes a computer program product, including a computer program / instructions, which, when executed by a processor, implement the data processing method described above.
[0104] In addition to the methods and apparatus described above, this disclosure also provides a computer-readable storage medium storing instructions that, when executed on a terminal device, cause the terminal device to implement the data processing method described in this disclosure.
[0105] In addition, this disclosure also provides a data processing device, see [link to relevant documentation]. Figure 7 As shown, it may include:
[0106] The data processing device includes a processor 701, a memory 702, an input device 703, and an output device 704. The number of processors 701 in the data processing device can be one or more. Figure 7 Taking a processor as an example. In some embodiments of this disclosure, the processor 701, memory 702, input device 703, and output device 704 can be connected via a bus or other means, wherein, Figure 7 Taking the example of a connection between China and Israel via a bus.
[0107] The memory 702 can be used to store software programs and modules. The processor 701 executes various functional applications and data processing of the data processing device by running the software programs and modules stored in the memory 702. The memory 702 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function, etc. In addition, the memory 702 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. The input device 703 can be used to receive input digital or character information, and to generate signal inputs related to user settings and function control of the data processing device.
[0108] Specifically in this embodiment, the processor 701 loads the executable files corresponding to the processes of one or more applications into the memory 702 according to the following instructions, and the processor 701 runs the applications stored in the memory 702, thereby realizing the various functions of the above-mentioned data processing device.
[0109] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0110] The above description is merely a specific embodiment of this disclosure, enabling those skilled in the art to understand or implement it. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not to be limited to the embodiments described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A backend system serving a frontend, characterized in that, The system includes a backend BFF management module that serves the front end and at least one BFF execution module, wherein the at least one BFF execution module is distributed and deployed on different business servers. The BFF management module is used to compile the BFF source code submitted by the user to obtain compiled BFF code, and then send the compiled BFF code to the BFF execution module deployed on the target business server; wherein, the BFF source code is generated based on the data processing requirements information of the business client corresponding to the target business server; The BFF execution module is used to process data processing requests from the business client by executing the compiled BFF code.
2. The backend system serving the frontend according to claim 1, characterized in that, The BFF execution module is equipped with a front-end code executor, which is used to execute the compiled BFF code in the code environment of the target business server.
3. The backend system serving the frontend according to claim 1, characterized in that, The BFF execution module is equipped with a code update module, which is used to send BFF code update requests to the BFF management module. The BFF management module is specifically used to send the BFF code to be updated to the BFF execution module after receiving the BFF code update request, if it is determined that there is BFF code to be updated.
4. The backend system serving the frontend according to claim 1, characterized in that, The BFF management module is specifically used to send the compiled BFF code to the BFF execution module deployed on the target business server when the preset code distribution conditions are met.
5. The backend system serving the frontend according to claim 1, characterized in that, The BFF management module is also used to store the compiled BFF code to a target storage space; wherein the target storage space includes a target database or a target cache.
6. The backend system serving the frontend according to claim 1, characterized in that, The target business server includes multiple business servers, each of which has a BFF execution module deployed on it.
7. The backend system serving the frontend according to claim 1, characterized in that, The BFF execution module is specifically used to obtain the business processing result obtained by the target business server after processing the data processing request from the business client, and then to execute the compiled BFF code to perform preset logic processing on the business processing result to obtain the BFF processing result; wherein, the BFF processing result is used to respond to the data processing request from the business client.
8. A data processing method, characterized in that, An application to a backend system serving a frontend, the system comprising a BFF management module and at least one BFF execution module, wherein the at least one BFF execution module is distributed and deployed on different business servers, the method comprising: After receiving the BFF source code submitted by the user, the BFF management module compiles the BFF source code to obtain the compiled BFF code, and sends the compiled BFF code to the BFF execution module deployed on the target business server. The BFF execution module is invoked to process data processing requests from the business client by executing the compiled BFF code.
9. A data processing apparatus, characterized in that, An apparatus for use in a backend system serving a frontend, the system comprising a BFF management module and at least one BFF execution module, wherein the at least one BFF execution module is distributed across different business servers, the apparatus comprising: The first calling module is used to call the BFF management module to compile the BFF source code submitted by the user after receiving it, and then send the compiled BFF code to the BFF execution module deployed on the target business server. The second calling module is used to call the BFF execution module to process data processing requests from the business client by executing the compiled BFF code.
10. An electronic device, characterized in that, The electronic device includes: processor; Memory used to store the processor's executable instructions; The processor is configured to read the executable instructions from the memory and execute the instructions to implement the data processing method of claim 8.
11. A computer-readable storage medium, characterized in that, The storage medium stores a computer program for executing the data processing method described in claim 8.
12. A computer program product, characterized in that, The computer program product includes a computer program / instruction that, when executed by a processor, implements the data processing method as described in claim 8.