Business processing method, apparatus, device, and computer-readable storage medium
By identifying target components and processing order, establishing parameter mapping relationships, and dynamically organizing the component chain, the problems of insufficient component integration complexity and scalability in existing technologies are solved, thereby improving the system's flexibility and scalability.
Patent Information
- Application Number
- CN202510025175.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-01-07
- Publication Date
- 2026-07-07
AI Technical Summary
In existing technologies, business processing requires developers to have professional scripting skills, components are highly coupled, and components cannot be dynamically added or removed during system runtime, resulting in insufficient flexibility and scalability.
By determining target components and their processing order based on preset business logic, establishing parameter mapping relationships, dynamically organizing component chains, supporting the loading and unloading of components during system runtime, and defining component interactions through a visual interface, the technical threshold is lowered.
It enables seamless integration and communication between components, improves system flexibility and scalability, reduces component integration complexity, and supports rapid adaptation to changes in business needs.
Smart Images
Figure CN122346302A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of software development technology, and in particular to a business processing method, apparatus, device, and computer-readable storage medium. Background Technology
[0002] API orchestration refers to the process of managing and configuring APIs. API orchestration can integrate different services together to form a coordinated system.
[0003] In existing technologies, developers need to write scripts using programming languages to orchestrate APIs and integrate different services to meet business requirements. If new business requirements need to be addressed, the corresponding scripts need to be rewritten. Furthermore, existing technologies typically manage components using static configuration, making it impossible to dynamically add or remove components at runtime.
[0004] Therefore, the existing business processes require developers to have professional scripting skills. At the same time, the multiple integrated services are highly coupled, and components cannot be dynamically added or removed during system runtime, resulting in insufficient flexibility and scalability. Summary of the Invention
[0005] To address the aforementioned technical problems, this disclosure provides a business processing method, apparatus, device, and computer-readable storage medium to improve the system's flexibility and scalability.
[0006] In a first aspect, embodiments of this disclosure provide a business processing method, including:
[0007] Based on the business logic of the preset business, determine multiple target components required to implement the preset business, as well as the business processing order between each target component;
[0008] Based on the business processing sequence, determine the parameter mapping relationship between every two adjacent target components;
[0009] Based on the parameter mapping relationship and the business processing order, the multiple target components are organized into a component chain corresponding to the preset business.
[0010] The preset service is processed through the component chain.
[0011] In some embodiments, before determining the multiple target components required to implement the preset service and the business processing order between each target component based on the business logic of the preset service, the method further includes:
[0012] During system operation, in response to component loading requests, the system obtains component information for newly added components;
[0013] Based on the component information, the newly added component is published to the system.
[0014] In some embodiments, the component information includes the interface definition information of the newly added component; the determination of multiple target components required to implement the preset service based on the business logic of the preset service includes:
[0015] If the target component includes the newly added component, then at least one adjacent component that is adjacent to the newly added component in the business processing sequence is determined.
[0016] Based on the interface definition information of the newly added component, interface association information between the newly added component and each of the adjacent components is constructed, so that the newly added component and each of the adjacent components can exchange data based on the interface association information.
[0017] In some embodiments, determining the parameter mapping relationship between every two adjacent target components according to the business processing order includes:
[0018] For every two adjacent target components, determine multiple candidate parameters output by the first component, where the first component is the target component that has the earlier business processing order among the two adjacent target components.
[0019] Based on the input parameters required by the second component, at least one target parameter is determined from the plurality of candidate parameters, wherein the second component is the target component that is later in the business processing order among the two adjacent target components.
[0020] In some embodiments, determining at least one target parameter from the plurality of candidate parameters based on the input parameters required by the second component includes:
[0021] In response to the user's selection operation of the multiple candidate parameters, at least one target parameter is determined from the multiple candidate parameters.
[0022] In some embodiments, after determining at least one target parameter from the plurality of candidate parameters based on the input parameters required by the second component, the method further includes:
[0023] For each target parameter of the second component, a placeholder expression corresponding to the target parameter is generated so that the second component can obtain the target parameter according to the placeholder expression during the processing of the preset service.
[0024] In some embodiments, the business logic based on a preset service, determining multiple target components required to implement the preset service, and the business processing order between each target component, includes:
[0025] A component selection interface is displayed, which includes multiple candidate components;
[0026] In response to the user's selection of the multiple candidate components, multiple target components required to implement the preset service are determined;
[0027] In response to the user's sorting operation on the plurality of target components, the business processing order among each of the target components is determined.
[0028] Secondly, embodiments of this disclosure provide a business processing apparatus, including:
[0029] The first determining module is used to determine, based on the business logic of the preset business, multiple target components required to implement the preset business, and the business processing order between each target component;
[0030] The second determining module is used to determine the parameter mapping relationship between every two adjacent target components according to the business processing order;
[0031] An organization module is used to organize the multiple target components into a component chain corresponding to a preset business according to the parameter mapping relationship and the business processing order;
[0032] The processing module is used to process the preset service through the component chain.
[0033] Thirdly, embodiments of this disclosure provide an electronic device, including:
[0034] Memory;
[0035] Processor; and
[0036] Computer programs;
[0037] The computer program is stored in the memory and configured to be executed by the processor to implement the method as described in the first aspect.
[0038] Fourthly, embodiments of this disclosure provide a computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor to implement the method described in the first aspect.
[0039] Fifthly, embodiments of this disclosure also provide a computer program product, which includes a computer program or instructions that, when executed by a processor, implement the business processing method described above.
[0040] The business processing method, apparatus, device, and computer-readable storage medium provided in this disclosure achieve seamless integration and communication between different components by defining the business processing sequence and the parameter mapping relationship between components. This reduces the complexity of component integration, and each component is relatively independent. As a result, different component chains can be flexibly organized to process corresponding preset businesses according to different business logics, thereby improving the system's flexibility and scalability. Attached Figure Description
[0041] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.
[0042] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0043] Figure 1 A flowchart of a business processing method provided in this embodiment of the disclosure;
[0044] Figure 2 A schematic diagram illustrating an application scenario provided by an embodiment of this disclosure;
[0045] Figure 3 This is a schematic diagram of a preset business process provided in an embodiment of the present disclosure;
[0046] Figure 4 The parameter processing flow of the target component and its original API provided in the embodiments of this disclosure;
[0047] Figure 5 A flowchart of component management provided for embodiments of this disclosure;
[0048] Figure 6 This is a schematic diagram of the structure of a service processing apparatus provided in an embodiment of the present disclosure;
[0049] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Detailed Implementation
[0050] To better understand the above-mentioned objectives, features, and advantages of this disclosure, the solutions disclosed herein will be further described below. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.
[0051] Numerous specific details are set forth in the following description in order to provide a full understanding of this disclosure, but this disclosure may also be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only some, and not all, of the embodiments of this disclosure.
[0052] In early product implementations, adding and removing components was typically done through static configuration. This meant that developers needed to manually configure components before system deployment and redeploy the system when changes were required. This approach was not only time-consuming and labor-intensive but also error-prone, as it demanded a deep understanding of the system's overall architecture and configuration from developers.
[0053] Furthermore, traditional component management methods typically lack dynamism, meaning they cannot dynamically add or remove components while the system is running. This limits the system's flexibility and scalability, making it difficult for the system to quickly adapt to changes in business needs.
[0054] In component integration, API orchestration typically involves point-to-point integration, meaning each API needs to be individually integrated and communicate with other APIs. This approach is not only complex but also difficult to maintain, as the complexity and cost of integration increase dramatically with the number of APIs. Furthermore, traditional API orchestration and integration methods often lack unified standards and specifications. This means different APIs may use different protocols and data formats to communicate. This increases the difficulty and cost of integration and can lead to incompatibility and interoperability issues between systems.
[0055] In summary, these issues limit the system's flexibility and scalability, increase its complexity and maintenance costs, reduce the reusability and sharing of services, and affect the system's ability to iterate rapidly and deliver continuously.
[0056] To address the aforementioned issues, this disclosure provides a business processing method, which will be described below with reference to specific embodiments.
[0057] Figure 1 A flowchart illustrating a business processing method provided in this embodiment of the disclosure. This method can be applied to... Figure 2The application scenario shown includes a gateway 21 and a system 22 with multiple registered components. System 22 can run on a server or terminal, such as a smartphone, PDA, tablet, wearable device with a display, desktop computer, laptop, all-in-one computer, or smart home device. System 22 registers multiple components and their associated native APIs. Component orchestration is achieved by organizing these components through API orchestration. Kong is an open-source, cloud-native, efficient, scalable, and distributed microservice abstraction layer, also known as an API gateway or API middleware. It is built on OpenResty (Nginx + Lua module) and provides RESTful APIs. Its main responsibility is to receive business requests from clients, forward these requests to the system according to preset routing rules, and process the business requests through the system's API orchestration and component orchestration functions.
[0058] It is understood that the business processing methods provided in the embodiments of this disclosure can also be applied in other scenarios.
[0059] The following is about Figure 1 The business processing method shown is described below, and the specific steps included in this method are as follows:
[0060] S101. Based on the business logic of the preset business, determine multiple target components required to implement the preset business, and the business processing order between each target component.
[0061] Pre-defined business processes refer to pre-defined business processes or business objectives that users need to perform, aiming to achieve specific business processing flows. These business processing flows are the business logic of the pre-defined business processes.
[0062] The target component refers to the multiple components that are associated with the preset business among the multiple components registered in the system.
[0063] The components are abstracted from common services and implement their functions by calling the original APIs in the system, thereby enabling the sharing and reuse of services across different projects or systems.
[0064] First, based on the multiple services involved in the preset business, identify multiple target components among the multiple components existing in the system that can perform the aforementioned services. Specifically, each component is used to support or implement at least one service in the preset business.
[0065] The business processing order between each target component refers to the order in which these components are executed in the business process. The business logic provides the implementation order of multiple services involved in the preset business; correspondingly, the business processing order between each target component can be determined based on the implementation order of multiple services.
[0066] Specifically, the business processing order between target components is divided into concurrent order, branch order, and serial order, and the components involved are called concurrent components, branch components, and serial components.
[0067] Concurrent components refer to components that can be executed simultaneously without any dependency on each other's execution results; branching components are used to determine the path of API calls based on specific conditions or logical decisions, and select different execution paths based on input parameters or certain conditions; sequential components refer to components that are executed one after another in sequence, with the output of each component becoming the input of the next component, and there are clear dependencies between components, requiring the previous component to complete before the execution of the next component can begin.
[0068] S102. Determine the parameter mapping relationship between every two adjacent target components according to the business processing order.
[0069] Parameter mapping refers to the correspondence between the output parameters of the previous component and the input parameters of the next component when data is transferred between adjacent components in the business processing sequence.
[0070] It is understandable that parameter mapping exists between two adjacent target components with a sequential order, but there is no parameter mapping between concurrent components.
[0071] Specifically, for every two adjacent target components, multiple candidate parameters are determined from the output of the first component, where the first component is the target component with the earlier service processing order among the two adjacent target components; based on the input parameters required by the second component, at least one target parameter is determined from the multiple candidate parameters, where the second component is the target component with the later service processing order among the two adjacent target components.
[0072] Between the first and second components, the output parameters of the first component are transmitted to the second component as input parameters. The first component's output parameters include multiple candidate parameters, but not every candidate parameter is a required input parameter for the second component. Based on the service implementation conditions of the second component, at least one candidate parameter is selected as the target parameter, and this target parameter is used as the input parameter of the second component.
[0073] S103. Based on the parameter mapping relationship and the business processing order, organize the multiple target components into a component chain corresponding to the preset business.
[0074] Based on the parameter mapping relationship and business processing order determined in the above steps, business data can be transmitted in the correct order among multiple target components until the last target component outputs the data. At this time, the multiple target components and their parameter mapping relationship are regarded as a whole, which is called the component chain.
[0075] Each target component can process input data and provide it to the system's native API, and process the API response data and output it to the next component for processing. In other words, by organizing the target components, the system's original APIs can be orchestrated, achieving API integration.
[0076] S104. Process the preset service through the component chain.
[0077] The business request data of the preset business is input into the component chain, and multiple target components in the component chain process and transmit the request data to realize the processing of the preset business and finally obtain the business processing result.
[0078] There is a parameter mapping relationship between the component chain and the preset business. Specifically, the request parameters of the preset business are input into the component chain, including determining at least one target parameter from the request parameters as the input parameter of the component chain; the business processing result is obtained through the component chain, including determining at least one target parameter from the output parameters of the component chain as the business processing result.
[0079] Figure 3 This is a schematic diagram of a preset business process provided in an embodiment of this disclosure. For example... Figure 3 As shown, the request parameter is the request parameter from the proxy interface. The input parameters of the component chain are obtained through the request parameter mapping. node1, node2, and node3 are the target components, and the three target components are connected in series. The target parameter is selected from the multiple output parameters of node1 as the input parameter of node2. The target parameter is selected from the multiple output parameters of node2 as the input parameter of node3. Finally, the output parameter of node3 is the response parameter. The business processing result of the preset business is obtained through the response parameter mapping, that is, the response parameter.
[0080] Among them, the request parameter mapping and response parameter mapping are parameter mappings between the Kong gateway proxy and the component chain, which are applied to API orchestration; the parameter mapping between target components is applied to the original API calls of the target components.
[0081] Figure 4 The parameter processing flow for the target component and its original API provided in the embodiments of this disclosure. For example... Figure 4As shown, in the API orchestration process, taking a single target component as an example, in order to map the output parameters (including query, request, and header) of the API in the previous target component or the request parameters from the proxy interface to the input parameters of the API in the next target component, target parameters are selected and input into the target component for processing to provide parameters for the original API; the original API is called to process the parameters to obtain the API response parameters, the API response parameters are processed to obtain the output parameters of the target component, and then the output parameters of the target component are mapped to response parameters to obtain the final output response parameters of the target component.
[0082] This embodiment of the disclosure determines multiple target components required to implement the preset service based on the business logic of the preset service, as well as the business processing order between each target component; determines the parameter mapping relationship between every two adjacent target components according to the business processing order; organizes the multiple target components into a component chain corresponding to the preset service according to the parameter mapping relationship and the business processing order; processes the preset service through the component chain; achieves seamless integration and communication between different components by defining the business processing order and the parameter mapping relationship between components, reducing the complexity of component integration, and making each component relatively independent, thereby enabling flexible organization of different component chains to process the corresponding preset service according to different business logic, improving the system's flexibility and scalability.
[0083] Based on the above embodiments, before determining the multiple target components required to implement the preset business and the business processing order between each target component based on the business logic of the preset business, the method further includes: during system operation, in response to a component loading request, obtaining component information of the newly added component; and publishing the newly added component to the system according to the component information.
[0084] Optionally, during system operation, in response to a component registration request, the system obtains the component information of the newly added component; and registers the newly added component into the system based on the component information.
[0085] Users can perform component management operations in the system, such as registering components, deleting components, and loading or unloading components. Figure 5 A flowchart illustrating the component management process provided in this embodiment of the disclosure. Figure 5 As shown, taking the user's interaction with the system through a browser as an example, the system includes a controller, a file service, and a database.
[0086] During component registration, users provide component information for each new component, including a unique component identifier and interface definition information to enable communication and data transfer between components. After registering the component to the system's component library, the API orchestration engine will be able to identify and call the required component. Users can provide component information for each new component by uploading a JAR file. Figure 4 As shown, users create components in the system and upload JAR files. After the system verifies the components and stores the component information, it returns the storage result, informing the user that the component registration was successful.
[0087] Specifically, the component information includes the interface definition information of the newly added component; the step of determining multiple target components required to implement the preset service based on the business logic of the preset service includes: if the target components include the newly added component, then determining at least one adjacent component adjacent to the newly added component in the service processing order; and constructing interface association information between the newly added component and each of the adjacent components according to the interface definition information of the newly added component, so that the newly added component and each of the adjacent components can exchange data based on the interface association information.
[0088] When a new component is to be applied to a pre-defined service, it needs to be able to exchange data normally with its neighboring components. Based on the interface definition information provided by the user, the interface association information between the new component and each of the neighboring components is constructed.
[0089] In the business logic of a predefined business, two adjacent components use the output parameters of the preceding component as the input parameters of the following component. Since the original APIs called by these two components are different, their corresponding interface specifications, request parameter formats, and response parameter formats may differ. Eliminating these differences based on the interface association information between adjacent components ensures that the output parameters of the preceding component are correctly processed by the original API called by the following component.
[0090] Correspondingly, when a component needs to be deleted from the system, the user submits a component deletion command to the system. After receiving the component deletion command, the system identifies the component corresponding to the deletion command and verifies the user's identity information and component usage information. If it is determined that the user has the operation permission and that the deletion of the component will not affect the ongoing business processing, the system deletes the component information in the database and returns the operation result, informing the user that the component deletion was successful.
[0091] The system also supports dynamically loading and unloading components at runtime without restarting the system or interrupting business operations, enabling hot-swapping of components. When loading a component, the system matches and validates it against its identifier and interface definition to ensure compatibility and correctness, and changes the component's state to "published" so that the API orchestration engine can call it. When unloading a component, the system releases the corresponding resources and updates the component's state in the system to "unpublished." Finally, the system provides feedback to the user on the results of the component loading or unloading operation.
[0092] The system maintains the status information of each component, including whether it is published and whether it is available. When any component fails or requires maintenance, the system can mark it as unavailable and automatically select another available component to replace it.
[0093] The embodiments disclosed herein improve the flexibility and scalability of the system by dynamically loading or unloading components during system runtime without restarting the entire system or application, enabling the system to adapt to changing needs more quickly.
[0094] Furthermore, this embodiment of the disclosure defines unified interface specifications and calling logic by constructing interface association information between components, thereby combining different components to achieve complex business functions. This orchestration capability enables the system to process requests more efficiently, while improving the system's maintainability and reusability.
[0095] In some embodiments, users can define the business logic of a preset business and the data transfer standards between components in a visual manner.
[0096] The business logic based on the preset business determines multiple target components required to implement the preset business, and the business processing order between each target component, including: displaying a component selection interface, which includes multiple candidate components; determining multiple target components required to implement the preset business in response to the user's selection operation of the multiple candidate components; and determining the business processing order between each target component in response to the user's sorting operation of the multiple target components.
[0097] The component selection interface displays multiple candidate components, and users can select one or more of them as the target component by clicking.
[0098] Optionally, the multiple candidate components displayed in the component selection interface are automatically selected by the system based on the business logic of the preset business.
[0099] Optionally, the candidate components can be grouped and / or categorized in the component selection interface to facilitate user search and use.
[0100] After identifying the target components, users can sort multiple target components by dragging and dropping the corresponding icons of each target component, such as sequential execution, conditional branching, and loop execution. They can also define the dependencies between multiple target components by drawing directed line segments and define the data flow paths between target components.
[0101] As described above, for every two adjacent target components, multiple candidate parameters are determined from the output of the first component, where the first component is the target component with the earlier service processing order among the two adjacent target components; based on the input parameters required by the second component, at least one target parameter is determined from the multiple candidate parameters, where the second component is the target component with the later service processing order among the two adjacent target components.
[0102] Specifically, determining at least one target parameter from the plurality of candidate parameters based on the input parameters required by the second component includes: determining at least one target parameter from the plurality of candidate parameters in response to the user's selection operation on the plurality of candidate parameters.
[0103] After the target component is determined, each target component will display multiple candidate parameters it outputs. Taking the first component as an example, when the user defines the parameter mapping relationship between the first component and the second component, the user can select from the multiple candidate parameters of the first component to determine at least one target parameter.
[0104] Optionally, for each target parameter of the second component, a placeholder expression corresponding to the target parameter is generated, so that the second component can obtain the target parameter according to the placeholder expression during the processing of the preset service.
[0105] Whenever a user specifies a target parameter, a placeholder expression corresponding to that target parameter is generated.
[0106] The placeholder expression contains the identifier of the API called by the second component, the value type of the parameter, and the business field of the parameter, which can be represented as: ${api_code.value_type.business_field}.
[0107] For example, the first component implements functionality by calling api1, and the second component implements functionality by calling api2; when api2 depends on the data.uid field of api1's response, the placeholder is ${api1.response.data.uid}; when api2 depends on the Cookie field of api1's header, the placeholder is ${api2.header.Cookie}.
[0108] This disclosure embodiment interacts with users through a visual interface, allowing users to quickly define API interfaces and business logic without manually writing code, reducing the technical threshold, improving development efficiency, and making the system more adaptable to changes, quickly responding to changes in business requirements, and accelerating product iteration and release.
[0109] Figure 6 This is a schematic diagram of the structure of a service processing apparatus provided in an embodiment of this disclosure. The service processing apparatus may be a terminal running a system as described in the above embodiments, or the service processing apparatus may be a component or assembly of the terminal. The service processing apparatus provided in this embodiment of the disclosure can execute the processing flow provided in the service processing method embodiments, such as... Figure 6 As shown, the service processing device 60 includes: a first determining module 61, a second determining module 62, an organizing module 63, and a processing module 64; the first determining module 61 is used to determine multiple target components required to implement the preset service, and the service processing order between each target component, based on the service logic of the preset service; the second determining module 62 is used to determine the parameter mapping relationship between every two adjacent target components according to the service processing order; the organizing module 63 is used to organize the multiple target components into a component chain corresponding to the preset service according to the parameter mapping relationship and the service processing order; the processing module 64 is used to process the preset service through the component chain.
[0110] Optionally, the business processing device 60 further includes a loading module 65, which, during system operation, responds to a component loading request, obtains component information of a newly added component, and publishes the newly added component to the system based on the component information.
[0111] Optionally, the component information includes the interface definition information of the newly added component; the first determining module 61 includes a first determining unit 611 and an interface defining unit 612; the first determining unit 611 is used to determine at least one adjacent component in the business processing sequence that is adjacent to the newly added component if the target component includes the newly added component; the interface defining unit 612 is used to construct interface association information between the newly added component and each of the adjacent components according to the interface definition information of the newly added component, so that the newly added component and each of the adjacent components can exchange data based on the interface association information.
[0112] Optionally, the second determining module 62 includes a second determining unit 621 and a third determining unit 622; the second determining unit 621 is used to determine multiple candidate parameters output by the first component for every two adjacent target components, wherein the first component is the target component with the earlier service processing order among the two adjacent target components; the third determining unit 622 is used to determine at least one target parameter from the multiple candidate parameters according to the input parameters required by the second component, wherein the second component is the target component with the later service processing order among the two adjacent target components.
[0113] Optionally, the third determining unit 622 is used to determine at least one target parameter from the multiple candidate parameters in response to the user's selection operation on the multiple candidate parameters.
[0114] Optionally, the second determining module 62 further includes a generating unit 623, which generates a placeholder expression corresponding to each target parameter for the second component, so that the second component can obtain the target parameter according to the placeholder expression during the processing of the preset service.
[0115] Optionally, the first determining module 61 further includes an interaction unit 613, used to display a component selection interface, which includes multiple candidate components; in response to the user's selection operation on the multiple candidate components, to determine multiple target components required to implement the preset business; and in response to the user's sorting operation on the multiple target components, to determine the business processing order between each of the target components.
[0116] Figure 6 The business processing apparatus of the illustrated embodiment can be used to execute the technical solutions of the above method embodiments. Its implementation principle and technical effect are similar, and will not be repeated here.
[0117] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. The electronic device may be a terminal running a system as described in the above embodiments. The electronic device provided in this disclosure can execute the processing flow provided in the service processing method embodiments, such as… Figure 7 As shown, the electronic device 70 includes: a memory 71, a processor 72, a computer program, and a communication interface 73; wherein the computer program is stored in the memory 71 and configured to be executed by the processor 72 using the business processing method described above.
[0118] In addition, this disclosure also provides a computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor to implement the business processing method described in the above embodiments.
[0119] Furthermore, this disclosure also provides a computer program product, which includes a computer program or instructions that, when executed by a processor, implement the business processing method described above.
[0120] 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.
[0121] 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 business processing method, characterized in that, The method includes: Based on the business logic of the preset business, determine multiple target components required to implement the preset business, as well as the business processing order between each target component; Based on the business processing sequence, determine the parameter mapping relationship between every two adjacent target components; Based on the parameter mapping relationship and the business processing order, the multiple target components are organized into a component chain corresponding to the preset business. The preset service is processed through the component chain.
2. The method according to claim 1, characterized in that, Before determining the multiple target components required to implement the preset service, and the business processing order between each target component, based on the business logic of the preset service, the method further includes: During system operation, in response to component loading requests, the system obtains component information for newly added components; Based on the component information, the newly added component is published to the system.
3. The method according to claim 2, characterized in that, The component information includes the interface definition information of the newly added component; the determination of multiple target components required to implement the preset business based on the business logic of the preset business includes: If the target component includes the newly added component, then at least one adjacent component that is adjacent to the newly added component in the business processing sequence is determined. Based on the interface definition information of the newly added component, interface association information between the newly added component and each of the adjacent components is constructed, so that the newly added component and each of the adjacent components can exchange data based on the interface association information.
4. The method according to claim 1, characterized in that, The step of determining the parameter mapping relationship between every two adjacent target components according to the business processing order includes: For every two adjacent target components, determine multiple candidate parameters output by the first component, where the first component is the target component that has the earlier business processing order among the two adjacent target components. Based on the input parameters required by the second component, at least one target parameter is determined from the plurality of candidate parameters, wherein the second component is the target component that is later in the business processing order among the two adjacent target components.
5. The method according to claim 4, characterized in that, Based on the input parameters required by the second component, at least one target parameter is determined from the plurality of candidate parameters, including: In response to the user's selection operation of the multiple candidate parameters, at least one target parameter is determined from the multiple candidate parameters.
6. The method according to claim 4, characterized in that, After determining at least one target parameter from the plurality of candidate parameters based on the input parameters required by the second component, the method further includes: For each target parameter of the second component, a placeholder expression corresponding to the target parameter is generated so that the second component can obtain the target parameter according to the placeholder expression during the processing of the preset service.
7. The method according to claim 1, characterized in that, The business logic based on the preset business determines multiple target components required to implement the preset business, and the business processing order between each target component, including: A component selection interface is displayed, which includes multiple candidate components; In response to the user's selection of the multiple candidate components, multiple target components required to implement the preset service are determined; In response to the user's sorting operation on the plurality of target components, the business processing order among each of the target components is determined.
8. A business processing device, characterized in that, include: The first determining module is used to determine, based on the business logic of the preset business, multiple target components required to implement the preset business, and the business processing order between each target component; The second determining module is used to determine the parameter mapping relationship between every two adjacent target components according to the business processing order; An organization module is used to organize the multiple target components into a component chain corresponding to a preset business according to the parameter mapping relationship and the business processing order; The processing module is used to process the preset service through the component chain.
9. An electronic device, characterized in that, include: Memory; processor; as well as Computer programs; The computer program is stored in the memory and configured to be executed by the processor to implement the method as described in any one of claims 1-7.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-7.