A service processing method and device, and a storage medium

Abstract

The application discloses a service processing method and device and a storage medium. It relates to the technical field of data processing. The method can be applied to an electronic device with processing capability. The method comprises the following steps: the electronic device receives a request message, and the request message is used for requesting to run a first service component. Then, the electronic device determines a first data field according to the service requirement of the first service component. The first data field is a data field required for running the first service component. If the first data field is also used for a second service component, the electronic device acquires the data of the first data field according to the configuration information of a common service component, and runs the first service component according to the data of the first data field, wherein the configuration information of the common service component is used for indicating the data field commonly used by multiple service components. The method is used to solve the problem that the existing service component cannot manage background data due to management conflicts when calling the same data field.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a business processing method, apparatus and storage medium. Background Technology

[0002] The online operations of the business platform require a large amount of backend data for support. This backend data includes various types of data, necessitating its management. To address this, data domains are introduced, with each data domain corresponding to a specific data type. This allows for the management of multiple types of backend data.

[0003] During business operations, data within a data domain is modified and maintained by calling that domain. In some scenarios, the same data domain may be called by different business components, causing conflicts and making it impossible to manage that data domain effectively. Summary of the Invention

[0004] This application provides a business processing method, apparatus, and storage medium to solve the problem that existing business models have management conflicts when calling the same data domain, which makes it impossible to manage the backend data.

[0005] Firstly, this application provides a business processing method. This method can be used in an electronic device with processing capabilities. Specifically, the method includes: the electronic device receiving a request message for requesting the execution of a first business component; then, the electronic device determining a first data domain based on the business requirements of the first business component, wherein the first data domain is the data domain required to run the first business component; if the first data domain is also used by a second business component, the electronic device obtaining data from the first data domain according to the configuration information of a common business component, and running the first business component based on the data from the first data domain, wherein the configuration information of the common business component indicates the data domain shared by multiple business components.

[0006] In this embodiment, a common business component is introduced to manage data domains shared by multiple business components. When a first or second business component uses a shared data domain, it can obtain data from the common business component and modify the data in that domain. This avoids management conflicts related to shared data domains.

[0007] Optionally, before obtaining the data of the first data domain based on the configuration information of the common business component, the method further includes: obtaining the configuration information of each business component in at least one business component, wherein the configuration information of each business component is used to indicate at least one data domain maintained by the business component. Then, based on the first configuration information of the first business component and the configuration information of at least one business component, it is determined that the first data domain is also used in the second business component.

[0008] Optionally, after determining that the first data domain is also used in the second business component, the method further includes: updating the first data domain to the data domain maintained by the common business component.

[0009] Optionally, if the first data domain is not present in at least one data domain maintained by the first service component, the method further includes: determining, based on the first configuration information, that the first data domain maintained by the first service component does not include the first data domain, and obtaining the third configuration information of the third service component. The third service component maintains at least one data domain including the first data domain, and the third service component is a service component other than the common service component. Then, the data of the first data domain is obtained based on the third configuration information.

[0010] Optionally, after obtaining data from the first data domain based on the third configuration information, the method further includes: generating an enumeration class of the first business component based on the data in the first data domain, wherein the enumeration class is used to verify the data referenced by the first business component.

[0011] In this embodiment, the maintenance of non-shared data domains is assigned to a third business component. When the first business component uses a data domain not maintained by itself, it can obtain data from the first data domain based on the configuration information of the third business component. Simultaneously, an enumeration class using the first data domain is generated in the runtime code of the first business component. The first business component cannot modify the first data domain itself, but modifications made to the first data domain by the third business component can be viewed through the enumeration class code.

[0012] Optionally, after updating the first data domain to the data domain maintained by the common business component, the method further includes: obtaining the second configuration information of the second business component. Based on the first configuration information and the second configuration information, it is determined that the first data domain is only used by the first business component. Then, the first data domain is deleted from the common business component.

[0013] Secondly, this application provides a service processing apparatus. The apparatus includes a receiving module, a determining module, and an acquiring module. The receiving module receives a request message requesting the execution of a first service component. The determining module determines a first data domain based on the service requirements of the first service component; the first data domain is the data domain required to run the first service component. The acquiring module, if the first data domain is also used by a second service component, acquires data from the first data domain based on the configuration information of a common service component, and executes the first service component based on the data from the first data domain. The configuration information of the common service component indicates the data domain shared by multiple service components.

[0014] Optionally, the determining module is further configured to: obtain configuration information of each business component in at least one business component, wherein the configuration information of each business component is used to indicate at least one data field maintained by the business component. Then, based on the first configuration information of the first business component and the configuration information of at least one business component, it is determined that the first data field is also used in the second business component.

[0015] Optionally, the determination module is also used to: update the first data domain to the data domain maintained by the public business component.

[0016] Optionally, the acquisition module is further configured to: determine, based on the first configuration information, that at least one data domain maintained by the first business component does not include the first data domain, and acquire the third configuration information of the third business component. The third business component maintains at least one data domain including the first data domain, and the third business component is a business component other than the common business component. Then, the data of the first data domain is acquired based on the third configuration information.

[0017] Optionally, the acquisition module is also used to: generate an enumeration class of the first business component based on the data of the first data field, which is used to verify the data referenced by the first business component.

[0018] Optionally, the determining module is further configured to: obtain second configuration information of the second business component; determine, based on the first and second configuration information, that the first data field is used only by the first business component; and then delete the first data field from the common business component.

[0019] Thirdly, embodiments of this application provide an electronic device including a processor and a memory communicatively connected to the processor. The memory stores computer-executable instructions, which are executed by the processor to enable the processor to perform the method described in any one of the first aspects above.

[0020] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, cause the processor to perform the method described in any one of the first aspects.

[0021] Fifthly, embodiments of this application provide a computer program product, which includes a computer program stored in a computer-readable storage medium. A processor can read the computer program from the computer-readable storage medium, and when the processor executes the computer program, it can implement the method described in any one of the first aspects above. Attached Figure Description

[0022] Figure 1 This application provides schematic diagrams illustrating the structures of various service components in its embodiments.

[0023] Figure 2 This is a schematic diagram of the structure of the common service component provided in the embodiments of this application;

[0024] Figure 3 A flowchart illustrating the business processing method provided in the embodiments of this application;

[0025] Figure 4 This is a schematic diagram of the structure of the business processing apparatus provided in the embodiments of this application;

[0026] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0027] To facilitate those skilled in the art to understand the solutions provided in the embodiments of this application, some terms used in the embodiments of this application will be briefly explained before introducing this application.

[0028] 1) A data domain refers to a collection of data with the same type (characteristics). For example, the data acquisition time is a data domain; in other words, the acquisition time of different types of data can be divided into a data domain. Another example is image data, where the location information of the image data is a data domain; in other words, the location information of the image acquisition is a data domain. A data domain can be represented by data values. When the data values ​​of a data domain are presented in list form, the corresponding data values ​​can be called code items in the data domain. In other words, code items belong to the data domain. When the range of values ​​of a data domain comes from a list, the values ​​in that list are called code items of that data domain. Data in a data domain is stored in a database, specifically, using predefined data types. Predefined data types can be predefined static variables or predefined enumeration variables.

[0029] 2) Enumeration class is a data type specifically used to store enumeration values. It can also be considered as representing data in the data field through enumeration values.

[0030] 3) Business components (business modules) are collections of software functional modules developed to implement corresponding business functions based on the requirements of a specific application business (referred to as business). These software functional modules belong to the next level of logical division units of the application and are a collection of models, including data domains, data items, code items, physical models, service classes, etc. A data item refers to a piece of data that uniquely identifies a data point with business meaning or technical parameters.

[0031] A business component is an abstract functional model. Integrating the functionality and interfaces of business components facilitates business development and maintenance. Business processing involves running one or more business components. Each business process is implemented through business components designed during the development phase of the business platform. In other words, to accommodate diverse business needs, a business platform typically includes multiple business components.

[0032] Each business component, during runtime, invokes data fields to manage the data it requires. A single business component can maintain multiple data fields, and a data field can be invoked by multiple business components. Therefore, a data field invoked by one business component may also be a data field maintained by another business component. The data fields maintained by a business component are configured by the system, for example, by writing configuration information. This configuration information is used to configure the multiple data fields maintained by the business component, and these multiple data fields are stored in the configuration information. Figure 1 This illustrates the structure of various business components of the business platform. Figure 1 Taking business components A, B, ..., N as an example. Business component A maintains data domains A, B, and C. Business component A can handle business transactions A and B. Business component B maintains data domains B, D, and E. Business component B can handle business transaction C. Business component N maintains data domain C, etc.

[0033] When a business component retrieves data from a specific data domain, it needs to first query its own configuration information to determine whether the data domain is one it maintains. If the data domain is one it maintains, the business component retrieves the data from that domain based on the configuration information. If the data domain is not one it maintains, meaning it is maintained by another business component, the business component can retrieve the data from that domain by querying the configuration information of that other business component.

[0034] As mentioned earlier, each business component uses a data domain to manage data. Depending on business needs, different business components may call different business components, and each business component may need to process data from one or more data domains. The data domains that different business components need to process may be different or the same. If the same data domain is called by different business components simultaneously—that is, multiple business components simultaneously manage (e.g., modify) the data in that data domain—it causes management conflicts, making it impossible to manage that data domain. Figure 1For example, business component A maintains data domains A, B, and C, while business component B maintains data domains D, B, and E. Both maintain data domain B simultaneously. In existing technologies, business component A and business component B can modify the data in data domain B at the same time, which will cause data management conflicts.

[0035] In view of this, this application provides a business processing method that resolves data domain management conflicts by introducing a common business component among multiple business components. The data domain maintained by the common business component in this application can be accessed simultaneously by multiple business components; that is, the data domain maintained by the common business component can be used to process different businesses at the same time. Even when the common business component is maintaining a data domain shared by multiple business components, each business component can still access and modify the data within that data domain.

[0036] Please see Figure 2 This illustration shows one structure of a common business component in an embodiment of this application. The structure of the common business component is similar to that of a regular business component. The data fields maintained by the common business component itself are also stored in the configuration information of the common business component. When a data field accessed by a certain business component (e.g., referred to as the first business component) is being accessed by another business component (e.g., referred to as the second business component), the first business component can access that data field from the common business component to obtain and manage the data within it; alternatively, the first business component can inform the common business component that the data it needs to manage will be uniformly managed by the common business component, thereby avoiding management conflicts. Figure 1 and Figure 2 For example, business component A calls data domain B, and business component B also calls data domain B, where data domain B can be maintained by a common component. In this case, business component A can call data domain B from the common component to avoid management conflicts related to data domain B.

[0037] To better understand the above technical solution, the following will provide a detailed explanation of the technical solution in conjunction with the accompanying drawings.

[0038] Please see Figure 3This diagram illustrates a flowchart of a business processing method provided in an embodiment of this application. This method can be executed by an electronic device with processing capabilities, including personal computers (PCs), terminals, etc. Of course, the type of electronic device in this embodiment is not limited to these. It should be noted that the ordinal numbers such as "first" and "second" mentioned in this application are used to distinguish multiple objects and are not used to limit the size, content, order, timing, application scenario, priority, or importance of the multiple objects. For example, the first business component, the second business component, and the third business component can be any other business component in the business platform besides the common business components.

[0039] Furthermore, the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article, unless otherwise specified, generally indicates that the preceding and following related objects have an "or" relationship.

[0040] S301. The electronic device receives a request message, which is used to request the operation of the first service component.

[0041] The first business component can be used to process data for one or more business processes. For a specific business process, depending on its requirements, it may be necessary to invoke the corresponding first business component. When the first business component needs to be invoked, the user can operate the business platform on the electronic device, causing the electronic device to generate a request message based on the user's actions. For example, a button (a software button) can be set on the business platform; when the user triggers this button, the electronic device can generate a request message. The electronic device then responds to the request message and runs the first business component.

[0042] S302. The electronic device determines the first data domain according to the business requirements of the first business component. The first data domain is the data domain required to run the first business component.

[0043] The electronic device determines, based on business needs, that the first business component needs to access the first data domain, which means it needs to manage the data indicated by the first data domain. For example, if the first business component is involved in deposit services, the business requirement is to recommend storage services to users based on their storage activity over the past month. The first business component determines that the first data domain to access is the data collection time domain.

[0044] S303. If the first data domain is also used for the second service component, the electronic device obtains the data of the first data domain according to the configuration information of the common service component, and runs the first service component according to the data of the first data domain.

[0045] It is understandable that a data domain may be called or managed by two business components simultaneously. When an electronic device determines whether the first data domain is also called by a second business component, it can obtain the configuration information of each business component in at least one business component (i.e., other business components besides the first business component), and then determine that the first data domain is also used by the second business component based on the configuration information of the first business component and the configuration information of at least one business component.

[0046] It should be understood that each business component independently maintains its own data domain. Within the same time period, modification and maintenance of each data domain can only be performed by one business component; otherwise, management conflicts will occur. Therefore, this application introduces a common business component, which maintains the data domains shared by multiple business components. In other words, the management authority for data domains shared by multiple business components belongs to the common business component. If any business component discovers that a data domain it needs to access is also being accessed by another business component, then that business component can access that data domain from the common business component. For example, if an electronic device determines that a first data domain is also being accessed by a second business component, then it can access the first data domain from the common business component.

[0047] In this embodiment, after the electronic device determines that the first data field is used by both the first service component and the second service component, the electronic device can update the first data field to the data field maintained by the common service component. Thus, for data fields shared by multiple service components, they are maintained by the common service component. Similarly, all data fields shared by multiple service components are updated to the common service component.

[0048] It can be seen that the first data field can be maintained by the first business component, the second business component, and the common business component. Accordingly, the first business component's access to the first data field includes the following three scenarios:

[0049] First, the first data domain is maintained by the first business component. The first business component can then retrieve data from the first data domain based on its own configuration information. After retrieving the data from the first data domain, the first business component can modify and maintain the data within it.

[0050] II. The first data domain is maintained by a common business component. The first business component can retrieve data from the common business component based on its configuration information. After retrieving the data, the first business component can modify and maintain it. It should be understood that modifications made to the first data domain by the first business component or other business components will also affect the use of the first data domain.

[0051] Third, the first data domain is maintained by a business component other than the common business component. For example, the first data domain is maintained by the second business component. The first business component can obtain data from the first data domain based on the configuration information of the second business component. However, since the first data domain is maintained by the second business component, and the first business component cannot maintain it, after obtaining the data from the second business component, the first business component cannot modify or maintain the data in the first data domain.

[0052] In this embodiment, each business component also maintains its own code related to its operation, which may include an enumeration class. When a business component references data in a data domain, code can be generated using the enumeration class to record the data referenced by the business component. Therefore, the code generated by the enumeration class can verify the data referenced by the business component. When a business component modifies the referenced data, the code in the enumeration class can reflect the modification made by the business component.

[0053] The generation of enumeration class code also varies depending on whether the business component is a common business component or a business component other than a common business component. Taking the first data field as an example, which can be maintained by the first business component, the second business component, and the common business component, the generation of enumeration class code includes the following three cases:

[0054] 1. When the first data field called by the first business component is maintained by the first business component, the first business component generates an enumeration class in its own running code to facilitate the verification of the first business component's modification of the first data field.

[0055] Second, when the first data field referenced by the first business component is maintained by the second business component, the first business component generates an enumeration class in its own running code to facilitate the verification of the second business component's modification of the first data field.

[0056] Third, when the first data field referenced by the first business component is maintained by a common business component, the first business component does not generate an enumeration class in its own running code. Instead, the common business component generates the enumeration class in its running code. Either the first or second business component can view the modifications to the first data field from the enumeration class in the common business component's running code. These modifications can be made by either the first or the second business component.

