CN112579156A - Processing system, processing method, processing device and processing equipment of business event - Google Patents
Processing system, processing method, processing device and processing equipment of business eventDownload PDFInfo
- Publication number
- CN112579156A CN112579156ACN202011459550.1ACN202011459550ACN112579156ACN 112579156 ACN112579156 ACN 112579156ACN 202011459550 ACN202011459550 ACN 202011459550ACN 112579156 ACN112579156 ACN 112579156A
- Authority
- CN
- China
- Prior art keywords
- business
- event
- code
- execution
- component
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/76—Adapting program code to run in a different environment; Porting
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
Translated fromChinese
Description
Translated fromChinese技术领域technical field
本发明实施例涉及数据处理技术领域，尤其涉及一种业务事件的处理系统以及处理方法、装置和设备。Embodiments of the present invention relate to the technical field of data processing, and in particular, to a business event processing system, and a processing method, apparatus, and device.
背景技术Background technique
在互联网领域内针对不同业务类型已经开发有大量应用程序，每一应用程序在执行相应的核心业务操作时，该核心业务下会扩展出大量支持该核心业务准确执行的旁路逻辑，此时该应用程序在核心业务的处理过程中，通常也需要处理各个旁路逻辑下指定的业务事件，以确保核心业务的执行准确性。A large number of application programs have been developed for different business types in the Internet field. When each application program performs the corresponding core business operation, a large number of bypass logics that support the accurate execution of the core business will be expanded under the core business. During the processing of the core business, the application usually also needs to process the business events specified under each bypass logic to ensure the execution accuracy of the core business.
目前，在核心业务的处理过程中，应用程序对于各个旁路逻辑下指定的业务事件，存在如下三种处理方式：At present, in the process of core business processing, the application has the following three processing methods for the business events specified under each bypass logic:
1)基于核心业务代码的开发语言，在核心业务代码中编写旁路逻辑下业务事件的处理代码，并重启修改后的核心业务代码，此时将旁路逻辑嵌入到核心业务中，容易造成核心业务代码泄露，使得核心业务执行时存在一定的稳定性风险。1) Based on the development language of the core business code, write the processing code of the business event under the bypass logic in the core business code, and restart the modified core business code. At this time, the bypass logic is embedded in the core business, which is easy to cause the core business. The leakage of business code makes certain stability risks exist in the execution of core business.
2)基于Lua或者其他脚本语言作为旁路逻辑下业务事件的代码语言，但是需要将脚本语言转换成核心业务的语言，从而限制了脚本的开发语言，而且由于应用程序通常不支持除原生语言外的其他脚本语言的运行，使得脚本代码的可移植性较差。2) Based on Lua or other scripting languages as the code language for business events under the bypass logic, but the scripting language needs to be converted into the language of the core business, which limits the development language of scripts, and because applications usually do not support languages other than native languages The operation of other scripting languages makes the script code less portable.
3)将核心业务处理过程中触发的各个旁路逻辑下的业务事件，按照消息的形式异步发送到Kafka消息中间件中，然后通过消息消费进程不断处理Kafka消息中间件内的各个业务事件，能够实现业务事件执行与核心业务处理的解耦，但是仅支持异步处理方式，无法同步向核心业务返回各个业务事件的处理结果，从而影响核心业务的执行效率。3) The business events under each bypass logic triggered in the core business processing process are asynchronously sent to the Kafka message middleware in the form of messages, and then the various business events in the Kafka message middleware are continuously processed through the message consumption process. Realize the decoupling of business event execution and core business processing, but only supports asynchronous processing, and cannot synchronously return the processing results of each business event to the core business, thus affecting the execution efficiency of the core business.
发明内容SUMMARY OF THE INVENTION
本发明实施例提供了一种业务事件的处理系统以及处理方法、装置和设备，实现业务事件的多语音编译和多方式执行，保证业务事件的执行可移植性和可扩展性，提高目标应用运行的安全性和高效性。The embodiments of the present invention provide a business event processing system and a processing method, device and equipment, which can realize multi-voice compilation and multi-mode execution of business events, ensure the portability and scalability of the execution of business events, and improve the operation of target applications. safety and efficiency.
第一方面，本发明实施例提供了一种业务事件的处理系统，该系统包括：事件管理组件、代码绑定组件和事件执行组件，所述事件管理组件内注册有目标应用运行时的各业务事件；其中，In a first aspect, an embodiment of the present invention provides a system for processing business events. The system includes: an event management component, a code binding component, and an event execution component. The event management component is registered with various services of the target application runtime. event; of which,
所述代码绑定组件面向所述事件管理组件内已注册的每一业务事件，在每一许可执行方式下分别绑定支持多语言编译转换的中间业务代码；The code binding component faces each business event registered in the event management component, and binds the intermediate business code supporting multi-language compilation and conversion under each license execution mode;
所述事件执行组件如果在所述目标应用运行时接收到目标业务事件的触发消息，则采用每一许可执行方式对应执行所述目标业务事件在该许可执行方式下绑定的中间业务代码。If the event execution component receives the trigger message of the target business event when the target application is running, it adopts each permission execution mode to execute the intermediate service code bound to the target business event in the permission execution mode.
第二方面，本发明实施例提供了一种业务事件的处理方法，应用于上述第一方面所述的业务事件的处理系统中，该方法包括如下非顺序执行的步骤：In a second aspect, an embodiment of the present invention provides a business event processing method, which is applied to the business event processing system described in the first aspect above. The method includes the following non-sequentially executed steps:
通过代码绑定组件面向事件管理组件内已注册的每一业务事件，在每一许可执行方式下分别绑定支持多语言编译转换的中间业务代码；Facing each business event registered in the event management component through the code binding component, bind the intermediate business code supporting multi-language compilation and conversion under each license execution mode;
如果在目标应用运行时通过事件执行组件接收到目标业务事件的触发消息，则通过所述事件执行组件采用所述目标业务事件注册时的每一许可执行方式，对应执行所述目标业务事件在该许可执行方式下绑定的中间业务代码；If the trigger message of the target business event is received through the event execution component when the target application is running, the event execution component adopts each permission execution mode when the target business event is registered, and executes the target business event in the corresponding execution mode of the target business event. The intermediate business code bound in the license execution mode;
其中，所述事件管理组件内注册有目标应用运行时的各业务事件。Wherein, each business event of the target application running time is registered in the event management component.
第三方面，本发明实施例提供了一种业务事件的处理装置，配置于上述第一方面所述的业务事件的处理系统中，该装置包括：In a third aspect, an embodiment of the present invention provides a service event processing apparatus, which is configured in the service event processing system described in the first aspect above, and the apparatus includes:
代码绑定模块，用于通过代码绑定组件面向事件管理组件内已注册的每一业务事件，在每一许可执行方式下分别绑定支持多语言编译转换的中间业务代码；The code binding module is used to face each business event registered in the event management component through the code binding component, and bind the intermediate business code supporting multi-language compilation and conversion under each license execution mode;
业务代码执行模块，用于如果在目标应用运行时通过事件执行组件接收到目标业务事件的触发消息，则通过所述事件执行组件采用所述目标业务事件注册时的每一许可执行方式，对应执行所述目标业务事件在该许可执行方式下绑定的中间业务代码；The business code execution module is used for, if the trigger message of the target business event is received through the event execution component when the target application is running, the event execution component adopts each permission execution mode when the target business event is registered, and executes the corresponding execution the intermediate business code bound to the target business event under the permission execution mode;
其中，所述事件管理组件内注册有目标应用运行时的各业务事件。Wherein, each business event of the target application running time is registered in the event management component.
第四方面，本发明实施例提供了一种计算机设备，该计算机设备包括：In a fourth aspect, an embodiment of the present invention provides a computer device, the computer device comprising:
一个或多个处理器；one or more processors;
存储装置，用于存储一个或多个程序；a storage device for storing one or more programs;
当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现本发明任意实施例所述的业务事件的处理方法。When the one or more programs are executed by the one or more processors, the one or more processors implement the method for processing a business event according to any embodiment of the present invention.
第五方面，本发明实施例提供了一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现本发明任意实施例所述的业务事件的处理方法。In a fifth aspect, an embodiment of the present invention provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, implements the business event processing method described in any embodiment of the present invention.
本发明实施例提供的一种业务事件的处理系统以及处理方法、装置和设备，在事件管理组件内注册目标应用运行时存在的各个业务事件，通过代码绑定组件面向事件管理组件内已注册的每一业务事件，在每一许可执行方式下分别绑定支持多语言编译转换的中间业务代码，使得业务事件执行与目标应用运行之间能够资源隔离，从而实现业务事件的多语音编译和多方式执行，保证业务事件的执行可移植性和可扩展性；同时，如果在目标应用运行时通过事件执行组件接收到目标业务事件的触发消息，则采用目标业务事件的每一许可执行方式对应执行目标业务事件在该许可执行方式下绑定的中间业务代码，避免对目标应用运行产生影响，从而提高目标应用运行的安全性和高效性。The embodiment of the present invention provides a business event processing system, processing method, device and device. Each business event that exists when a target application is running is registered in an event management component, and a code binding component is used to face registered events in the event management component. Each business event is bound to the intermediate business code that supports multi-language compilation and conversion under each license execution mode, so that resources can be isolated between the execution of the business event and the running of the target application, thereby realizing multi-voice compilation and multi-mode business events. Execute to ensure the execution portability and scalability of the business event; at the same time, if the trigger message of the target business event is received through the event execution component when the target application is running, each permission execution mode of the target business event is used to correspond to the execution target. The intermediate business code bound by the business event in this permission execution mode avoids affecting the running of the target application, thereby improving the security and efficiency of the running of the target application.
附图说明Description of drawings
通过阅读参照以下附图所作的对非限制性实施例所作的详细描述，本发明的其它特征、目的和优点将会变得更明显：Other features, objects and advantages of the present invention will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings:
图1为本发明实施例一提供的一种业务事件的处理系统的原理架构图；FIG. 1 is a schematic structural diagram of a system for processing business events according to
图2为本发明实施例二提供的一种业务事件的处理系统的结构示意图；FIG. 2 is a schematic structural diagram of a service event processing system according to
图3为本发明实施例三提供的一种业务事件的处理系统的结构示意图；FIG. 3 is a schematic structural diagram of a service event processing system according to Embodiment 3 of the present invention;
图4为本发明实施例四提供的一种业务事件的处理方法的流程图；4 is a flowchart of a method for processing a business event according to Embodiment 4 of the present invention;
图5为本发明实施例五提供的一种业务事件的处理方法的流程图；5 is a flowchart of a method for processing a business event according to Embodiment 5 of the present invention;
图6为本发明实施例六提供的一种业务事件的处理装置的结构示意图；6 is a schematic structural diagram of an apparatus for processing a service event according to Embodiment 6 of the present invention;
图7为本发明实施例七提供的一种计算机设备的结构示意图。FIG. 7 is a schematic structural diagram of a computer device according to Embodiment 7 of the present invention.
具体实施方式Detailed ways
下面结合附图和实施例对本发明作进一步的详细说明。可以理解的是，此处所描述的具体实施例仅仅用于解释本发明，而非对本发明的限定。另外还需要说明的是，为了便于描述，附图中仅示出了与本发明相关的部分而非全部结构。此外，在不冲突的情况下，本发明中的实施例及实施例中的特征可以相互组合。The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention, but not to limit the present invention. In addition, it should be noted that, for the convenience of description, the drawings only show some but not all structures related to the present invention. Furthermore, the embodiments of the invention and the features of the embodiments may be combined with each other without conflict.
由于各个业务应用在执行相应的核心业务操作时，该核心业务下会扩展出大量辅助该核心业务准确执行的旁路逻辑，因此为了确保核心业务的执行准确性，在该业务应用运行过程中，通常需要处理各个旁路逻辑下指定的业务事件；此时，本发明实施例会在任一业务应用中针对所存在的各个旁路逻辑指定的业务事件，专门设计一种新的事件处理系统，并内嵌到该业务应用中，用于在该业务应用的运行过程中，执行和管理与每一业务事件绑定的业务代码。此时，为了解决开发语言的包容性以及可移植性的问题，本发明实施例可以选用抽象描述代码执行环境的中间字节码技术(WebAssembly，WASM)来解决；WASM代码是一种抹平了不同架构的机器码，支持多种语言(如AssemblyScript、C\C++，Rust、Golang和Python等)下的编译代码能够转换为WASM代码。因此，本发明实施例可以基于WASM中间字节码，构建一个支持同步和异步的事件处理系统，并内嵌入业务应用中，以实现业务事件的多语音编译和多方式执行，保证业务事件的执行可移植性和可扩展性，并提高业务应用运行的安全性和高效性。Since each business application executes the corresponding core business operation, a large number of bypass logics will be expanded under the core business to assist the accurate execution of the core business. Therefore, in order to ensure the execution accuracy of the core business, during the operation of the business application, Usually, it is necessary to process the business events specified under each bypass logic; at this time, the embodiment of the present invention will specifically design a new event processing system for the business events specified by each bypass logic existing in any business application, and integrate the internal It is embedded in the business application and used to execute and manage the business code bound to each business event during the running process of the business application. At this time, in order to solve the problems of inclusiveness and portability of the development language, the embodiment of the present invention can use an intermediate bytecode technology (WebAssembly, WASM) that abstractly describes the code execution environment to solve; WASM code is a kind of smoothing Machine codes of different architectures, and compiled codes that support multiple languages (such as AssemblyScript, C\C++, Rust, Golang, and Python, etc.) can be converted into WASM codes. Therefore, the embodiment of the present invention can build an event processing system supporting synchronous and asynchronous based on the WASM intermediate bytecode, and embed it into a business application, so as to realize multi-voice compilation and multi-mode execution of business events, and ensure the execution of business events. Portability and scalability, and improve the security and efficiency of business application operation.
实施例一Example 1
图1为本发明实施例一提供的一种业务事件的处理系统的原理架构图。本实施例可适用于在任一种业务应用内运行核心业务时，对核心业务扩展出的各个旁路逻辑下指定的业务事件进行处理的情况中。具体的，参照图1，该业务事件的处理系统10可以包括：事件管理组件110、代码绑定组件120和事件执行组件130。FIG. 1 is a schematic structural diagram of a system for processing business events according to
其中，事件管理组件110内注册有目标应用运行时的各业务事件；具体的，代码绑定组件120面向事件管理组件110内已注册的每一业务事件，在每一许可执行方式下分别绑定支持多语言编译转换的中间业务代码；事件执行组件130如果在目标应用运行时接收到目标业务事件的触发消息，则采用每一许可执行方式对应执行目标业务事件在该许可执行方式下绑定的中间业务代码。Among them, the
可选的，本实施例中的目标应用可以为任一互联网业务类型下所开发出的能够安装于客户端上的业务应用程序，在该目标应用上执行主要的核心业务操作时，会扩展出大量用于辅助核心业务准确执行的旁路逻辑，此时为了确保目标应用内核心业务的运行准确性，本实施例还需要对各个旁路逻辑下产生的业务事件进行处理。此时，为了避免旁路逻辑下业务实践的处理，对核心业务运行造成负向影响，本实施例需要对核心业务与旁路逻辑下的业务事件进行隔离处理，使两者之间的处理过程互不影响，因此针对各个旁路逻辑下的业务事件的处理，会专门为每一业务事件重新编写相应处理功能的执行代码，以与核心业务的执行代码隔离开来，使得核心业务与旁路逻辑下的业务事件均能够独立执行，无需对核心业务的执行代码进行修改，从而保证目标应用内核心业务的运行安全性和稳定性。因此，本实施例针对目标应用内旁路逻辑下的业务事件，会专门设计一个事件处理装置，也就是本实施例中的业务事件的处理系统10，将该业务事件的处理系统10内嵌入目标应用中，用于在目标应用内的某一业务事件被触发时，能够通过运行为该业务事件重新编写的执行代码，来获取该业务事件的处理结果。Optionally, the target application in this embodiment may be a service application developed under any Internet service type that can be installed on the client. A large number of bypass logics are used to assist the accurate execution of the core business. In this case, in order to ensure the running accuracy of the core business in the target application, this embodiment also needs to process the business events generated under each bypass logic. At this time, in order to avoid the processing of business practices under the bypass logic, which has a negative impact on the operation of the core business, this embodiment needs to isolate the core business and the business events under the bypass logic, so that the processing between the two They do not affect each other, so for the processing of business events under each bypass logic, the execution code of the corresponding processing function will be specially rewritten for each business event to isolate it from the execution code of the core business, so that the core business and the bypass The business events under the logic can be executed independently without modifying the execution code of the core business, thus ensuring the operation security and stability of the core business in the target application. Therefore, in this embodiment, an event processing device is specially designed for the business event under the bypass logic in the target application, that is, the business
在本实施例中，为了准确了解目标应用运行时所产生的各个业务事件，会预先分析目标应用运行时，在核心业务下所扩展出的各个旁路逻辑，然后判断每一旁路逻辑下生成的业务事件，并将每一业务事件注册入事件管理组件110内，以便后续通过该事件管理组件110查看目标应用运行时核心业务扩展出的各个旁路逻辑下的业务事件，并针对每一业务事件的功能，专门编写对应的执行代码。此时，由于采用特定脚本语言编写各个业务事件的执行代码时，目标应用通常不支持除原生语言外的其他脚本语言的运行，使得采用特定脚本语言所编写的执行代码的可移植性较差，因此为了提高业务事件执行代码的可移植性，提高代码开发语言的包容性和开放性，本实施例会选用支持多语言编译转换的中间业务代码，来解决执行代码可移植性差的问题，本实施例中的中间业务代码可以为采用中间字节码技术(WebAssembly，WASM)为每一业务事件编写的WASM代码，支持多种语言(如AssemblyScript、C\C++、Rust、Golang或Python等)等编译的原始执行代码均能够转换成相应的WASM代码。In this embodiment, in order to accurately understand the various business events generated when the target application is running, each bypass logic extended under the core business during the running of the target application will be analyzed in advance, and then each bypass logic generated under each bypass logic will be judged. business events, and register each business event into the
具体的，开发人员通过事件管理组件110查看目标应用运行时核心业务扩展出的各个旁路逻辑下的业务事件，并分析出每一业务事件的事件功能后，会采用任一语言的专门为各个业务事件专门编写对应的原始执行代码，同时为了保证业务事件代码的可移植性，会将该原始执行代码转换成支持多语言编译转换的WASM语言下的中间业务代码，进而通过代码绑定组件120面向事件管理组件110内已注册的每一业务事件，分别绑定为该业务事件编写的各个中间业务代码，后续通过各个业务事件与中间业务代码之间的绑定关系，来查找表示每一业务事件功能的中间业务代码，并通过运行该中间业务代码来确保业务实践的准确处理。Specifically, the developer uses the
同时，由于每一业务事件下编写的各个中间业务代码所表示的事件功能可能存在关联，也可能不存在任何关联，因此每一业务事件下各个中间业务代码的执行方式也各不相同，通过分析每一业务事件具备的事件功能之间的联系，可以确定出每一业务事件下运行各个中间业务代码时允许采用的许可执行方式，同时在针对每一业务事件的各个事件功能，编写对应的中间业务代码时，也会定义出每一中间业务代码的实际执行方式，进而通过代码绑定组件120分析每一业务事件下编写的各个中间业务代码的实际执行方式，并按照该业务事件下每一中间业务代码的实际执行方式，将该中间业务代码绑定到该业务事件下执行方式相同的许可执行方式下，也就是在每一业务事件的每一许可执行方式下，均绑定有支持采用该许可执行方式来实际执行的中间业务代码。At the same time, because the event functions represented by each intermediate business code written under each business event may or may not have any correlation, the execution methods of each intermediate business code under each business event are also different. The connection between the event functions of each business event can determine the permission execution mode that is allowed when running each intermediate business code under each business event, and at the same time, for each event function of each business event, write the corresponding intermediate business code. When the business code is used, the actual execution mode of each intermediate business code is also defined, and then the actual execution mode of each intermediate business code written under each business event is analyzed through the
需要说明的是，本实施例中业务事件的许可执行方式可以包括同步执行方式和异步执行方式中的至少一种。此时，在业务事件的同步执行方式下，会绑定一部分中间业务代码，在该业务事件的异步执行方式下，也会绑定一部分中间业务代码，从而实现业务事件的多语音编译和多方式执行，保证业务事件的执行可移植性和可扩展性。It should be noted that, the permission execution manner of the service event in this embodiment may include at least one of a synchronous execution manner and an asynchronous execution manner. At this time, in the synchronous execution mode of the business event, a part of the intermediate business code will be bound, and in the asynchronous execution mode of the business event, a part of the intermediate business code will also be bound, so as to realize the multi-voice compilation and multi-mode of the business event. Execution ensures the portability and scalability of the execution of business events.
进一步的，在目标应用的运行过程中，会不断触发执行对应的业务事件，此时如果通过事件执行组件130接收到某一目标业务事件的触发消息，那么直接会通过代码绑定组件120查找出该目标业务事件在每一许可执行方式下分别绑定的各个中间业务代码，然后分别采用每一许可执行方式，对应执行目标业务事件在该许可执行方式下绑定的各个中间业务代码；例如，同步执行目标业务事件在同步执行方式下绑定的各个中间业务代码，异步执行目标业务事件在异步执行方式下绑定的各个中间业务代码。Further, during the running process of the target application, the corresponding business event will be continuously triggered and executed. At this time, if the trigger message of a target business event is received through the
示例性的，在同步执行目标业务事件在同步执行方式下绑定的各个中间业务代码时，可以按照在同步执行方式下各个中间业务代码的绑定顺序，依次运行在同步执行方式下绑定的每一中间业务代码；而在异步执行目标业务事件在异步执行方式下绑定的各个中间业务代码时，可以专门开启一个独立线程，采用该独立线程来运行在异步执行方式下绑定的各个中间业务代码。然后，将目标业务事件下绑定的每一中间业务代码的执行结果反馈给目标应用，以确保目标应用的准确运行。Exemplarily, when synchronously executing each intermediate business code bound by the target business event in the synchronous execution mode, the code bound in the synchronous execution mode may be sequentially executed according to the binding sequence of each intermediate business code in the synchronous execution mode. Each intermediate business code; when asynchronously executing each intermediate business code bound by the target business event in the asynchronous execution mode, an independent thread can be specially opened, and the independent thread can be used to run each intermediate business code bound in the asynchronous execution mode. Business code. Then, the execution result of each intermediate business code bound under the target business event is fed back to the target application, so as to ensure the accurate operation of the target application.
需要说明的是，本实施例中的代码绑定过程与代码执行过程属于业务事件处理的两个阶段，代码绑定过程会在本实施例中业务事件的处理系统10的开发阶段完成，在为目标应用内各个旁路逻辑下的业务事件均在每一许可执行方式下分别绑定有对应的中间业务代码后，可以将该业务事件的处理系统10内嵌到该目标应用中，并在该目标应用的运行过程中通过事件执行组件130实时接收各个业务事件的触发消息，从而在应用运行阶段执行目标业务事件的代码执行过程，以此实现目标应用内各个旁路逻辑下业务事件的准确处理，在保证目标应用内核心业务的运行准确性的基础上，进一步提高业务事件的执行可移植性和可扩展性，以及目标应用运行的安全性和高效性。It should be noted that the code binding process and the code execution process in this embodiment belong to two stages of business event processing, and the code binding process will be completed in the development stage of the business
本实施例提供的技术方案，在事件管理组件内注册目标应用运行时存在的各个业务事件，通过代码绑定组件面向事件管理组件内已注册的每一业务事件，在每一许可执行方式下分别绑定支持多语言编译转换的中间业务代码，使得业务事件执行与目标应用运行之间能够资源隔离，从而实现业务事件的多语音编译和多方式执行，保证业务事件的执行可移植性和可扩展性；同时，如果在目标应用运行时通过事件执行组件接收到目标业务事件的触发消息，则采用目标业务事件的每一许可执行方式对应执行目标业务事件在该许可执行方式下绑定的中间业务代码，避免对目标应用运行产生影响，从而提高目标应用运行的安全性和高效性。In the technical solution provided by this embodiment, each business event that exists when the target application is running is registered in the event management component, and each business event registered in the event management component is oriented to each business event registered in the event management component through the code binding component. Bind the intermediate business code that supports multi-language compilation and conversion, so that resources can be isolated between the execution of business events and the running of the target application, so as to realize multi-voice compilation and multi-mode execution of business events, and ensure the portability and scalability of the execution of business events. At the same time, if the trigger message of the target business event is received through the event execution component when the target application is running, each permission execution mode of the target business event is used to execute the intermediate services bound by the target business event under the permission execution mode. code to avoid affecting the running of the target application, thereby improving the security and efficiency of the running of the target application.
实施例二
图2为本发明实施例二提供的一种业务事件的处理系统的结构示意图。本实施例是在上述实施例提供的技术方案的基础上进行优化。参照图2，该业务事件的处理系统20可以包括事件管理组件210、代码绑定组件220和事件执行组件230。FIG. 2 is a schematic structural diagram of a system for processing a business event according to
其中，事件管理组件210内注册有目标应用运行时的各业务事件；具体的，代码绑定组件220面向事件管理组件210内已注册的每一业务事件，在每一许可执行方式下分别绑定支持多语言编译转换的中间业务代码；事件执行组件230如果在目标应用运行时接收到目标业务事件的触发消息，则采用每一许可执行方式对应执行目标业务事件在该许可执行方式下绑定的中间业务代码。Among them, the
需要说明的是，本实施例中的事件管理组件210、代码绑定组件220和事件执行组件230与上述实施例中的事件管理组件、代码绑定组件和事件执行组件具备相同的功能。It should be noted that the
具体的，为了保证目标应用内各个业务事件在开发阶段的准确注册以及在运行阶段的准确触发，本实施例中的事件管理组件210可以包括事件注册接口(Regist)211和事件触发接口(Trigger)212。Specifically, in order to ensure accurate registration of each business event in the target application in the development phase and accurate triggering in the running phase, the
其中，事件注册接口211采用事件标识和许可执行方式注册目标应用运行时的各业务事件；事件触发接口212按照事件标识和事件触发条件，实时检测各业务事件的触发状态，并向事件执行组件230发送目标业务事件的触发消息。Among them, the
可选的，事件注册接口211主要用于注册目标应用运行时所产生的各个业务事件，此时将业务事件的事件标识(如事件名称等)以及该业务事件下运行各个中间业务代码时所允许采用的许可执行方式作为该事件注册接口211的接口输入定义，以此通过事件注册接口211不断输入每一业务事件的注册信息，同时将该事件注册接口211的接口输出定义为注册成功或者注册失败及失败原因，从而保证业务事件的准确注册。Optionally, the
同时，事件触发接口212主要用于在目标应用运行阶段内实时检测是否存在被触发执行的目标业务事件，此时该事件触发接口212的接口输入定义为业务事件的事件标识、事件触发条件(例如JSON编码封装的当前事件触发的具体信息)以及目标业务事件下各个中间业务代码的执行结果的回调处理方法等，此时回调处理方法的输入可以为目标业务事件在JSON解码封装下的处理结果，通过该事件触发接口212实时检测接口输入信息来判断各业务事件的触发状态，并将该事件触发接口212的接口输出定义为无，从而准确检测目标应用运行过程中各业务事件的触发状态，并在检测到目标业务事件被触发时，向事件执行组件230发送该目标业务事件的触发消息，以通过该事件执行组件230执行该目标业务事件下绑定的各个中间业务代码。At the same time, the
此外，对于每一业务事件与中间业务代码的绑定而言，主要是接收预先为每一业务事件所编写的中间业务代码，确定该中间业务代码的实际执行方式，并将业务事件与中间业务代码对应关联起来，以便后续能够准确查找出为每一业务事件编写的中间业务代码，因此为了保证业务事件与中间业务代码之间的绑定关系准确性，本实施例中的代码绑定组件220可以包括绑定接口(Bind)221、绑定移除接口(Remove)222和代码升级接口(Upgrade)223。In addition, for the binding of each business event and the intermediate business code, it is mainly to receive the intermediate business code written for each business event in advance, determine the actual execution mode of the intermediate business code, and associate the business event with the intermediate business code. The codes are correspondingly associated, so that the intermediate business code written for each business event can be accurately found in the future. Therefore, in order to ensure the accuracy of the binding relationship between the business event and the intermediate business code, the
其中，绑定接口221按照事件标识、代码标识、实际执行方式和代码字节流，为每一业务事件，在各许可执行方式下分别绑定对应的中间业务代码；绑定移除接口222按照事件标识、代码标识和实际执行方式，移除各业务事件在对应许可执行方式下已绑定的中间业务代码；代码升级接口223按照代码标识和代码升级字节流，更新各业务事件已绑定的中间业务代码。Among them, the binding
具体的，绑定接口221主要用于接收为每一业务事件编写的各个中间业务代码，以及该中间业务代码指向的业务事件，此时可以将绑定接口221的接口输入定义为待绑定业务事件的事件标识、所录入中间业务代码的代码标识、中间业务代码的实际执行方式以及该中间业务代码的代码字节流等，该代码字节流可以为WASM代码的二进制字节流；此时，按照上述接口输入信息可以在每一业务事件的各个许可执行方式下不断绑定各个中间业务代码，并且在绑定接口221的接口输入中还可以输入中间业务代码所依赖的扩展方法名称，以便后续在目标应用内创建对应的虚拟环境时，能够装载各个中间业务代码对应的扩展方法，从而保证中间业务代码的执行高效性。同时，该绑定接口221的接口输出定义为绑定成功或者绑定失败及失败原因，从而保证业务事件与中间业务代码之间的准确绑定。Specifically, the binding
此外，为了支持各个业务事件所绑定的中间业务代码的有效更新，本实施例会通过绑定移除接口222来删除某些失效的绑定关系，此时该绑定移除接口222的接口输入定义为业务事件的事件标识、所绑定的中间业务代码的代码标识以及该中间业务代码的实际执行方式，此时上述接口输入信息，可以对应的查找出在该业务事件内与实际执行方式相同的许可执行方式下绑定的需要移除的某一中间业务代码，然后直接在该业务事件下的绑定关系中移除该中间业务代码的代码信息，并将该绑定移除接口222的接口输出定义为移除成功或者移除失败及失败原因，从而保证各个业务事件所绑定的中间业务代码的有效更新。In addition, in order to support the effective update of the intermediate business codes bound to each business event, in this embodiment, some invalid binding relationships are deleted through the
同时，为了支持各个业务事件所绑定的中间业务代码的全面升级，本实施例会通过代码升级接口223来不断更新各个中间业务代码的代码内容，也就是本实施例中的代码字节流，此时该代码升级接口223的接口输入定义为待升级中间业务代码的代码标识，以及升级替换的代码升级字节流，此时按照上上述接口输入信息，将待升级中间业务代码原有的代码字节流替换为当前的代码升级字节流，并将该代码升级接口223的接口输出定义为升级成功或者升级失败及失败原因，从而保证中间业务代码升级的全面性和准确性。At the same time, in order to support the comprehensive upgrade of the intermediate service codes bound to each service event, this embodiment will continuously update the code content of each intermediate service code through the
进一步的，为了准确维护业务事件与中间业务代码之间的绑定关系，本实施例的业务事件的处理系统20中还可以包括存储组件240，该存储组件240采用键值对的方式记录每一业务事件在不同许可执行方式下已绑定的中间业务代码，以及该中间业务代码的代码字节流。Further, in order to accurately maintain the binding relationship between the business event and the intermediate business code, the business
示例性的，本实施例中的存储组件240可以划分出代码列表和绑定关系列表，以将中间业务代码的代码字节流和中间业务代码与业务事件之间的绑定关系隔离存储，此时在绑定关系列表中以事件标识和许可执行方式为键名，记录每一业务组件在不同许可执行方式下已绑定的中间业务代码的代码标识；在代码列表中以代码标识为键名，记录每一业务组件已绑定的各个中间业务代码的代码字节流。此外，在代码列表中还会记录每一业务组件已绑定的各个中间业务代码所依赖的扩展方法名称。Exemplarily, the
具体的，在绑定关系列表中通过将每一业务事件的事件标识和许可执行方式结合起来，统一作为key值，然后将value值设置为该key值指定的业务事件在具体许可执行方式下已绑定的各个中间业务代码的代码标识，从而将事件标识与代码标识关联起来，在每一业务事件的各个许可执行方式下得到准确的绑定关系；同时，每次为每一业务组件绑定的中间业务代码时，均会在代码列表中将所绑定的中间业务代码的代码标识作为key值，然后value值设置为该key值指定的中间业务代码的代码字节流，从而在代码列表中依次记录每一中间业务代码的代码内容。Specifically, in the binding relationship list, the event identifier of each business event and the license execution method are combined and unified as the key value, and then the value value is set as the business event specified by the key value has been executed under the specific license execution mode. The code identification of each intermediate business code that is bound, so as to associate the event identification with the code identification, and obtain an accurate binding relationship under each license execution mode of each business event; at the same time, each time is bound for each business component In the code list, the code identifier of the bound intermediate business code will be used as the key value in the code list, and then the value value will be set to the code byte stream of the intermediate business code specified by the key value, so that in the code list Record the code content of each intermediate business code in turn.
本实施例提供的技术方案，根据事件管理组件与代码绑定组件的具体功能分别设置不同的功能接口，保证目标应用运行前业务事件的准确注册以及目标应用运行过程后目标业务事件的准确触发检测，从而使业务事件执行与目标应用运行之间能够资源隔离，实现业务事件的多语音编译和多方式执行，保证业务事件的执行可移植性和可扩展性；同时采用在存储组件中划分出代码列表和绑定关系列表，来分别存储中间业务代码的代码内容和中间业务代码与业务事件之间的绑定关系，从而保证代码绑定的准确性，以及代码更新的便捷性。In the technical solution provided by this embodiment, different functional interfaces are respectively set according to the specific functions of the event management component and the code binding component, so as to ensure the accurate registration of business events before the target application runs and the accurate trigger detection of the target business events after the target application runs. , so that resources can be isolated between the execution of business events and the running of target applications, multi-voice compilation and multi-mode execution of business events can be realized, and the execution portability and scalability of business events can be guaranteed. A list and a binding relationship list are used to store the code content of the intermediate business code and the binding relationship between the intermediate business code and business events, so as to ensure the accuracy of code binding and the convenience of code update.
实施例三Embodiment 3
图3为本发明实施例三提供的一种业务事件的处理系统的结构示意图。本实施例是在上述实施例提供的技术方案的基础上进行优化。参照图3，该业务事件的处理系统30可以包括事件管理组件310、代码绑定组件320和事件执行组件330。FIG. 3 is a schematic structural diagram of a system for processing a service event according to Embodiment 3 of the present invention. This embodiment is optimized on the basis of the technical solutions provided by the foregoing embodiments. Referring to FIG. 3 , the business
其中，事件管理组件310内注册有目标应用运行时的各业务事件；具体的，代码绑定组件320面向事件管理组件310内已注册的每一业务事件，在每一许可执行方式下分别绑定支持多语言编译转换的中间业务代码；事件执行组件330如果在目标应用运行时接收到目标业务事件的触发消息，则采用每一许可执行方式对应执行目标业务事件在该许可执行方式下绑定的中间业务代码。Among them, the
同时，本实施例中的事件管理组件310可以包括事件注册接口311和事件触发接口312；其中，事件注册接口311采用事件标识和许可执行方式注册目标应用运行时的各业务事件；事件触发接口312按照事件标识和事件触发条件，实时检测各业务事件的触发状态，并向事件执行组件330发送目标业务事件的触发消息。At the same time, the
而且，代码绑定组件320可以包括绑定接口321、绑定移除接口322和代码升级接口323；其中，绑定接口321按照事件标识、代码标识、实际执行方式和代码字节流，为每一业务事件，在各许可执行方式下分别绑定对应的中间业务代码；绑定移除接口322按照事件标识、代码标识和实际执行方式，移除各业务事件在对应许可执行方式下已绑定的中间业务代码；代码升级接口323按照代码标识和代码升级字节流，更新各业务事件已绑定的中间业务代码。Moreover, the
此外，本实施例中的业务事件的处理系统30还可以包括存储组件340，该存储组件340采用键值对的方式记录每一业务事件在不同许可执行方式下已绑定的中间业务代码，以及该中间业务代码的代码字节流。具体的，存储组件340可以包括代码列表和绑定关系列表；其中，绑定关系列表以事件标识和许可执行方式为键名，记录每一业务组件在不同许可执行方式下已绑定的中间业务代码的代码标识；代码列表以代码标识为键名，记录每一业务组件已绑定的各个中间业务代码的代码字节流。In addition, the business
进一步的，为了保证目标应用运行过程中，目标业务事件被触发时所绑定的各个中间业务代码的准确执行，以及中间业务代码的准确绑定，本实施例的业务事件的处理系统30还可以包括虚拟环境创建组件350和控制中心360。Further, in order to ensure the accurate execution of each intermediate business code bound when the target business event is triggered during the running of the target application, and the accurate binding of the intermediate business code, the business
其中，虚拟环境创建组件350在目标应用启动时，根据每一业务事件已绑定的各中间业务代码的执行配置，创建对应的代码虚拟运行环境，并在代码虚拟运行环境内装载每一业务事件已绑定的各中间业务代码的扩展方法。The virtual
具体的，为了保证目标业务事件被触发后，所绑定的各个中间业务代码的准确执行，本实施例会在目标应用启动后，预先查找出每一业务事件已绑定的各个中间业务代码的执行配置，也就是中间业务代码成功运行时所需要利用的虚拟环境参数等，从而创建出适合各个中间业务代码成功运行的代码虚拟运行环境，例如运行控制器、运行内存以及是否允许开启线程来执行等，从而确保中间业务代码运行环境的隔离和安全。同时，通过查找每一业务事件已绑定的各个中间业务代码所依赖的各个扩展方法名称，能够将各个中间业务代码所依赖的各个扩展方法预先装载到所创建的代码虚拟运行环境内，以便后续直接采用外部调用的扩展方法来直接运行各个中间业务代码，从而保证中间业务代码的运行准确性。Specifically, in order to ensure the accurate execution of each bound intermediate business code after the target business event is triggered, this embodiment will pre-find the execution of each intermediate business code bound to each business event after the target application is started. Configuration, that is, the virtual environment parameters that the intermediate business code needs to use when running successfully, so as to create a code virtual running environment suitable for the successful running of each intermediate business code, such as running the controller, running memory, and whether to allow threads to be opened for execution, etc. , so as to ensure the isolation and security of the intermediate business code running environment. At the same time, by looking up the name of each extension method that each intermediate business code that has been bound to each business event depends on, each extension method that each intermediate business code depends on can be pre-loaded into the created code virtual operating environment, so that subsequent The extension method of external call is directly used to directly run each intermediate business code, so as to ensure the running accuracy of the intermediate business code.
此外，控制中心360面向事件管理组件310内已注册的每一业务事件，采用多语言开发对应的初始业务代码，并转换为对应的中间业务代码，以绑定到该业务事件的对应许可执行方式下。In addition, for each business event registered in the
具体的，控制中心360可以通过操作界面来展示事件管理组件310内已注册的每一业务事件，以及该业务事件当前绑定的各个中间业务代码，此时开发人员可以通过查看事件管理组件310内已注册的每一业务事件的中间业务代码的绑定情况，支持采用多语言为各个业务事件编写对应的初始业务代码，从而开发出多语言下的初始业务代码，进而将初始业务代码对应转换成支持多语言编译转换的中间业务代码，以绑定到该业务事件的对应许可执行方式下，从而保证业务事件下执行代码的可移植性。Specifically, the
本实施例提供的技术方案，在事件管理组件内注册目标应用运行时存在的各个业务事件，通过控制中心面向事件管理组件内已注册的每一业务事件，采用多语言开发对应的初始业务代码，通过代码绑定组件面向事件管理组件内已注册的每一业务事件，在每一许可执行方式下分别绑定支持多语言编译转换的中间业务代码，使得业务事件执行与目标应用运行之间能够资源隔离，从而实现业务事件的多语音编译和多方式执行，保证业务事件的执行可移植性和可扩展性；同时，在目标应用启动时，通过虚拟环境创建组件为各个中间业务代码创建对应的代码虚拟运行环境，从而保证中间业务代码的运行准确性，并在目标应用运行时通过事件执行组件接收到目标业务事件的触发消息时，则采用目标业务事件的每一许可执行方式对应执行目标业务事件在该许可执行方式下绑定的中间业务代码，避免对目标应用运行产生影响，从而提高目标应用运行的安全性和高效性。In the technical solution provided by this embodiment, each business event that exists when the target application is running is registered in the event management component, and the corresponding initial business code is developed in multiple languages for each business event registered in the event management component through the control center, Faced with each business event registered in the event management component through the code binding component, bind the intermediate business code that supports multi-language compilation and conversion under each license execution mode, so that resources can be connected between the execution of the business event and the running of the target application. Isolation, so as to realize multi-voice compilation and multi-mode execution of business events, and ensure the portability and scalability of the execution of business events; at the same time, when the target application starts, the corresponding code is created for each intermediate business code through the virtual environment creation component Virtual operating environment to ensure the accuracy of the operation of the intermediate business code, and when the target application is running through the event execution component to receive the trigger message of the target business event, each permission execution method of the target business event is used to execute the target business event correspondingly The intermediate business code bound in this permission execution mode avoids affecting the running of the target application, thereby improving the security and efficiency of running the target application.
实施例4Example 4
图4为本发明实施例四提供的一种业务事件的处理方法的流程图，本实施例可适用于在任一种业务应用内运行核心业务时，对核心业务扩展出的各个旁路逻辑下指定的业务事件进行处理的情况中。本实施例提供的一种业务事件的处理方法可以由本发明实施例提供的业务事件的处理装置来执行，该装置可以通过软件和/或硬件的方式来实现，并集成在执行本方法的计算机设备中，该计算机设备可以是配置有对应业务应用的终端。FIG. 4 is a flowchart of a method for processing a business event according to Embodiment 4 of the present invention. This embodiment is applicable to when running a core business in any business application, specifying the bypass logic extended by the core business. in the case of a business event being processed. The method for processing a business event provided in this embodiment may be executed by the apparatus for processing a business event provided in this embodiment of the present invention, and the apparatus may be implemented in software and/or hardware, and integrated into a computer device that executes the method. , the computer equipment may be a terminal configured with a corresponding service application.
具体的，参考图4，该方法可以包括如下非顺序执行的步骤：Specifically, referring to FIG. 4 , the method may include the following non-sequential steps:
S410，通过代码绑定组件面向事件管理组件内已注册的每一业务事件，在每一许可执行方式下分别绑定支持多语言编译转换的中间业务代码。S410 , face each business event registered in the event management component through the code binding component, and bind the intermediate business code supporting multi-language compilation and conversion under each license execution mode.
在本实施例中，为了准确了解目标应用运行时所产生的各个业务事件，会预先分析目标应用运行时，在核心业务下所扩展出的各个旁路逻辑，然后判断每一旁路逻辑下生成的业务事件，并将每一业务事件注册入事件管理组件内，以便后续通过该事件管理组件查看目标应用运行时核心业务扩展出的各个旁路逻辑下的业务事件，并针对每一业务事件的功能，专门编写对应的执行代码。此时，为了保证业务事件代码的可移植性，会为每一业务事件编写支持多语言编译转换的WASM语言下的中间业务代码，进而通过代码绑定组件面向事件管理组件内已注册的每一业务事件，分别绑定为该业务事件编写的各个中间业务代码，后续通过各个业务事件与中间业务代码之间的绑定关系，来查找表示每一业务事件功能的中间业务代码，并通过运行该中间业务代码来确保业务实践的准确处理。In this embodiment, in order to accurately understand the various business events generated when the target application is running, each bypass logic extended under the core business during the running of the target application will be analyzed in advance, and then each bypass logic generated under each bypass logic will be judged. business events, and register each business event into the event management component, so that the business events under each bypass logic extended by the core business of the target application when the target application is running can be viewed through the event management component, and the functions of each business event can be viewed , specially write the corresponding execution code. At this time, in order to ensure the portability of the business event code, the intermediate business code in the WASM language that supports multi-language compilation and conversion will be written for each business event, and then the code binding component will be used to face each registered event management component. The business event is bound to each intermediate business code written for the business event, and then the binding relationship between each business event and the intermediate business code is used to find the intermediate business code representing the function of each business event, and by running the Intermediate business code to ensure accurate processing of business practices.
同时，由于每一业务事件下编写的各个中间业务代码所表示的事件功能可能存在关联，也可能不存在任何关联，因此每一业务事件下各个中间业务代码的执行方式也各不相同，通过分析每一业务事件具备的事件功能之间的联系，可以确定出每一业务事件下运行各个中间业务代码时允许采用的许可执行方式，同时在针对每一业务事件的各个事件功能，编写对应的中间业务代码时，也会定义出每一中间业务代码的实际执行方式，进而通过代码绑定组件分析每一业务事件下编写的各个中间业务代码的实际执行方式，并按照该业务事件下每一中间业务代码的实际执行方式，将该中间业务代码绑定到该业务事件下执行方式相同的许可执行方式下，也就是在每一业务事件的每一许可执行方式下，均绑定有支持采用该许可执行方式来实际执行的中间业务代码。At the same time, because the event functions represented by each intermediate business code written under each business event may or may not have any correlation, the execution methods of each intermediate business code under each business event are also different. The connection between the event functions of each business event can determine the permission execution mode that is allowed when running each intermediate business code under each business event, and at the same time, for each event function of each business event, write the corresponding intermediate business code. When the business code is used, the actual execution mode of each intermediate business code will also be defined, and then the actual execution mode of each intermediate business code written under each business event will be analyzed through the code binding component, and the actual execution mode of each intermediate business code under the business event will be analyzed. The actual execution mode of the business code, the intermediate business code is bound to the permission execution mode with the same execution mode under the business event, that is, under each permission execution mode of each business event, is bound to support the use of this License execution mode to actually execute the intermediate business code.
需要说明的是，本实施例中业务事件的许可执行方式可以包括同步执行方式和异步执行方式中的至少一种。此时，在业务事件的同步执行方式下，会绑定一部分中间业务代码，在该业务事件的异步执行方式下，也会绑定一部分中间业务代码，从而实现业务事件的多语音编译和多方式执行，保证业务事件的执行可移植性和可扩展性。It should be noted that, the permission execution manner of the service event in this embodiment may include at least one of a synchronous execution manner and an asynchronous execution manner. At this time, in the synchronous execution mode of the business event, a part of the intermediate business code will be bound, and in the asynchronous execution mode of the business event, a part of the intermediate business code will also be bound, so as to realize the multi-voice compilation and multi-mode of the business event. Execution ensures the portability and scalability of the execution of business events.
此时，对于每一业务事件与中间业务代码的绑定而言，主要是接收预先为每一业务事件所编写的中间业务代码，确定该中间业务代码的实际执行方式，并将业务事件与中间业务代码对应关联起来，以便后续能够准确查找出为每一业务事件编写的中间业务代码，因此为了保证业务事件与中间业务代码之间的绑定关系准确性，本实施例中的代码绑定组件可以包括绑定接口(Bind)、绑定移除接口(Remove)和代码升级接口(Upgrade)。At this time, for the binding of each business event and the intermediate business code, it is mainly to receive the intermediate business code written for each business event in advance, determine the actual execution mode of the intermediate business code, and associate the business event with the intermediate business code. The business codes are correspondingly associated, so that the intermediate business code written for each business event can be accurately found in the future. Therefore, in order to ensure the accuracy of the binding relationship between the business event and the intermediate business code, the code binding component in this embodiment is It can include a binding interface (Bind), a binding removal interface (Remove), and a code upgrade interface (Upgrade).
其中，绑定接口按照事件标识、代码标识、实际执行方式和代码字节流，为每一业务事件，在各许可执行方式下分别绑定对应的中间业务代码；绑定移除接口按照事件标识、代码标识和实际执行方式，移除各业务事件在对应许可执行方式下已绑定的中间业务代码；代码升级接口按照代码标识和代码升级字节流，更新各业务事件已绑定的中间业务代码，从而保证业务事件与中间业务代码之间的准确绑定、绑定更新和代码升级。Among them, the binding interface is bound to the corresponding intermediate business code under each license execution mode for each business event according to the event ID, code ID, actual execution mode and code byte stream; the binding removal interface is based on the event ID. , code identification and actual execution mode, remove the intermediate business code that has been bound to each business event under the corresponding license execution mode; the code upgrade interface updates the intermediate business bound to each business event according to the code identification and code upgrade byte stream code, so as to ensure accurate binding, binding update and code upgrade between business events and intermediate business code.
S420，如果在目标应用运行时通过事件执行组件接收到目标业务事件的触发消息，则通过事件执行组件采用目标业务事件注册时的每一许可执行方式，对应执行目标业务事件在该许可执行方式下绑定的中间业务代码。S420, if the trigger message of the target business event is received through the event execution component when the target application is running, the event execution component adopts each permission execution mode when the target business event is registered, and the corresponding execution target business event is executed in the permission execution mode Binding intermediate business code.
可选的，在目标应用的运行过程中，会不断触发执行对应的业务事件，此时如果通过事件执行组件接收到某一目标业务事件的触发消息，那么直接会通过代码绑定组件查找出该目标业务事件在每一许可执行方式下分别绑定的各个中间业务代码，然后分别采用每一许可执行方式，对应执行目标业务事件在该许可执行方式下绑定的各个中间业务代码；例如，同步执行目标业务事件在同步执行方式下绑定的各个中间业务代码，异步执行目标业务事件在异步执行方式下绑定的各个中间业务代码。Optionally, during the running process of the target application, the corresponding business event will be continuously triggered and executed. At this time, if the trigger message of a target business event is received through the event execution component, the code binding component will directly find out the corresponding business event. Each intermediate business code bound to the target business event under each license execution mode, and then each license execution mode is respectively used to execute each intermediate business code bound to the target business event under this license execution mode; for example, synchronization Execute each intermediate business code bound by the target business event in the synchronous execution mode, and asynchronously execute each intermediate business code bound by the target business event in the asynchronous execution mode.
此时，为了保证目标应用内各个业务事件在开发阶段的准确注册以及在运行阶段的准确触发，本实施例中的事件管理组件可以包括事件注册接口(Regist)和事件触发接口(Trigger)。其中，事件注册接口采用事件标识和许可执行方式注册目标应用运行时的各业务事件；事件触发接口按照事件标识和事件触发条件，实时检测各业务事件的触发状态，并向事件执行组件发送目标业务事件的触发消息，从而保证目标业务事件的触发准确性。At this time, in order to ensure accurate registration of various business events in the target application in the development phase and accurate triggering in the running phase, the event management component in this embodiment may include an event registration interface (Regist) and an event trigger interface (Trigger). Among them, the event registration interface uses the event identifier and permission execution method to register each business event when the target application is running; the event trigger interface detects the trigger status of each business event in real time according to the event identifier and event trigger conditions, and sends the target business to the event execution component. The triggering message of the event ensures the triggering accuracy of the target business event.
需要说明的是，本实施例提供的业务事件的处理方法可以应用于本发明任意实施例所提供的业务事件的处理系统中，具备相同的功能和有益效果。It should be noted that the business event processing method provided in this embodiment can be applied to the business event processing system provided by any embodiment of the present invention, and has the same functions and beneficial effects.
本实施例提供的技术方案，在事件管理组件内注册目标应用运行时存在的各个业务事件，通过代码绑定组件面向事件管理组件内已注册的每一业务事件，在每一许可执行方式下分别绑定支持多语言编译转换的中间业务代码，使得业务事件执行与目标应用运行之间能够资源隔离，从而实现业务事件的多语音编译和多方式执行，保证业务事件的执行可移植性和可扩展性；同时，如果在目标应用运行时通过事件执行组件接收到目标业务事件的触发消息，则采用目标业务事件的每一许可执行方式对应执行目标业务事件在该许可执行方式下绑定的中间业务代码，避免对目标应用运行产生影响，从而提高目标应用运行的安全性和高效性。In the technical solution provided by this embodiment, each business event that exists when the target application is running is registered in the event management component, and each business event registered in the event management component is oriented to each business event registered in the event management component through the code binding component. Bind the intermediate business code that supports multi-language compilation and conversion, so that resources can be isolated between the execution of business events and the running of the target application, so as to realize multi-voice compilation and multi-mode execution of business events, and ensure the portability and scalability of the execution of business events. At the same time, if the trigger message of the target business event is received through the event execution component when the target application is running, each permission execution mode of the target business event is used to execute the intermediate services bound by the target business event under the permission execution mode. code to avoid affecting the running of the target application, thereby improving the security and efficiency of the running of the target application.
实施例五Embodiment 5
图5为本发明实施例五提供的一种业务事件的处理方法的流程图。本实施例是在上述实施例的基础上进行优化。具体的，如图5所示，本实施例主要对于业务事件与中间业务代码的具体绑定过程以及目标业务事件被触发时所绑定的各个中间业务代码的具体执行过程进行详细的解释说明。FIG. 5 is a flowchart of a method for processing a service event according to Embodiment 5 of the present invention. This embodiment is optimized on the basis of the above-mentioned embodiment. Specifically, as shown in FIG. 5 , this embodiment mainly explains in detail the specific binding process of the business event and the intermediate business code and the specific execution process of each intermediate business code bound when the target business event is triggered.
可选的，如图5所示，本实施例中可以包括如下步骤：Optionally, as shown in FIG. 5 , this embodiment may include the following steps:
S510，通过代码绑定组件面向事件管理组件内已注册的每一业务事件，在每一许可执行方式下分别绑定支持多语言编译转换的中间业务代码。S510, face each business event registered in the event management component through the code binding component, and bind the intermediate business code supporting multi-language compilation and conversion under each license execution mode.
S520，通过存储组件采用键值对的方式记录每一业务事件在不同许可执行方式下已绑定的中间业务代码，以及该中间业务代码的代码字节流。S520, the storage component uses a key-value pair to record the bound intermediate business code of each business event under different license execution modes, and the code byte stream of the intermediate business code.
可选的，为了准确维护业务事件与中间业务代码之间的绑定关系，可以将存储组件划分出代码列表和绑定关系列表，以将中间业务代码的代码字节流和中间业务代码与业务事件之间的绑定关系隔离存储，此时在绑定关系列表中以事件标识和许可执行方式为键名，记录每一业务组件在不同许可执行方式下已绑定的中间业务代码的代码标识；在代码列表中以代码标识为键名，记录每一业务组件已绑定的各个中间业务代码的代码字节流。此外，在代码列表中还会记录每一业务组件已绑定的各个中间业务代码所依赖的扩展方法名称。Optionally, in order to accurately maintain the binding relationship between business events and intermediate business codes, the storage component can be divided into a code list and a binding relationship list, so as to combine the code byte stream of the intermediate business code and the intermediate business code with the business code. The binding relationship between events is isolated and stored. At this time, in the binding relationship list, the event ID and the license execution mode are used as the key names to record the code ID of the intermediate business code bound by each business component under different license execution modes. ; In the code list, use the code ID as the key name to record the code byte stream of each intermediate service code bound to each service component. In addition, the extension method name that each intermediate business code bound to each business component depends on is also recorded in the code list.
具体的，在绑定关系列表中通过将每一业务事件的事件标识和许可执行方式结合起来，统一作为key值，然后将value值设置为该key值指定的业务事件在具体许可执行方式下已绑定的各个中间业务代码的代码标识，从而将事件标识与代码标识关联起来，在每一业务事件的各个许可执行方式下得到准确的绑定关系；同时，每次为每一业务组件绑定的中间业务代码时，均会在代码列表中将所绑定的中间业务代码的代码标识作为key值，然后value值设置为该key值指定的中间业务代码的代码字节流，从而在代码列表中依次记录每一中间业务代码的代码内容。Specifically, in the binding relationship list, the event identifier of each business event and the license execution method are combined and unified as the key value, and then the value value is set as the business event specified by the key value has been executed under the specific license execution mode. The code identification of each intermediate business code that is bound, so as to associate the event identification with the code identification, and obtain an accurate binding relationship under each license execution mode of each business event; at the same time, each time is bound for each business component In the code list, the code identifier of the bound intermediate business code will be used as the key value in the code list, and then the value value will be set to the code byte stream of the intermediate business code specified by the key value, so that in the code list Record the code content of each intermediate business code in turn.
S530，在目标应用启动时，通过虚拟环境创建组件根据每一业务事件已绑定的各中间业务代码的执行配置，创建对应的代码虚拟运行环境，并在代码虚拟运行环境内装载每一业务事件已绑定的各中间业务代码的扩展方法。S530, when the target application is started, the virtual environment creation component creates a corresponding code virtual operating environment according to the execution configuration of each intermediate business code bound to each business event, and loads each business event in the code virtual operating environment The extension method of each bound intermediate business code.
具体的，为了保证目标业务事件被触发后，所绑定的各个中间业务代码的准确执行，本实施例会在目标应用启动后，预先查找出每一业务事件已绑定的各个中间业务代码的执行配置，也就是中间业务代码成功运行时所需要利用的虚拟环境参数等，从而创建出适合各个中间业务代码成功运行的代码虚拟运行环境，例如运行控制器、运行内存以及是否允许开启线程来执行等，从而确保中间业务代码运行环境的隔离和安全。同时，通过查找每一业务事件已绑定的各个中间业务代码所依赖的各个扩展方法名称，能够将各个中间业务代码所依赖的各个扩展方法预先装载到所创建的代码虚拟运行环境内，以便后续直接采用外部调用的扩展方法来直接运行各个中间业务代码，从而保证中间业务代码的运行准确性。Specifically, in order to ensure the accurate execution of each bound intermediate business code after the target business event is triggered, this embodiment will pre-find the execution of each intermediate business code bound to each business event after the target application is started. Configuration, that is, the virtual environment parameters that the intermediate business code needs to use when running successfully, so as to create a code virtual running environment suitable for the successful running of each intermediate business code, such as running the controller, running memory, and whether to allow threads to be opened for execution, etc. , so as to ensure the isolation and security of the intermediate business code running environment. At the same time, by looking up the name of each extension method that each intermediate business code that has been bound to each business event depends on, each extension method that each intermediate business code depends on can be pre-loaded into the created code virtual operating environment, so that subsequent The extension method of external call is directly used to directly run each intermediate business code, so as to ensure the running accuracy of the intermediate business code.
S540，如果在目标应用运行时通过事件执行组件接收到目标业务事件的触发消息，则通过事件执行组件从代码绑定组件中查询目标业务事件在每一许可执行方式下已绑定的中间业务代码。S540, if the triggering message of the target business event is received through the event execution component when the target application is running, the event execution component is used to query the code binding component for the bound intermediate business code of the target business event under each license execution mode .
可选的，如果在目标应用运行过程中，通过事件执行组件接收到目标业务事件的触发消息，说明该目标业务事件被触发，需要运行该目标业务事件绑定的各个中间业务代码，来实现目标业务事件的准确处理，此时首先需要从代码绑定组件中查询目标业务事件在每一许可执行方式下已绑定的中间业务代码，以便后续采用每一许可执行方式，对应执行目标业务事件在该许可执行方式下绑定的中间业务代码，确保业务事件的处理准确性。Optionally, if a trigger message of the target business event is received through the event execution component during the running of the target application, it means that the target business event is triggered, and each intermediate business code bound to the target business event needs to be run to achieve the goal. For accurate processing of business events, at this time, it is first necessary to query the intermediate business code of the target business event bound under each license execution mode from the code binding component, so that each license execution mode can be used subsequently, and the corresponding execution target business event is in The intermediate business code bound in this license execution mode ensures the processing accuracy of business events.
S550，通过事件执行组件采用目标业务事件注册时的每一许可执行方式，对应执行目标业务事件在该许可执行方式下绑定的中间业务代码。S550, the event execution component adopts each permission execution mode when the target business event is registered, correspondingly executes the intermediate business code bound to the target business event in the permission execution mode.
S560，通过事件执行组件回调目标业务事件在同步执行方式下的代码执行结果，并发送给目标应用。S560, the code execution result of the target business event in the synchronous execution mode is called back by the event execution component, and sent to the target application.
可选的，在完成目标业务事件在每一许可执行方式下所绑定的各个中间业务代码的执行后，为了保证目标应用的准确运行，本实施例还会通过事件执行组件来回调该目标业务事件在同步执行方式下的代码执行结果，从而应用到目标应用的后续运行过程中，实现目标应用内核心业务的准确运行。Optionally, after completing the execution of each intermediate business code bound to the target business event under each permission execution mode, in order to ensure the accurate operation of the target application, this embodiment will also use the event execution component to call back the target business. The code execution result of the event in the synchronous execution mode is applied to the subsequent running process of the target application to realize the accurate operation of the core business in the target application.
本实施例提供的技术方案，在事件管理组件内注册目标应用运行时存在的各个业务事件，通过代码绑定组件面向事件管理组件内已注册的每一业务事件，在每一许可执行方式下分别绑定支持多语言编译转换的中间业务代码，使得业务事件执行与目标应用运行之间能够资源隔离，从而实现业务事件的多语音编译和多方式执行，保证业务事件的执行可移植性和可扩展性；同时，如果在目标应用运行时通过事件执行组件接收到目标业务事件的触发消息，则采用目标业务事件的每一许可执行方式对应执行目标业务事件在该许可执行方式下绑定的中间业务代码，避免对目标应用运行产生影响，从而提高目标应用运行的安全性和高效性。In the technical solution provided by this embodiment, each business event that exists when the target application is running is registered in the event management component, and each business event registered in the event management component is oriented to each business event registered in the event management component through the code binding component. Bind the intermediate business code that supports multi-language compilation and conversion, so that resources can be isolated between the execution of business events and the running of the target application, so as to realize multi-voice compilation and multi-mode execution of business events, and ensure the portability and scalability of the execution of business events. At the same time, if the trigger message of the target business event is received through the event execution component when the target application is running, each permission execution mode of the target business event is used to execute the intermediate services bound by the target business event under the permission execution mode. code to avoid affecting the running of the target application, thereby improving the security and efficiency of the running of the target application.
实施例六Embodiment 6
图6为本发明实施例六提供的一种业务事件的处理装置的结构示意图，可以配置于本发明任意实施例提供的业务事件的处理系统中。具体的，如图6所示，该装置可以包括：FIG. 6 is a schematic structural diagram of a service event processing apparatus provided in Embodiment 6 of the present invention, which may be configured in the service event processing system provided by any embodiment of the present invention. Specifically, as shown in Figure 6, the device may include:
代码绑定模块610，用于通过代码绑定组件面向事件管理组件内已注册的每一业务事件，在每一许可执行方式下分别绑定支持多语言编译转换的中间业务代码；The
业务代码执行模块620，用于如果在目标应用运行时通过事件执行组件接收到目标业务事件的触发消息，则通过所述事件执行组件采用所述目标业务事件注册时的每一许可执行方式，对应执行所述目标业务事件在该许可执行方式下绑定的中间业务代码；The business
其中，所述事件管理组件内注册有目标应用运行时的各业务事件。Wherein, each business event of the target application running time is registered in the event management component.
本实施例提供的技术方案，在事件管理组件内注册目标应用运行时存在的各个业务事件，通过代码绑定组件面向事件管理组件内已注册的每一业务事件，在每一许可执行方式下分别绑定支持多语言编译转换的中间业务代码，使得业务事件执行与目标应用运行之间能够资源隔离，从而实现业务事件的多语音编译和多方式执行，保证业务事件的执行可移植性和可扩展性；同时，如果在目标应用运行时通过事件执行组件接收到目标业务事件的触发消息，则采用目标业务事件的每一许可执行方式对应执行目标业务事件在该许可执行方式下绑定的中间业务代码，避免对目标应用运行产生影响，从而提高目标应用运行的安全性和高效性。In the technical solution provided by this embodiment, each business event that exists when the target application is running is registered in the event management component, and each business event registered in the event management component is oriented to each business event registered in the event management component through the code binding component. Bind the intermediate business code that supports multi-language compilation and conversion, so that resources can be isolated between the execution of business events and the running of the target application, so as to realize multi-voice compilation and multi-mode execution of business events, and ensure the portability and scalability of the execution of business events. At the same time, if the trigger message of the target business event is received through the event execution component when the target application is running, each permission execution mode of the target business event is used to execute the intermediate services bound by the target business event under the permission execution mode. code to avoid affecting the running of the target application, thereby improving the security and efficiency of the running of the target application.
本实施例提供的业务事件的处理装置可适用于上述任意实施例提供的业务事件的处理方法，具备相应的功能和有益效果。The apparatus for processing a business event provided in this embodiment is applicable to the processing method for a business event provided in any of the above embodiments, and has corresponding functions and beneficial effects.
实施例七Embodiment 7
图7为本发明实施例七提供的一种计算机设备的结构示意图，如图7所示，该计算机设备包括处理器70、存储装置71和通信装置72；计算机设备中处理器70的数量可以是一个或多个，图7中以一个处理器70为例；计算机设备中的处理器70、存储装置71和通信装置72可以通过总线或其他方式连接，图7中以通过总线连接为例。FIG. 7 is a schematic structural diagram of a computer device according to Embodiment 7 of the present invention. As shown in FIG. 7 , the computer device includes a
本实施例提供的一种计算机设备可用于执行上述任意实施例提供的业务事件的处理方法，具备相应的功能和有益效果。The computer device provided in this embodiment can be used to execute the business event processing method provided by any of the foregoing embodiments, and has corresponding functions and beneficial effects.
实施例八Embodiment 8
本发明实施例八还提供了一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时可实现上述任意实施例中的业务事件的处理方法。该方法具体可以包括如下非顺序执行的步骤：The eighth embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the method for processing a service event in any of the foregoing embodiments can be implemented. Specifically, the method may include the following non-sequential steps:
通过代码绑定组件面向事件管理组件内已注册的每一业务事件，在每一许可执行方式下分别绑定支持多语言编译转换的中间业务代码；Facing each business event registered in the event management component through the code binding component, bind the intermediate business code supporting multi-language compilation and conversion under each license execution mode;
如果在目标应用运行时通过事件执行组件接收到目标业务事件的触发消息，则通过所述事件执行组件采用所述目标业务事件注册时的每一许可执行方式，对应执行所述目标业务事件在该许可执行方式下绑定的中间业务代码；If the trigger message of the target business event is received through the event execution component when the target application is running, the event execution component adopts each permission execution mode when the target business event is registered, and executes the target business event in the corresponding execution mode of the target business event. The intermediate business code bound in the license execution mode;
其中，所述事件管理组件内注册有目标应用运行时的各业务事件。Wherein, each business event of the target application running time is registered in the event management component.
当然,本发明实施例所提供的一种包含计算机可执行指令的存储介质，其计算机可执行指令不限于如上所述的方法操作，还可以执行本发明任意实施例所提供的业务事件的处理方法中的相关操作。Of course, a storage medium containing computer-executable instructions provided by an embodiment of the present invention, the computer-executable instructions of which are not limited to the above-mentioned method operations, and can also execute the business event processing method provided by any embodiment of the present invention. related operations in .
通过以上关于实施方式的描述，所属领域的技术人员可以清楚地了解到，本发明可借助软件及必需的通用硬件来实现，当然也可以通过硬件实现，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在计算机可读存储介质中，如计算机的软盘、只读存储器(Read-Only Memory,ROM)、随机存取存储器(RandomAccess Memory,RAM)、闪存(FLASH)、硬盘或光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。From the above description of the embodiments, those skilled in the art can clearly understand that the present invention can be realized by software and necessary general-purpose hardware, and of course can also be realized by hardware, but in many cases the former is a better embodiment . Based on such understanding, the technical solutions of the present invention can be embodied in the form of software products in essence or the parts that make contributions to the prior art, and the computer software products can be stored in a computer-readable storage medium, such as a floppy disk of a computer , read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), flash memory (FLASH), hard disk or CD, etc., including several instructions to make a computer device (which can be a personal computer, A server, or a network device, etc.) executes the methods described in the various embodiments of the present invention.
值得注意的是，上述业务事件的处理装置的实施例中，所包括的各个单元和模块只是按照功能逻辑进行划分的，但并不局限于上述的划分，只要能够实现相应的功能即可；另外，各功能单元的具体名称也只是为了便于相互区分，并不用于限制本发明的保护范围。It is worth noting that, in the embodiment of the above-mentioned apparatus for processing business events, the units and modules included are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be realized; , the specific names of the functional units are only for the convenience of distinguishing from each other, and are not used to limit the protection scope of the present invention.
以上所述仅为本发明的优选实施例，并不用于限制本发明，对于本领域技术人员而言，本发明可以有各种改动和变化。凡在本发明的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.
Claims (17)
Translated fromChinesePriority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011459550.1ACN112579156B (en) | 2020-12-11 | 2020-12-11 | A business event processing system, processing method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011459550.1ACN112579156B (en) | 2020-12-11 | 2020-12-11 | A business event processing system, processing method, device and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112579156Atrue CN112579156A (en) | 2021-03-30 |
| CN112579156B CN112579156B (en) | 2024-11-22 |
Family
ID=75131421
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011459550.1AActiveCN112579156B (en) | 2020-12-11 | 2020-12-11 | A business event processing system, processing method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112579156B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113282378A (en)* | 2021-07-23 | 2021-08-20 | 奥特酷智能科技(南京)有限公司 | Vehicle-mounted system based on environment isolation subsystem |
| CN113296742A (en)* | 2021-05-17 | 2021-08-24 | 建信金融科技有限责任公司 | APP data processing method and device and mobile terminal |
| CN120407043A (en)* | 2025-07-01 | 2025-08-01 | 中信建投证券股份有限公司 | Business response method, device, electronic device and storage medium |
| CN120407043B (en)* | 2025-07-01 | 2025-10-14 | 中信建投证券股份有限公司 | A business response method, device, electronic device and storage medium |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040220910A1 (en)* | 2003-05-02 | 2004-11-04 | Liang-Jie Zang | System and method of dynamic service composition for business process outsourcing |
| US20050278708A1 (en)* | 2004-06-15 | 2005-12-15 | Dong Zhao | Event management framework for network management application development |
| US20100064357A1 (en)* | 2008-09-09 | 2010-03-11 | Kerstin Baird | Business Processing System Combining Human Workflow, Distributed Events, And Automated Processes |
| CN103279840A (en)* | 2013-06-08 | 2013-09-04 | 北京首钢自动化信息技术有限公司 | Workflow engine implement method based on dynamic language and event processing mechanism |
| CN103927218A (en)* | 2014-04-30 | 2014-07-16 | 广州唯品会网络技术有限公司 | Event dispatching method and system |
| US20190305957A1 (en)* | 2018-04-02 | 2019-10-03 | Ca, Inc. | Execution smart contracts configured to establish trustworthiness of code before execution |
| CN111309406A (en)* | 2020-02-17 | 2020-06-19 | 北京字节跳动网络技术有限公司 | Event processing method and device of application program and electronic equipment |
| CN111369221A (en)* | 2020-03-09 | 2020-07-03 | 浙江大学 | Intelligent contract monitoring method and system for block chain supervision |
| US20200250372A1 (en)* | 2019-02-04 | 2020-08-06 | Cloudflare, Inc. | Application remoting across a network using draw commands |
| CN111679828A (en)* | 2020-05-25 | 2020-09-18 | 泰康保险集团股份有限公司 | Data processing method and device, electronic equipment and storage medium |
- 2020
- 2020-12-11CNCN202011459550.1Apatent/CN112579156B/enactiveActive
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040220910A1 (en)* | 2003-05-02 | 2004-11-04 | Liang-Jie Zang | System and method of dynamic service composition for business process outsourcing |
| US20050278708A1 (en)* | 2004-06-15 | 2005-12-15 | Dong Zhao | Event management framework for network management application development |
| US20100064357A1 (en)* | 2008-09-09 | 2010-03-11 | Kerstin Baird | Business Processing System Combining Human Workflow, Distributed Events, And Automated Processes |
| CN103279840A (en)* | 2013-06-08 | 2013-09-04 | 北京首钢自动化信息技术有限公司 | Workflow engine implement method based on dynamic language and event processing mechanism |
| CN103927218A (en)* | 2014-04-30 | 2014-07-16 | 广州唯品会网络技术有限公司 | Event dispatching method and system |
| US20190305957A1 (en)* | 2018-04-02 | 2019-10-03 | Ca, Inc. | Execution smart contracts configured to establish trustworthiness of code before execution |
| US20200250372A1 (en)* | 2019-02-04 | 2020-08-06 | Cloudflare, Inc. | Application remoting across a network using draw commands |
| CN111309406A (en)* | 2020-02-17 | 2020-06-19 | 北京字节跳动网络技术有限公司 | Event processing method and device of application program and electronic equipment |
| CN111369221A (en)* | 2020-03-09 | 2020-07-03 | 浙江大学 | Intelligent contract monitoring method and system for block chain supervision |
| CN111679828A (en)* | 2020-05-25 | 2020-09-18 | 泰康保险集团股份有限公司 | Data processing method and device, electronic equipment and storage medium |
Non-Patent Citations (6)
| Title |
|---|
| ABDERRAHMANE LESHOB等: "A value-oriented approach to business process specialization: Principles, proof-of-concept, and validation", JOURNAL OF SYSTEMS AND SOFTWARE, vol. 127, 17 February 2017 (2017-02-17), pages 120 - 149, XP029939939, DOI: 10.1016/j.jss.2017.02.002* |
| BEN WILCOCK: "Simple Event Driven Microservices with Spring Cloud Stream", Retrieved from the Internet <URL:https://spring.io/blog/2019/10/15/simple-event-driven-microservices-with-spring-cloud-stream>* |
| JAN ŠILAR等: "Development of In-Browser Simulators for Medical Education: Introduction of a Novel Software Toolchain", J MED INTERNET RES 2019, vol. 21, no. 7, 3 July 2019 (2019-07-03), pages 1 - 10* |
| 崔盛斌: "面向航空票价发布系统的事件驱动模型设计与应用", 中国优秀硕士学位论文全文数据库 工程科技Ⅱ辑, no. 1, 15 January 2020 (2020-01-15), pages 031 - 61* |
| 潘从祥: "基于Web技术的移动机器人SLAM方法研究", 中国优秀硕士学位论文全文数据库 信息科技辑, no. 1, 15 January 2020 (2020-01-15), pages 140 - 852* |
| 車輪の唄: "spring 事件：实现业务逻辑解耦", Retrieved from the Internet <URL:https://www.cnblogs.com/kukudi/p/17345265.html>* |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113296742A (en)* | 2021-05-17 | 2021-08-24 | 建信金融科技有限责任公司 | APP data processing method and device and mobile terminal |
| CN113282378A (en)* | 2021-07-23 | 2021-08-20 | 奥特酷智能科技(南京)有限公司 | Vehicle-mounted system based on environment isolation subsystem |
| CN113282378B (en)* | 2021-07-23 | 2021-11-12 | 奥特酷智能科技(南京)有限公司 | Vehicle-mounted system based on environment isolation subsystem |
| CN120407043A (en)* | 2025-07-01 | 2025-08-01 | 中信建投证券股份有限公司 | Business response method, device, electronic device and storage medium |
| CN120407043B (en)* | 2025-07-01 | 2025-10-14 | 中信建投证券股份有限公司 | A business response method, device, electronic device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112579156B (en) | 2024-11-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2368189B1 (en) | Debugging pipeline | |
| CN105512044B (en) | Update method and system for the library of object of keyword driving test | |
| US7539854B2 (en) | System and method to seamlessly enable enhanced management and scripting of a computer system and its add-in devices | |
| US20100281463A1 (en) | XML based scripting framework, and methods of providing automated interactions with remote systems | |
| US8607203B1 (en) | Test automation framework using dependency injection | |
| CN111179086A (en) | Intelligent contract virtual machine based on WebAssembly | |
| CN105893061A (en) | Application program development method and system | |
| CN118227424B (en) | Log record template access method and system applied to distributed component | |
| CN108345458B (en) | A method and system for calling static compiled language and scripting language | |
| CN111880804A (en) | Application program code processing method and device | |
| CN112579156A (en) | Processing system, processing method, processing device and processing equipment of business event | |
| WO2017020459A1 (en) | Method and apparatus for configuring plugin package for host | |
| WO2022038461A1 (en) | Method and system for identifying and extracting independent services from a computer program | |
| CN111240772A (en) | Data processing method and device based on block chain and storage medium | |
| WO2023179298A1 (en) | Application program updating method and apparatus, application program development method and apparatus, and computer device | |
| CN111240728A (en) | Application program updating method, device, equipment and storage medium | |
| US10394610B2 (en) | Managing split packages in a module system | |
| CN111061642A (en) | Full-automatic competition data processing system and method based on user data | |
| CN113590179B (en) | Plug-in detection method and device, electronic equipment and storage medium | |
| CN113590166B (en) | Application program updating method and device and computer readable storage medium | |
| CN113626001B (en) | API dynamic arrangement method and device based on script | |
| CN114253532A (en) | Model development method, device, engine and storage medium | |
| CN116501596A (en) | App testing method and device | |
| CN113791824A (en) | Peripheral driver loading method, system and medium for terminal equipment | |
| CN104714791B (en) | A kind of method and apparatus that Web applications are split and reset |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |