Event-driven processing method and device, equipment, medium and product

Abstract

The invention provides an event-driven processing method and device, equipment, a medium and a product. Relates to the technical field of data processing. The method comprises the following steps: acquiring a to-be-processed application service demand; determining a business application according to a to-be-processed application service demand; querying a service application interface in a preset service application container according to the service application; determining a corresponding technical component according to the business application; querying a technical component interface in a preset technical component container according to the technical component; configuring a framework starter according to the business application interface and the technical component interface; and the business application is started through the framework starter, so that the flexibility of event-driven processing is improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to an event-driven processing method, apparatus, device, medium, and product. Background Art

[0002] As financial markets continue to develop, transaction volumes continue to expand, transaction frequency increases dramatically, and trading strategies become increasingly complex. Automated trading systems must make real-time trading decisions and execute trades based on market fluctuations. This constantly changing market information can be considered as different types of external events, to which automated trading systems must respond immediately. Therefore, event-driven frameworks are currently the mainstream implementation model for building automated trading systems.

[0003] In related technologies, event-driven frameworks typically consist of only a basic event-driven engine, upon which application developers can define event types and corresponding processing logic. Furthermore, each application implemented using an existing event-driven framework will load all technical modules upon startup.

[0004] This will result in poor flexibility in event-driven processing. Summary of the Invention

[0005] The present application provides an event-driven processing method, apparatus, device, medium and product to solve the problem of poor flexibility of event-driven processing in the prior art.

[0006] In a first aspect, the present application provides an event-driven processing method, comprising:

[0007] Obtain pending application service requirements;

[0008] Determining a business application based on the application service requirements to be processed;

[0009] According to the business application, query the business application interface in the preset business application container;

[0010] Determine the corresponding technical components based on the business application;

[0011] According to the technical component, query the technical component interface in the preset technical component container;

[0012] Configuring a framework launcher according to the business application interface and the technical component interface;

[0013] The business application is started through the framework launcher.

[0014] The event-driven framework of the present application first determines one or more corresponding business applications based on application service requirements, and based on the one or more business applications, queries the business application interface in the preset business application container, thereby realizing flexible assembly for different business applications. Before starting the business application, the technical component corresponding to the business application is combined to query the technical component interface in the preset technical component container, and then the business application can be started only according to the business application interface and the technical component interface, without loading all technical modules, thereby improving the efficiency of event-driven processing. Moreover, the present application can flexibly assemble business applications based on application service requirements. Compared with traditional applications based on existing event-driven frameworks, it can support on-demand combination of different business applications to form different application service nodes. The framework provides unified distributed capabilities based on the event-driven engine, and uses the same set of frameworks to realize event flow and driving of a single application service node or across nodes, thereby improving the flexibility of event-driven processing.

[0015] In one possible design, before querying a preset business application container for a business application interface according to the business application, the method further includes:

[0016] Get multiple business applications;

[0017] Performing interface abstraction processing on the multiple business applications to obtain multiple business application interfaces;

[0018] A preset business application container is created according to the multiple business application interfaces.

[0019] Here, this application abstracts the interface of the business application and implements a business application container that can load application instances. Application developers can implement functionally cohesive and reusable business applications based on the abstract interface defined by the framework. It can support different business applications to be combined on demand and loaded into the container to form different application service nodes. Through flexible configuration, it realizes the pluggability of business applications, and improves the flexibility and scalability of event-driven processing.

[0020] In one possible design, the business application includes multiple ones of a policy execution application, an order management application, an order execution application, and a risk management application.

[0021] Among them, the business applications of this application support strategy execution applications, order management applications, order execution applications or risk control applications, providing users with highly flexible and diverse business applications to meet the diverse business needs of the trading system.

[0022] In a possible design, before querying a preset technology component container for a technology component interface based on the technology component, the method further includes:

[0023] Acquisition of multiple technology components;

[0024] Performing interface abstraction processing on the multiple technical components to obtain multiple technical component interfaces;

[0025] A preset technology component container is created according to the multiple technology component interfaces.

[0026] Here, this application designs a technical component container for technical component abstraction. Application developers can load technical components into the container through configuration, and automatically assemble to generate a usable framework. Compared with the existing technology, each application based on the existing event-driven framework will load all technical modules when it starts. When starting the business application, this application only needs to configure the technical components according to the needs, realizing the pluggability of technical components, and then realizing the pluggability of application functions, further improving the flexibility of event-driven processing and improving the efficiency of event-driven processing.

[0027] In one possible design, the technical components include multiple ones of remote event publishing, remote event subscription, and event-driven engine.

[0028] Optionally, determining a corresponding technical component according to the business application includes:

[0029] Obtaining a component configuration file corresponding to the business application;

[0030] According to the component configuration file, the corresponding technical component is determined.

[0031] Among them, this application can automatically determine the corresponding technical components based on the component configuration file corresponding to the business application, without the need to load all technical components every time the business application is started. Through flexible configuration, event-driven can be quickly implemented, thereby improving the efficiency of event-driven processing.

[0032] In one possible design, obtaining the application service requirements to be processed includes:

[0033] Display the configuration interface of the event-driven framework;

[0034] Receive the application service requirements to be processed input by the user on the configuration interface of the event-driven framework.

[0035] Among them, this application provides a configuration interface of an event-driven framework that can be configured by users, visually displaying various configurations for users, facilitating users to flexibly implement the configuration of the event-driven framework, and improving user experience.

[0036] In a second aspect, the present application provides an event-driven processing device, comprising:

[0037] An acquisition module is used to obtain application service requirements to be processed;

[0038] A first determining module is used to determine a business application according to the application service requirement to be processed;

[0039] A first query module is used to query a business application interface in a preset business application container according to the business application;

[0040] A second determination module is used to determine a corresponding technical component according to the business application;

[0041] A second query module is used to query a technology component interface in a preset technology component container according to the technology component;

[0042] A configuration module, configured to configure a framework launcher according to the business application interface and the technical component interface;

[0043] The startup module is used to start the business application through the framework launcher.

[0044] In one possible design, before the first query module is used to query a preset business application container for a business application interface according to the business application, the apparatus further includes a first container module, which is used to:

[0045] Get multiple business applications;

[0046] Performing interface abstraction processing on the multiple business applications to obtain multiple business application interfaces;

[0047] A preset business application container is created according to the multiple business application interfaces.

[0048] In one possible design, the business application includes multiple ones of a policy execution application, an order management application, an order execution application, and a risk management application.

[0049] In one possible design, before the second query module is used to query a preset technology component container for a technology component interface based on the technology component, the apparatus further includes a second container module, which is used to:

[0050] Acquisition of multiple technology components;

[0051] Performing interface abstraction processing on the multiple technical components to obtain multiple technical component interfaces;

[0052] A preset technology component container is created according to the multiple technology component interfaces.

[0053] In one possible design, the technical components include multiple ones of remote event publishing, remote event subscription, and event-driven engine.

[0054] In one possible design, the second determining module is specifically configured to:

[0055] Obtaining a component configuration file corresponding to the business application;

[0056] According to the component configuration file, the corresponding technical component is determined.

[0057] In one possible design, the acquisition module is specifically configured to:

[0058] Display the configuration interface of the event-driven framework;

[0059] Receive the application service requirements to be processed input by the user on the configuration interface of the event-driven framework.

[0060] In a third aspect, the present application provides an event-driven processing device, comprising: at least one processor and a memory; the memory stores computer-executable instructions; the at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the event-driven processing method described in the first aspect and various possible designs of the first aspect.

[0061] In a fourth aspect, the present application provides a computer-readable storage medium, which stores computer-executable instructions. When a processor executes the computer-executable instructions, it implements the event-driven processing method described in the first aspect and various possible designs of the first aspect.

[0062] In a fifth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the event-driven processing method described in the first aspect and various possible designs of the first aspect.

[0063] The event-driven processing method, device, equipment, medium and product provided by the present application first determine the corresponding one or more business applications based on application service requirements, and based on the one or more business applications, query the business application interface in the preset business application container, thereby realizing flexible assembly for different business applications. Before starting the business application, the technical component corresponding to the business application is combined to query the technical component interface in the preset technical component container, and then the business application can be started only according to the business application interface and the technical component interface, without loading all technical modules, thereby improving the efficiency of event-driven processing. Moreover, the present application can flexibly assemble business applications based on application service requirements. Compared with traditional applications based on existing event-driven frameworks, it can support on-demand combination of different business applications to form different application service nodes. The framework provides unified distributed capabilities based on the event-driven engine, and uses the same set of frameworks to realize event flow and driving of a single application service node or across nodes, thereby improving the flexibility of event-driven processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0065] Figure 1 A schematic diagram of an event-driven processing system architecture provided in an embodiment of the present application;

[0066] Figure 2 A flowchart of an event-driven processing method provided in an embodiment of the present application;

[0067] Figure 3 A flowchart of another event-driven processing method provided in an embodiment of the present application;

[0068] Figure 4 A flowchart of another event-driven processing method provided in an embodiment of the present application;

[0069] Figure 5 A schematic diagram of the structure of an event-driven processing device provided in an embodiment of the present application;

[0070] Figure 6 A schematic diagram of the structure of an event-driven processing device provided in an embodiment of the present application.

[0071] The above drawings illustrate specific embodiments of the present application, which will be described in more detail below. These drawings and the textual description are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0072] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0073] In the technical solution of this application, the collection, storage, use, processing, transmission, provision and disclosure of information such as financial data or user data involved comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0074] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned. They should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0075] Automated trading systems are able to quickly identify trading opportunities and accurately execute trading orders in a rapidly changing market environment. Automated trading systems must make real-time trading decisions and execute trades based on market dynamics, such as price fluctuations and order fulfillment status. These constantly changing market information can be considered external events of varying types, and automated trading systems must respond to these events immediately. Therefore, event-driven frameworks are currently the mainstream implementation model for building automated trading systems. For example, when a stock's price breaks through a pre-set resistance level, the system can immediately capture this price event and generate trading instructions based on strategic rules.

[0076] Existing event-driven frameworks usually only include a basic event-driven engine, based on which application developers can define event types and corresponding processing logic. If they need to implement the sending and receiving of distributed events and drive event processing based on a distributed model, they need to independently develop or integrate other basic technical capabilities. Each application implemented based on an existing event-driven framework will load all technical modules when it starts. The above solutions have poor encapsulation and lack the basic capabilities of modularly designing event-driven frameworks. They are also less flexible, and existing solutions cannot achieve pluggable framework technology modules and application functions. Without unified distributed capabilities, a single framework cannot be used to implement event communication across physical nodes and drive business logic execution. Overall, existing event-driven processing technologies have poor flexibility.

[0077] In order to solve the above problems, an embodiment of the present application provides an event-driven processing method, device, equipment, medium and product, wherein the method abstractly designs a container for technical components and a container for business applications, which facilitates self-configuration of technical components and business applications, and realizes a flexible event-driven framework.

[0078] Optionally, the embodiment of the present application abstractly designs a container of a technical component (Bundle), and application developers can load dependent components into the container through configuration and assemble them to generate a usable framework by themselves;

[0079] Optionally, the embodiment of the present application abstractly designs a business application (APP) container. Application developers can implement functionally cohesive and reusable business applications based on the abstract interface defined by the framework, and can support different business applications to be combined on demand and loaded into the container to form different application service nodes.

[0080] Optionally, embodiments of the present application can support the flow of business events within a single application service node, as well as across nodes. Nodes can achieve efficient point-to-point direct communication, and business events can be automatically routed according to rules.

[0081] Optional, Figure 1 The present invention provides an event-driven processing system architecture diagram, the event-driven processing system can be a computer device. Figure 1 In the above architecture, the above architecture includes at least one of a data acquisition device 101, a processing device 102 and a display device 103.

[0082] It is understood that the structure illustrated in the embodiments of this application does not constitute a specific limitation on the event-driven processing system architecture. In other feasible implementations of this application, the above architecture may include more or fewer components than shown in the figure, or combine certain components, split certain components, or arrange components differently. The specific configuration can be determined based on the actual application scenario and is not limited here. Figure 1 The components shown can be implemented in hardware, software, or a combination of software and hardware.

[0083] In a specific implementation process, the data acquisition device 101 may include an input / output interface and may also include a communication interface. The data acquisition device 101 may be connected to the processing device via the input / output interface or the communication interface.

[0084] The processing device 102 may abstractly design a container for technical components and a container for business applications, so as to facilitate self-configuration of technical components and business applications and implement a flexible event-driven framework.

[0085] The display device 103 may also be a touch screen display or a screen of a terminal device, which is used to receive user instructions while displaying the above content to achieve interaction with the user.

[0086] It should be understood that the above-mentioned processing device can be implemented by a processor reading instructions in a memory and executing the instructions, or it can be implemented by a chip circuit.

[0087] In addition, the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0088] The technical solution of this application is described in detail below with reference to specific embodiments:

[0089] Optionally, Figure 2 A flow chart of an event-driven processing method provided in an embodiment of the present application. The execution subject of the embodiment of the present application can be Figure 1 The processing device 102 in the embodiment may be a computer device determined according to the actual application scenario. Figure 2 As shown, the method includes the following steps:

[0090] S201: Obtain application service requirements to be processed.

[0091] Optionally, the application service demand may be automatically triggered by an event-driven processing system during event processing.

[0092] Optionally, the application service requirements may be user input.

[0093] Optionally, the application service request may be sent by other terminal devices.

[0094] S202: Determine the business application according to the application service requirements to be processed.

[0095] Optionally, an application service requirement may include one or more business applications. The embodiment of the present application can realize the assembly of different business applications according to the application service requirement.

[0096] Optionally, the application service requirements include configuration information of the business application.

[0097] Specifically, the application service requirements also include configuration information of the technical components corresponding to each business application.

[0098] S203: According to the business application, query the business application interface in the preset business application container.

[0099] The preset business application container includes a plurality of business application interfaces obtained based on business application abstraction.

[0100] S204: Determine corresponding technical components based on business applications.

[0101] Optionally, the technical components here may be determined based on configuration information of the business applications and / or configuration information of the technical components corresponding to each business application.

[0102] Optionally, the embodiment of the present application can pre-configure corresponding technical components for each business application without user specification. The corresponding technical components can be directly determined according to the business application based on the pre-configured stored information.

[0103] Optionally, determining corresponding technical components according to business applications includes:

[0104] Obtain the component configuration file corresponding to the business application; determine the corresponding technical component based on the component configuration file.

[0105] Among them, the embodiment of the present application can automatically determine the corresponding technical components based on the component configuration file corresponding to the business application, without having to load all technical components every time the business application is started. Through flexible configuration, event-driven can be quickly implemented, thereby improving the efficiency of event-driven processing.

[0106] S205: According to the technical component, query the technical component interface in the preset technical component container.

[0107] The preset technical component container includes a plurality of technical component interfaces obtained based on technical component abstraction.

[0108] S206: Configure the framework launcher according to the business application interface and the technical component interface.

[0109] Optionally, if there are multiple business application interfaces, the framework launcher can implement the assembly of multiple different business applications.

[0110] S207: Start the business application through the framework launcher.

[0111] The event-driven framework of the embodiment of the present application first determines one or more corresponding business applications based on application service requirements, and based on the one or more business applications, queries the business application interface in the preset business application container, thereby realizing flexible assembly for different business applications. Before starting the business application, the technical component corresponding to the business application is combined to query the technical component interface in the preset technical component container, and then the business application can be started only according to the business application interface and the technical component interface, without loading all technical modules, thereby improving the efficiency of event-driven processing. Moreover, the embodiment of the present application can flexibly assemble business applications based on application service requirements. Compared with traditional applications implemented based on existing event-driven frameworks, it can support on-demand combination of different business applications to form different application service nodes. The framework provides unified distributed capabilities based on the event-driven engine, and uses the same set of frameworks to realize event flow and driving of a single application service node or across nodes, thereby improving the flexibility of event-driven processing.

[0112] Optionally, in order to achieve flexible configuration of the event-driven framework, the embodiment of the present application pre-abstracts the technical components and the containers of the business applications. Figure 3 A flow chart of another event-driven processing method provided in an embodiment of the present application is shown as follows: Figure 3 As shown, the method includes:

[0113] S301: Obtain application service requirements to be processed.

[0114] S302: Determine the business application according to the application service requirements to be processed.

[0115] The implementation of steps S301 and S302 is the same as that of steps S201 and S202, and will not be described in detail here.

[0116] S303: Acquire multiple business applications.

[0117] In one possible design, the business application includes multiple of a policy execution application, an order management application, an order execution application, and a risk management application.

[0118] Optionally, the business applications in the event-driven processing system or automated trading system can be directly obtained, and the applications requiring abstract interfaces can be determined based on their configuration information, type information, or triggering events.

[0119] Optionally, multiple business applications may be acquired based on user input.

[0120] Optionally, multiple business applications may be acquired based on historical events.

[0121] Among them, the business applications of the embodiments of the present application support policy execution applications, order management applications, order execution applications or risk control applications, providing users with highly flexible and diverse business applications to meet the diverse business needs of the trading system.

[0122] S304: Perform interface abstraction processing on multiple business applications to obtain multiple business application interfaces.

[0123] S305: Creating a preset business application container according to the multiple business application interfaces.

[0124] In a possible implementation, in this step, a business application container is defined: abstract business application interfaces, such as application initialization, loading, unloading, and startup; and a container that can load application instances is implemented, that is, the element type in the container is a business application.

[0125] Here, the embodiment of the present application abstracts the interface of the business application and implements a business application container that can load application instances. Application developers can implement functionally cohesive and reusable business applications based on the abstract interface defined by the framework. It can support different business applications to be combined on demand and loaded into the container to form different application service nodes. Through flexible configuration, the business application is pluggable, which improves the flexibility and scalability of event-driven processing.

[0126] S306: According to the business application, query the business application interface in the preset business application container.

[0127] S307: Determine corresponding technical components based on business applications.

[0128] S308: Acquire multiple technical components.

[0129] In one possible design, the technical components include multiple ones of remote event publishing, remote event subscription, and an event-driven engine.

[0130] Optionally, technical components corresponding to business applications within an event-driven processing system or an automated trading system are directly obtained.

[0131] Optionally, multiple technical components may be acquired based on user input.

[0132] Optionally, multiple business applications may be obtained based on historical events, and then technical components called by the business applications may be obtained.

[0133] S309: Perform interface abstraction processing on the multiple technical components to obtain multiple technical component interfaces.

[0134] S3010: Create a preset technical component container based on multiple technical component interfaces.

[0135] In a possible implementation, in this step, the technical component and the container are defined: the interface of the abstract technical component is defined, such as initialization, loading, unloading, starting of the component, and the like; based on the interface, the functions of the basic components, such as the remote event publishing, the remote event subscription, and the event-driven engine, are implemented; and a container that can load a component instance is implemented, that is, the element type in the container is the technical component.

[0136] Here, the technical component container is designed for the technical component abstraction in the embodiment of the application, and the application developer can load the technical component into the container through a configuration manner, and automatically assemble to generate a usable framework. Compared with the prior art in which each application based on an existing event-driven framework loads all technical modules at startup, the embodiment of the application only needs to configure the technical component according to the requirement at the startup of the business application, realizes the pluggable technical component, and further realizes the pluggable application function, further improves the flexibility of the event-driven processing, and improves the efficiency of the event-driven processing.

[0137] S3011: According to the technical component, a technical component interface is queried in a preset technical component container.

[0138] S3012: According to the business application interface and the technical component interface, a framework starter is configured.

[0139] S3013: The business application is started through the framework starter.

[0140] In the embodiment of the application, the business application can be implemented based on the business application interface, for example, a business function such as a policy execution application, an order management application, an order execution application, and a risk control application. Then, the application is assembled and started, different business applications are assembled according to the requirement of different application services, and the application is started through the framework starter.

[0141] The embodiment of the application encapsulates the basic technical capability of the framework through the abstract module design, and realizes the pluggable technical module of the framework and the pluggable application function through the flexible configuration manner. Meanwhile, the framework provides unified distributed capability based on the event-driven engine, and realizes the event flow transfer and driving of a single application service node or across nodes by using the same set of frameworks. On the basis of improving the flexibility and expansibility of the system, the development difficulty of the automated transaction application system is also greatly reduced.

[0142] Optionally, the embodiment of the application can provide a visual operation interface, and accordingly, Figure 4 Another flowchart of an event-driven processing method provided by the embodiment of the application is shown in FIG. 4. Figure 4 The method comprises the following steps.

[0143] S401: A configuration interface of an event-driven framework is displayed.

[0144] S402: receiving an application service requirement to be processed input by a user on a configuration interface of an event-driven framework.

[0145] It can be understood that the specific form of the configuration interface is not limited in the embodiments of the present application.

[0146] The user can input the application service requirement to be processed by clicking, selecting by pulling down or inputting.

[0147] S403: determining a business application according to the application service requirement to be processed.

[0148] S404: querying a business application interface in a preset business application container according to the business application.

[0149] S405: determining a corresponding technical component according to the business application.

[0150] S406: querying a technical component interface in a preset technical component container according to the technical component.

[0151] S407: configuring a framework launcher according to the business application interface and the technical component interface.

[0152] S408: starting the business application through the framework launcher.

[0153] The implementation manners of steps S403-S408 are the same as those of steps S202-S207, and thus are not described herein.

[0154] The embodiments of the present application provide a configuration interface of an event-driven framework that can be configured by a user, visually show the user various configurations, facilitate the user to flexibly configure the event-driven framework, and improve user experience.

[0155] Figure 5 A structural schematic diagram of an event-driven processing device provided by the embodiments of the present application is shown in FIG. 5. Figure 5 As shown in FIG. 5, the device provided by the embodiments of the present application includes an acquisition module 501, a first determination module 502, a first query module 503, a second determination module 504, a second query module 505, a configuration module 506 and a starting module 507. The event-driven processing device herein can be the event-driven processing system itself, or a chip or integrated circuit that implements the function of the processing device in the event-driven processing system. It should be noted that the division of the acquisition module 501, the first determination module 502, the first query module 503, the second determination module 504, the second query module 505, the configuration module 506 and the starting module 507 is only a logical division, and physically, they can be integrated or independent.

[0156] The acquisition module is used to obtain the application service requirements to be processed;

[0157] A first determination module is used to determine a business application based on the application service requirements to be processed;

[0158] A first query module is used to query a business application interface in a preset business application container according to the business application;

[0159] A second determination module is used to determine corresponding technical components according to business applications;

[0160] The second query module is used to query the technology component interface in the preset technology component container according to the technology component;

[0161] Configuration module, used to configure the framework launcher according to the business application interface and technical component interface;

[0162] The startup module is used to start business applications through the framework launcher.

[0163] In one possible design, before the first query module is configured to query a preset business application container for a business application interface based on the business application, the apparatus further includes a first container module configured to:

[0164] Get multiple business applications;

[0165] Perform interface abstraction processing on multiple business applications to obtain multiple business application interfaces;

[0166] Create a preset business application container based on multiple business application interfaces.

[0167] In one possible design, the business application includes multiple of a policy execution application, an order management application, an order execution application, and a risk management application.

[0168] In one possible design, before the second query module is used to query a preset technical component container for a technical component interface based on the technical component, the apparatus further includes a second container module, which is used to:

[0169] Acquisition of multiple technology components;

[0170] Perform interface abstraction processing on multiple technical components to obtain multiple technical component interfaces;

[0171] Create a preset technology component container based on multiple technology component interfaces.

[0172] In one possible design, the technical components include multiple ones of remote event publishing, remote event subscription, and an event-driven engine.

[0173] In a possible design, the second determining module is specifically configured to:

[0174] obtain a component configuration file corresponding to the service application;

[0175] determine a corresponding technical component according to the component configuration file.

[0176] In a possible design, the obtaining module is specifically configured to:

[0177] display a configuration interface of the event-driven framework;

[0178] receive an application service requirement to be processed input by a user on the configuration interface of the event-driven framework.

[0179] Reference Figure 6 , which shows a structural schematic diagram of an event-driven processing device suitable for being used to implement embodiments of the present disclosure, and the event-driven processing device can be a terminal device or a server. The terminal device can include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a Personal Digital Assistant (PDA), a Portable Android Device (PAD), a Portable Media Player (PMP), a vehicle-mounted terminal (for example, a vehicle-mounted navigation terminal), and the like, and a fixed terminal such as a digital TV, a desktop computer, and the like. Figure 6 The event-driven processing device shown is merely an example, and should not bring any limitation to the functions and use range of the embodiments of the present disclosure.

[0180] As shown in Figure 6 , the event-driven processing device can include a processing apparatus (for example, a central processor, a graphics processor, and the like) 601, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage apparatus 608 to a Random Access Memory (RAM) 603. In the RAM 603, various programs and data required by the event-driven processing device for operation are also stored. The processing apparatus 601, the ROM 602, and the RAM 603 are connected to each other through a bus 604. An Input / Output (I / O) interface 605 is also connected to the bus 604.

[0181] Typically, the following devices may be connected to the I / O interface 605: an input device 606 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 607 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 608 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 609. The communication device 609 may allow the event-driven processing device to communicate with other devices wirelessly or by wire to exchange data. Although Figure 6 The event-driven processing device having various devices is shown, but it should be understood that it is not required to implement or have all of the devices shown. More or fewer devices may be implemented or have alternatively.

[0182] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network via the communication device 609, or installed from the storage device 608, or installed from the ROM 602. When the computer program is executed by the processing device 601, the above-mentioned functions defined in the method of the embodiment of the present disclosure are performed.

[0183] It is noted that the aforementioned computer-readable medium of the present disclosure can be a computer-readable signal medium or a computer-readable storage medium or any combination thereof. The computer-readable storage medium can be, for example and without limitation, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer-readable storage medium can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, the computer-readable storage medium can be any tangible medium that contains or stores a program used by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, the computer-readable signal medium can include a computer-readable program code transmitted by a computer-readable storage medium or carried by a carrier wave in a baseband or as part of a carrier wave. Such a propagated computer-readable signal medium can take many forms, including but not limited to, electro-magnetic, optical, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium that can be used to carry or store computer-readable program code except the computer-readable storage media that can be specifically excluded in the present disclosure. The computer-readable medium can transmit, propagate or transport, for example, the program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained in the computer-readable medium can be transmitted by any suitable medium, including but not limited to, wire, cable, RF (radio frequency), etc., or any suitable combination of the foregoing.

[0184] The aforementioned computer-readable medium can be contained in the aforementioned event-driven processing device, or can exist separately without being assembled into the event-driven processing device.

[0185] The aforementioned computer-readable medium carries one or more programs, which, when executed by the event-driven processing device, cause the event-driven processing device to perform the method shown in the aforementioned embodiments.

[0186] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0187] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the module, program segment, or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of the boxes in the block diagram and / or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0188] The units involved in the embodiments described in this disclosure may be implemented in software or hardware. In some cases, the name of a unit does not limit the unit itself. For example, the first acquisition unit may also be described as a "unit for acquiring at least two Internet Protocol addresses."

[0189] The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, and without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chip (SOCs), complex programmable logic devices (CPLDs), and the like.

[0190] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, device or equipment. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0191] The event-driven processing device of the embodiment of the present application can be used to execute the technical solutions in the above-mentioned method embodiments of the present application. Its implementation principles and technical effects are similar and will not be repeated here.

[0192] An embodiment of the present application further provides a computer-readable storage medium, which stores computer-executable instructions. When the computer-executable instructions are executed by a processor, they are used to implement any of the above-mentioned event-driven processing methods.

[0193] An embodiment of the present application further provides a computer program product, including a computer program, which, when executed by a processor, is used to implement any of the above-mentioned event-driven processing methods.

[0194] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of modules is only a logical function division. In actual implementation, there may be other division methods, such as multiple modules can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or module, which can be electrical, mechanical or other forms.

[0195] Modules described as separate components may or may not be physically separate, and components shown as modules may or may not be physical units, that is, they may be located in one place or distributed across multiple network elements. Some or all of these modules may be selected to implement the solution of this embodiment based on actual needs.

[0196] In addition, the functional modules in the various embodiments of the present application may be integrated into a single processing unit, or each module may exist physically separately, or two or more modules may be integrated into a single unit. The above-mentioned modules may be implemented in the form of hardware or hardware plus software functional units.

[0197] The above-mentioned integrated module implemented in the form of a software functional module can be stored in a computer-readable storage medium. The above-mentioned software functional module is stored in a storage medium and includes a number of instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) or a processor to perform some steps of the methods of various embodiments of the present application.

[0198] It should be understood that the processor may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the present invention may be directly implemented by a hardware processor or implemented by a combination of hardware and software modules in the processor.

[0199] The memory may include a high-speed RAM memory, and may also include non-volatile storage NVM, such as at least one disk memory, and may also be a USB flash drive, a mobile hard disk, a read-only memory, a magnetic disk or an optical disk.

[0200] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. Buses can be categorized as address buses, data buses, and control buses. For ease of illustration, the buses in the drawings of this application are not limited to just one bus or just one type of bus.

[0201] The storage medium may be implemented by any type of volatile or non-volatile memory device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0202] An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the storage medium can also exist as discrete components in an electronic control unit or a main control device.

[0203] Those skilled in the art will appreciate that all or part of the steps in the above-described method embodiments can be implemented using hardware associated with program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0204] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some or all of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. An event-driven processing method, characterized in that: include: Obtain pending application service requirements; Determining a business application based on the application service requirements to be processed; According to the business application, query the business application interface in the preset business application container; Determine the corresponding technical components based on the business application; According to the technical component, query the technical component interface in the preset technical component container; Configuring a framework launcher according to the business application interface and the technical component interface; The business application is started through the framework launcher.

2. The method according to claim 1, characterized in that Before searching for a business application interface in a preset business application container according to the business application, the method further includes: Get multiple business applications; Performing interface abstraction processing on the multiple business applications to obtain multiple business application interfaces; A preset business application container is created according to the multiple business application interfaces.

3. The method according to claim 2, characterized in that The business applications include multiple ones of a policy execution application, an order management application, an order execution application, and a risk management and control application.

4. The method according to any one of claims 1 to 3, characterized in that Before searching for a technology component interface in a preset technology component container according to the technology component, the method further includes: Acquisition of multiple technology components; Performing interface abstraction processing on the multiple technical components to obtain multiple technical component interfaces; A preset technology component container is created according to the multiple technology component interfaces.

5. The method according to claim 4, characterized in that The technical components include multiple ones of remote event publishing, remote event subscription and event-driven engine.

6. The method according to any one of claims 1 to 3, characterized in that Determining corresponding technical components according to the business application includes: Obtaining a component configuration file corresponding to the business application; According to the component configuration file, the corresponding technical component is determined.

7. The method according to any one of claims 1 to 3, characterized in that The obtaining of the pending application service requirements includes: Display the configuration interface of the event-driven framework; Receive the application service requirements to be processed input by the user on the configuration interface of the event-driven framework.

8. An event-driven processing device, characterized in that: include: An acquisition module is used to obtain application service requirements to be processed; A first determining module is used to determine a business application according to the application service requirement to be processed; A first query module is used to query a business application interface in a preset business application container according to the business application; A second determination module is used to determine a corresponding technical component according to the business application; A second query module is used to query a technology component interface in a preset technology component container according to the technology component; A configuration module, configured to configure a framework launcher according to the business application interface and the technical component interface; The startup module is used to start the business application through the framework launcher.

9. An event-driven processing device, characterized in that include: a processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 7.

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

11. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 7 when being executed by a processor.

Images