[0057] When the first data field is maintained by a business component other than the common business component, for example, by a third business component other than the common business component, the electronic device, when referencing the first data field, first determines, based on the first configuration information of the first business component, that at least one data field maintained by the first business component does not include the first data field. Then, the electronic device obtains the third configuration information of the third business component and retrieves the data of the first data field based on the third configuration information. When referencing the first data field, the electronic device generates an enumeration class corresponding to the first data field in the runtime code of the first business component. Since the first business component cannot modify the data in the first data field, but the third business component can modify the data in the first data field, the first business component can view the modifications made to the data in the first data field by the third business component through the generated enumeration class.

[0058] If a data domain is initially maintained by multiple business components, but may later be maintained by only one business component, then the data domain can be removed from the shared business component. For example, initially, the first data domain is shared by the first and second business components, but later the usage of the first data domain changes, and it is maintained solely by the first business component, then the first data domain should be removed from the shared business component. In other words, when the first data domain changes from a shared data domain to a data domain solely maintained by the first business component, it needs to be removed from the shared business component, and the ownership of the first data domain needs to be updated to the first business component.

[0059] When an electronic device determines whether a first data field is maintained by a first service component and not by a second service component, it can obtain second configuration information from the second service component. This second configuration information represents the configuration information of the data field maintained by the second service component after changes. If the changed second configuration information does not include the first data field, the electronic device determines that the first data field is not maintained by the second service component. That is, the electronic device determines, based on the first and second configuration information, that the first data field is used only by the first service component. In this case, the electronic device can delete the first data field from the common service component. In other words, the first data field is assigned to the maintenance of the first service component.

[0060] Based on the same inventive concept, embodiments of this application also provide an apparatus for implementing the above-described business processing method.

[0061] Please see Figure 4Based on the same inventive concept, this application also provides a service processing device 400. The service processing device 400 includes a receiving module 401, a determining module 402, and an acquiring module 403. The receiving module 401 receives a request message requesting the execution of a first service component. The determining module 402 determines a first data domain based on the service requirements of the first service component; the first data domain is the data domain required to run the first service component. The acquiring module 403, if the first data domain is also used by a second service component, acquires data from the first data domain based on the configuration information of a common service component, and runs the first service component based on the data from the first data domain. The configuration information of the common service component indicates the data domain shared by multiple service components.

[0062] Optionally, the determining module 402 is further configured to: obtain configuration information of each business component in at least one business component, wherein the configuration information of each business component is used to indicate at least one data field maintained by the business component. Then, based on the first configuration information of the first business component and the configuration information of at least one business component, it is determined that the first data field is also used in the second business component.

[0063] Optionally, the determining module 402 is also used to: update the first data domain to the data domain maintained by the public business component.

[0064] Optionally, the acquisition module 403 is further configured to: determine, based on the first configuration information, that at least one data field maintained by the first service component does not include the first data field, and acquire the third configuration information of the third service component. The at least one data field maintained by the third service component includes the first data field, and the third service component is a service component other than the common service component. Then, the data of the first data field is acquired based on the third configuration information.

[0065] Optionally, the acquisition module 403 is further configured to: generate an enumeration class of the first business component based on the data of the first data field, the enumeration class being used to verify the data referenced by the first business component.

[0066] Optionally, the determining module 402 is further configured to: obtain second configuration information of the second service component; determine, based on the first configuration information and the second configuration information, that the first data field is used only by the first service component; and then delete the first data field from the common service component.

[0067] Please see Figure 5 Based on the same inventive concept, this application provides an electronic device 500, which includes at least one processor 501, at least one memory 502, and computer program instructions stored in the memory. When the computer program instructions are executed by the processor, the aforementioned gate motor driving method is implemented.

[0068] Optionally, the processor 501 may be a central processing unit, an application-specific integrated circuit (ASIC), one or more integrated circuits for controlling program execution, a hardware circuit developed using a field-programmable gate array (FPGA), or a baseband processor.

[0069] Optionally, the read-write lock operating device further includes a memory 502 connected to at least one processor 501. The memory 502 may include read-only memory (ROM), random access memory (RAM), and disk storage. The memory 502 is used to store data required for the processor 501 to run. There may be one or more memories 502. The memory 502 is used in… Figure 5 It is shown together, but it should be noted that memory 502 is not a mandatory functional module, therefore in Figure 5 It is shown in dashed lines.

[0070] Based on the same inventive concept, embodiments of this application also provide a computer-readable storage medium storing computer instructions that, when executed on a computer, cause the computer to perform the aforementioned gate motor driving method.

[0071] In specific implementation, computer-readable storage media include: Universal Serial Bus flash drive (USB), portable hard drive, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, and other storage media that can store program code.

[0072] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device, and unit described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0073] In the several embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0074] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0075] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0076] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes: Universal Serial Bus flash disks, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, optical disks, and other media capable of storing program code.

[0077] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.

Claims

1. A business processing method, characterized in that, include: Receive a request message, the request message being used to request the execution of a first business component; The first data domain is determined based on the business requirements of the first business component, and the data in the first data domain is the data required to run the first business component. If the first data domain is also used for the second business component, the data of the first data domain is obtained according to the configuration information of the common business component, and the first business component is run according to the data of the first data domain. The configuration information of the common business component is used to indicate the data domain used by multiple business components. Wherein, when it is determined, based on the first configuration information of the first business component, that at least one data field maintained by the first business component does not include the first data field, the third configuration information of the third business component is obtained, wherein the at least one data field maintained by the third business component includes the first data field, and the third business component is a business component other than the common business component; Data from the first data domain is obtained based on the third configuration information.

2. The method as described in claim 1, characterized in that, Before obtaining the data of the first data domain based on the configuration information of the common business components, the method further includes: Obtain the configuration information of each business component in at least one business component, wherein the configuration information of each business component is used to indicate at least one data field maintained by the business component; Based on the first configuration information of the first service component and the configuration information of the at least one service component, it is determined that the first data domain is also used in the second service component.

3. The method as described in claim 2, characterized in that, After determining that the first data domain is also used in the second business component, the method further includes: Update the first data domain to the data domain maintained by the public business component.

4. The method as described in claim 1, characterized in that, After obtaining data from the first data domain based on the third configuration information, the method further includes: An enumeration class for the first business component is generated based on the data in the first data field. The enumeration class is used to verify the data referenced by the first business component.

5. The method as described in claim 3, characterized in that, After updating the first data domain to the data domain maintained by the public business component, the method further includes: Obtain the second configuration information of the second business component; Based on the first configuration information and the second configuration information, it is determined that the first data domain is used only for the first business component; Delete the first data field in the public business component.

6. A business processing apparatus, characterized in that, include: A receiving module is configured to receive a request message, wherein the request message is used to request the execution of a first business component; The determination module is used to determine a first data domain based on the business requirements of the first business component, wherein the data in the first data domain is the data required to run the first business component. The acquisition module is used to acquire data from the first data domain according to the configuration information of the common business component if the first data domain is also used for the second business component, and to run the first business component according to the data from the first data domain, wherein the configuration information of the common business component is used to indicate the data domain used by multiple business components. The acquisition module is further configured to: when it is determined, based on the first configuration information of the first business component, that at least one data field maintained by the first business component does not include the first data field, acquire the third configuration information of the third business component, wherein the at least one data field maintained by the third business component includes the first data field, and the third business component is a business component other than the common business component; and acquire the data of the first data field based on the third configuration information.

7. The apparatus as claimed in claim 6, characterized in that, The determining module is also used for: Obtain the configuration information of each business component in at least one business component, wherein the configuration information of each business component is used to indicate at least one data field maintained by the business component; Based on the first configuration information of the first service component and the configuration information of the at least one service component, it is determined that the first data domain is also used in the second service component.

8. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-5.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-5.

10. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1-5.

Images