CN110321211A - Asynchronous schedule method and device for operation system - Google Patents
Asynchronous schedule method and device for operation system Download PDFInfo
- Publication number
- CN110321211A CN110321211A CN201910583150.2A CN201910583150A CN110321211A CN 110321211 A CN110321211 A CN 110321211A CN 201910583150 A CN201910583150 A CN 201910583150A CN 110321211 A CN110321211 A CN 110321211A
- Authority
- CN
- China
- Prior art keywords
- operation system
- event
- asynchronous
- processing
- asynchronous schedule
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
This application discloses a kind of asynchronous schedule method and devices for operation system.This method is included in asynchronous process scene, submits event according to standard Event Processing Interface；In event saving interface, by the data storage handled in asynchronous process scene to database；Further include: one or more events are handled in the asynchronous schedule component；Event handling class is determined according to event type, and the event handling class of the operation system is called according to the event handling class；The processing result that the operation system returns is received in the asynchronous schedule component.Present application addresses the high technical problems of asynchronous process cost.By the application by the scene generalities of asynchronous process, abstract.Insertion type component in the application is easy integrated with operation system.And need not additionally dispose, save hardware resource.
Description
Technical field
This application involves operation system asynchronous process fields, in particular to a kind of asynchronous tune for operation system
Spend method and device.
Background technique
There can be many scenes in operation system to need to switch to asynchronous process.
Inventors have found that existing asynchronous process is using centralized settling mode, it is higher for the cost of operation system access.
Further, maintenance cost is caused to improve.
For the high problem of asynchronous process cost in the related technology, currently no effective solution has been proposed.
Summary of the invention
The main purpose of the application is to provide a kind of asynchronous schedule method and device for operation system, different to solve
The high problem of step processing cost.
To achieve the goals above, according to the one aspect of the application, a kind of asynchronous tune for operation system is provided
Degree method is embedded in asynchronous schedule component in operation system.
It include: in asynchronous process scene, according to standard according to the asynchronous schedule method for operation system of the application
Event handling interface submits event, wherein one or more events refer to different to needing to carry out by asynchronous schedule component
Walk the conversion results of the business scenario of processing；In event saving interface, by the data storage handled in asynchronous process scene to number
According to library；Further include: one or more events are handled in the asynchronous schedule component；It is determined at event according to event type
Class is managed, and calls the event handling class of the operation system according to the event handling class；It is received in the asynchronous schedule component
The processing result that the operation system returns.
Further, in asynchronous process scene, before standard Event Processing Interface submission event, further includes: different
Step scheduling assembly initialization step, the asynchronous schedule assembly initialization step includes: in operation system charging assembly, starting group
Part initialization；Event handling class in component scans operation system, and bind the mapping of event handling class and event type；In industry
Business system completes assembly initialization.
Further, if receiving the processing result that the operation system returns in the asynchronous schedule component includes: institute
The processing result for stating operation system return is success, then is to handle successfully by event handling status modifier；It converts event to cold
Data complete event handling.
Further, if receiving the processing result that the operation system returns in the asynchronous schedule component includes: institute
The processing result for stating operation system return is to retry, then is in processing by event handling status modifier；Calculating event is next time
The time is handled, next event calling processing is waited.
Further, if receiving the processing result that the operation system returns in the asynchronous schedule component includes: institute
The processing result for stating operation system return is failure, then is processing failure by event handling status modifier；Increase the failure of processing
Number, according to the frequency of failure calculating handle the time next time, wherein the frequency of failure it is more, calculating locate next time
It is bigger to manage time interval.
Further, asynchronous schedule group further include: alarm step, the alarm step include: to judge asynchronous schedule component
Whether the frequency of failure received in the processing result that the operation system returns is more than processing threshold values；If it is determined that asynchronous schedule group
It is more than processing threshold values that part, which receives the frequency of failure in the processing result that the operation system returns, then sends processing failure alarm simultaneously
Terminate event handling.
Further, asynchronous schedule group further include: cleaning or the step of ArchivalEvent receives institute according to asynchronous schedule component
State the event that the processing in the processing result of operation system return successfully has been converted into cold data；To the cold data in event into
Row periodically filing or cleaning.
To achieve the goals above, according to the another aspect of the application, a kind of asynchronous tune for operation system is provided
Device is spent, asynchronous schedule component is embedded in operation system.
It include: submission module according to the asynchronous schedule device for operation system of the application, in asynchronous process field
Jing Zhong submits event according to standard Event Processing Interface, wherein one or more events refer to through asynchronous schedule component
Conversion results to the business scenario for needing to carry out asynchronous process；Preserving module is used in event saving interface, by asynchronous process
The data storage handled in scene is to database；Further include: processing module, for handling one in the asynchronous schedule component
Or multiple events；Calling module, for determining event handling class according to event type, and according to the event handling class tune
With the event handling class of the operation system；Return module is returned for receiving the operation system in the asynchronous schedule component
The processing result returned.
Further, further includes: initialization module, for starting assembly initialization in operation system charging assembly；Component
The event handling class in operation system is scanned, and binds the mapping of event handling class and event type；In operation system completion group
Part initialization.
Further, the asynchronous schedule component further include: alarm module, for judging described in the reception of asynchronous schedule component
Whether the frequency of failure in processing result that operation system returns is more than processing threshold values；If it is determined that asynchronous schedule component receives institute
Stating the frequency of failure in the processing result of operation system return is more than processing threshold values, then sends processing failure and alert and terminate event
Processing；Data filing or cleaning modul, for being received in the processing result that the operation system returns according to asynchronous schedule component
Processing successfully have been converted into the event of cold data；Cold data in event is periodically filed or cleared up.
It is used for the asynchronous schedule method and device of operation system in the embodiment of the present application, is embedded in using in operation system
The mode of asynchronous schedule component is protected by submitting event according to standard Event Processing Interface in asynchronous process scene in event
Interface is deposited, by the data storage handled in asynchronous process scene to database, and by the asynchronous schedule component
The one or more events of reason；Event handling class is determined according to event type, and according to event handling class calling
The event handling class of operation system；The processing result that the operation system returns is received in the asynchronous schedule component.Reach
By the scene generalities of asynchronous process, the purpose of abstract, the whole process of event handling is standardized to realize, it is stylized
Technical effect, and then solve the high technical problem of asynchronous process cost.
Further, by the way that cold and hot data are automatically separated, can make data to be processed remain at one it is controllable
In range, avoid causing data accumulation excessive as time increases to influence treatment effeciency.Decayed plan by processing failure
Slightly, so that it may avoid it is meaningless retry, save server resource.By introducing alarming mechanism, when event can not be processed
When, it can timely notify business responsible person, improve the timeliness found the problem.Periodically file in addition, additionally providing cold data
Or clearing function, database resource can be saved.
Detailed description of the invention
The attached drawing constituted part of this application is used to provide further understanding of the present application, so that the application's is other
Feature, objects and advantages become more apparent upon.The illustrative examples attached drawing and its explanation of the application is for explaining the application, not
Constitute the improper restriction to the application.In the accompanying drawings:
Fig. 1 is the asynchronous schedule method flow schematic diagram for operation system according to the application first embodiment；
Fig. 2 is the asynchronous schedule method flow schematic diagram for operation system according to the application second embodiment；
Fig. 3 is the asynchronous schedule method flow schematic diagram for operation system according to the application 3rd embodiment；
Fig. 4 is the asynchronous schedule method flow schematic diagram for operation system according to the application fourth embodiment；
Fig. 5 is the asynchronous schedule method flow schematic diagram for operation system according to the 5th embodiment of the application；
Fig. 6 is the asynchronous schedule method flow schematic diagram for operation system according to the application sixth embodiment；
Fig. 7 is the asynchronous schedule method flow schematic diagram for operation system according to the 7th embodiment of the application；
Fig. 8 is the asynchronous schedule apparatus structure schematic diagram for operation system according to the application first embodiment；
Fig. 9 is the asynchronous schedule apparatus structure schematic diagram for operation system according to the application second embodiment；
Figure 10 is the scheduling component operation schematic illustration according to the embodiment of the present application.
Specific embodiment
In order to make those skilled in the art more fully understand application scheme, below in conjunction in the embodiment of the present application
Attached drawing, the technical scheme in the embodiment of the application is clearly and completely described, it is clear that described embodiment is only
The embodiment of the application a part, instead of all the embodiments.Based on the embodiment in the application, ordinary skill people
Member's every other embodiment obtained without making creative work, all should belong to the model of the application protection
It encloses.
It should be noted that the description and claims of this application and term " first " in above-mentioned attached drawing, "
Two " etc. be to be used to distinguish similar objects, without being used to describe a particular order or precedence order.It should be understood that using in this way
Data be interchangeable under appropriate circumstances, so as to embodiments herein described herein.In addition, term " includes " and " tool
Have " and their any deformation, it is intended that cover it is non-exclusive include, for example, containing a series of steps or units
Process, method, system, product or equipment those of are not necessarily limited to be clearly listed step or unit, but may include without clear
Other step or units listing to Chu or intrinsic for these process, methods, product or equipment.
In this application, term " on ", "lower", "left", "right", "front", "rear", "top", "bottom", "inner", "outside",
" in ", "vertical", "horizontal", " transverse direction ", the orientation or positional relationship of the instructions such as " longitudinal direction " be orientation based on the figure or
Positional relationship.These terms are not intended to limit indicated dress primarily to better describe the application and embodiment
Set, element or component must have particular orientation, or constructed and operated with particular orientation.
Also, above-mentioned part term is other than it can be used to indicate that orientation or positional relationship, it is also possible to for indicating it
His meaning, such as term " on " also are likely used for indicating certain relations of dependence or connection relationship in some cases.For ability
For the those of ordinary skill of domain, the concrete meaning of these terms in this application can be understood as the case may be.
In addition, term " installation ", " setting ", " being equipped with ", " connection ", " connected ", " socket " shall be understood in a broad sense.For example,
It may be a fixed connection, be detachably connected or monolithic construction；It can be mechanical connection, or electrical connection；It can be direct phase
It even, or indirectly connected through an intermediary, or is two connections internal between device, element or component.
For those of ordinary skills, the concrete meaning of above-mentioned term in this application can be understood as the case may be.
It should be noted that in the absence of conflict, the features in the embodiments and the embodiments of the present application can phase
Mutually combination.The application is described in detail below with reference to the accompanying drawings and in conjunction with the embodiments.
As shown in Figure 1, this method includes the following steps, namely S102 to step S110:
Step S102 submits event according to standard Event Processing Interface in asynchronous process scene；
Specifically, an embeddable lightweight asynchronous schedule component to operation system, asynchronous schedule component have a core
Concept event (event), the business scenario of asynchronous process in need a thing can be converted into for component
Part.One or more events refer to the conversion knot by asynchronous schedule component to the business scenario for needing to carry out asynchronous process
Fruit.
Step S104, in event saving interface, by the data storage handled in asynchronous process scene to database；
Specifically, it need to only be handled for the standard Event for needing the Scene realization component of asynchronous process to provide in operation system
Interface, and data are stored in database by the event saving interface that component provides on suitable opportunity, it is subsequent to transfer to group all
Part is completed, very small to the intrusion of operation system, so that it is very small to access cost.
Further include:
Step S106 handles one or more events in the asynchronous schedule component；
Step S108 determines event handling class according to event type, and calls the business according to the event handling class
The event handling class of system；
Step S110 receives the processing result that the operation system returns in the asynchronous schedule component.
It is embedded in asynchronous schedule component in operation system and carries out above-mentioned operation, can located in the asynchronous schedule component
One or the multiple events of batch processing are managed, the event handling class are determined according to event type, then further according to the thing
Part processing class is invoked at the event handling class in the operation system, and receives in the asynchronous schedule component by the business
The processing result that system returns.By the way that the scene for needing asynchronous process to be abstracted into the concept of one or more events, and one
The processing whole process of a or multiple events is packaged in an asynchronous schedule component, is uniformly completed by asynchronous schedule component.
Specifically, batch event to be processed can be fished for by event scheduling, and each is to be processed for circular treatment
Event.Event handling class can be found according to event type, call the event handling class in operation system to event at
Reason.
It can be seen from the above description that the application realizes following technical effect:
By the way of being embedded in asynchronous schedule component in operation system, by asynchronous process scene, according to standard
Event handling interface submits event, in event saving interface, by the data storage handled in asynchronous process scene to database, with
And by handling one or more events in the asynchronous schedule component；Event handling class is determined according to event type,
And the event handling class of the operation system is called according to the event handling class；The industry is received in the asynchronous schedule component
The processing result that business system returns.Achieve the purpose that the scene generalities of asynchronous process, abstract, to realize thing
The whole process standardization of part processing, stylized technical effect, and then solve the high technical problem of asynchronous process cost.
According to the embodiment of the present application, as preferred in the present embodiment, as shown in Fig. 2, in asynchronous process scene, according to
Before standard Event Processing Interface submission event, further includes: asynchronous schedule assembly initialization step, at the beginning of the asynchronous schedule component
Beginningization step includes:
Step S202 starts assembly initialization in operation system charging assembly；
Step S204, the event handling class in component scans operation system, and bind event handling class and event type
Mapping；
Step S206 completes assembly initialization in operation system.
Specifically, the initialization of asynchronous schedule component can be completed by aforesaid operations.Start service in operation system,
The charging assembly in operation system, component are carried out initializing the event handling class started in scanning business business system, then be bound
The mapping of event handling class and event type, initialization component finish.
Preferably, cold and hot data are automatically separated in embodiments herein, data to be processed can be made to protect always
It holds in a controllable range, avoids causing data accumulation excessive as time increases to influence treatment effeciency.
According to the embodiment of the present application, as preferred in the present embodiment, as shown in figure 3, being connect in the asynchronous schedule component
Receiving the processing result that the operation system returns includes:
Step S302, if the operation system return processing result be success, be by event handling status modifier
It handles successfully；
Step S304 converts cold data for event, completes event handling.
Specifically, asynchronous schedule component uses the event storage organization SQL of standard.
The asynchronous schedule component supports individual event processing or scheduling formula processing, if the place that the operation system returns
Event handling status modifier is then to handle successfully the result is that success by reason.The asynchronous schedule component supports single thread or more
Thread scheduling event handling.The cold and hot data of asynchronous schedule component are automatically separated, and for converting cold data for event, are completed
Event handling.
According to the embodiment of the present application, as preferred in the present embodiment, as shown in figure 4, being connect in the asynchronous schedule component
Receiving the processing result that the operation system returns includes:
Step S402, if the operation system return processing result be to retry, be by event handling status modifier
In processing；
Step S404 calculates the processing time next time of event, waits next event calling processing.
Specifically, asynchronous schedule component uses the event storage organization SQL of standard.
The asynchronous schedule component supports individual event processing or scheduling formula processing, if the place that the operation system returns
Reason is the result is that retry, then by event handling status modifier in processing.The asynchronous schedule component supports single thread or multi-thread
The processing of journey scheduling events, further calculates the processing time next time of event, waits next event calling processing.
According to the embodiment of the present application, as preferred in the present embodiment, as shown in figure 5, being connect in the asynchronous schedule component
Receiving the processing result that the operation system returns includes:
Step S502, if the operation system return processing result be failure, be by event handling status modifier
Processing failure；
Step S504 increases the frequency of failure of processing, handles the time next time according to frequency of failure calculating, wherein
The frequency of failure it is more, calculate next time processing time interval it is bigger.
Specifically, scheduling attenuating mechanism when asynchronous schedule component is using exception, while supporting customized decaying strategy.
The asynchronous schedule component supports individual event processing or scheduling formula processing, if the place that the operation system returns
Event handling status modifier is then processing failure the result is that failure by reason.The asynchronous schedule component supports single thread or more
Thread scheduling event handling increases the frequency of failure of processing, handles the time next time according to frequency of failure calculating.
Preferably, by introducing processing failure decaying strategy, it can be retried to avoid meaningless, save server resource.
According to the embodiment of the present application, as preferred in the present embodiment, as shown in fig. 6, asynchronous schedule group further include: alarm
Step, the alarm step include:
Step S602, the frequency of failure for judging that asynchronous schedule component receives in the processing result that the operation system returns are
No is more than processing threshold values；
Step S604, if it is determined that asynchronous schedule component receives the failure time in the processing result that the operation system returns
Number is more than processing threshold values, then sends processing failure and alert and terminate event handling.
Specifically, the asynchronous schedule component supports unsuccessfully to be more than the alarming mechanism for handling threshold values.By judging asynchronous tune
Whether the frequency of failure that degree component receives in the processing result that the operation system returns is more than processing threshold values, if it is determined that asynchronous
It is more than processing threshold values that scheduling component, which receives the frequency of failure in the processing result that the operation system returns, then at event suspension
Reason, event scheduling terminate, and wait next scheduling.The asynchronous schedule component supports customized decaying strategy, and the frequency of failure is not
It can be configured less than permission maximum attempts.
Preferably, by introducing alarming mechanism, when event can not be processed, business can timely be notified to be responsible for
People improves the timeliness found the problem.
According to the embodiment of the present application, as preferred in the present embodiment, as shown in fig. 7, asynchronous schedule group further include: cleaning
Or the step of ArchivalEvent,
Step S702, the processing received in the processing result that the operation system returns according to asynchronous schedule component are successful
Have been converted into the event of cold data；
Step S704 is periodically filed or is cleared up to the cold data in event.
Specifically, the asynchronous schedule component supports data filing and clearing function.
It should be noted that step shown in the flowchart of the accompanying drawings can be in such as a group of computer-executable instructions
It is executed in computer system, although also, logical order is shown in flow charts, and it in some cases, can be with not
The sequence being same as herein executes shown or described step.
Preferably, periodically filed or clearing function by providing cold data, database resource can be saved.
According to the embodiment of the present application, additionally provide a kind of for implementing the asynchronous schedule for operation system of the above method
Device, as shown in figure 8, being embedded in asynchronous schedule component in operation system, which includes: to submit module 10, for asynchronous
It handles in scene, submits event according to standard Event Processing Interface, wherein one or more events refer to through asynchronous tune
Spend conversion results of the component to the business scenario for needing to carry out asynchronous process；Preserving module 20 is used in event saving interface, will
The data storage handled in asynchronous process scene is to database；Further include: processing module 30, in the asynchronous schedule component
The one or more events of middle processing；Calling module 40, for determining event handling class according to event type, and according to described
Event handling class calls the event handling class of the operation system；Return module 50, for being received in the asynchronous schedule component
The processing result that the operation system returns.
In the submission module 10 of the embodiment of the present application specifically, an embeddable lightweight asynchronous schedule to operation system
Component, asynchronous schedule component have the concept of a core event (event), asynchronous process in need business scenario for group
An event can be converted into for part.One or more events refer to different to needing to carry out by asynchronous schedule component
Walk the conversion results of the business scenario of processing.
In the preserving module 20 of the embodiment of the present application specifically, operation system only need to be for needing the scene of asynchronous process
Realize the standard Event Processing Interface that component provides, and the event saving interface for providing data by component on suitable opportunity
It is stored in database, it is subsequent that component is transferred to complete all, it is very small to the intrusion of operation system, so that it is very small to access cost.
It is embedded in operation system in the processing module 30 of the embodiment of the present application, calling module 40 and return module 50 different
Above-mentioned operation is carried out in step scheduling component, can handle one or the multiple things of batch processing in the asynchronous schedule component
Part determines the event handling class according to event type, is then invoked at the operation system further according to the event handling class
In event handling class, and receive the processing result that is returned by the operation system in the asynchronous schedule component.Passing through will
It needs the scene of asynchronous process to be abstracted into the concept of one or more events, and the processing whole process of one or more events is beaten
Packet is uniformly completed in the asynchronous schedule component, by asynchronous schedule component.
Specifically, batch event to be processed can be fished for by event scheduling, and each is to be processed for circular treatment
Event.Event handling class can be found according to event type, call the event handling class in operation system to event at
Reason.
According to the embodiment of the present application, as preferred in the present embodiment, as shown in Figure 9, further includes: initialization module is used
In in operation system charging assembly, start assembly initialization 60；Event handling class in component scans operation system, and bind thing
The mapping of part processing class and event type；Assembly initialization is completed in operation system.
Specifically, the initialization of asynchronous schedule component can be completed by aforesaid operations.Start service in operation system,
The charging assembly in operation system, component are carried out initializing the event handling class started in scanning business business system, then be bound
The mapping of event handling class and event type, initialization component finish.
Preferably, cold and hot data are automatically separated in embodiments herein, data to be processed can be made to protect always
It holds in a controllable range, avoids causing data accumulation excessive as time increases to influence treatment effeciency.
According to the embodiment of the present application, as preferred in the present embodiment, as shown in figure 9, the asynchronous schedule component also wraps
It includes: alarm module 70, for judging that asynchronous schedule component receives the frequency of failure in the processing result that the operation system returns
It whether is more than processing threshold values；If it is determined that asynchronous schedule component receives the failure time in the processing result that the operation system returns
Number is more than processing threshold values, then sends processing failure and alert and terminate event handling；Data filing or cleaning modul 80 are used for basis
Asynchronous schedule component receives the event that the processing in the processing result that the operation system returns successfully has been converted into cold data；
Cold data in event is periodically filed or cleared up.
Specifically, the asynchronous schedule component supports unsuccessfully to be more than the alarming mechanism for handling threshold values.By judging asynchronous tune
Whether the frequency of failure that degree component receives in the processing result that the operation system returns is more than processing threshold values, if it is determined that asynchronous
It is more than processing threshold values that scheduling component, which receives the frequency of failure in the processing result that the operation system returns, then at event suspension
Reason, event scheduling terminate, and wait next scheduling.The asynchronous schedule component supports customized decaying strategy, and the frequency of failure is not
It can be configured less than permission maximum attempts.
Preferably, by introducing alarming mechanism, when event can not be processed, business can timely be notified to be responsible for
People improves the timeliness found the problem.
Specifically, the asynchronous schedule component supports data filing and clearing function.
As shown in Figure 10, be the embodiment of the present application the asynchronous schedule method for operation system realization principle.
Specifically, it need to only be handled for the standard Event for needing the Scene realization component of asynchronous process to provide in operation system
Interface, and data are stored in database by the event saving interface that component provides on suitable opportunity, it is subsequent to transfer to group all
Part is completed, to the intrusion of operation system very small, and access cost is very small.
Asynchronous schedule component is embedded in operation system, scheduling component is used for, according to the event storage organization of standard
(SQL)。
Component is dispatched, supports individual event processing and scheduling formula processing；Component is dispatched, supports single thread or multithreading tune
Spend event handling；Scheduling component supports cold and hot data to be automatically separated；Dispatch scheduling attenuating mechanism when component supports abnormal；Scheduling
Component supports customized decaying strategy；It dispatches component and supports unsuccessfully to be more than the alarming mechanism for handling threshold values；It dispatches component and supports number
According to filing and clearing function.
Insertion type component in the embodiment of the present application is easy integrated with operation system.And need not additionally dispose, it saves
Hardware resource.
Obviously, those skilled in the art should be understood that each module of above-mentioned the application or each step can be with general
Computing device realize that they can be concentrated on a single computing device, or be distributed in multiple computing devices and formed
Network on, optionally, they can be realized with the program code that computing device can perform, it is thus possible to which they are stored
Be performed by computing device in the storage device, perhaps they are fabricated to each integrated circuit modules or by they
In multiple modules or step be fabricated to single integrated circuit module to realize.In this way, the application be not limited to it is any specific
Hardware and software combines.
The foregoing is merely preferred embodiment of the present application, are not intended to limit this application, for the skill of this field
For art personnel, various changes and changes are possible in this application.Within the spirit and principles of this application, made any to repair
Change, equivalent replacement, improvement etc., should be included within the scope of protection of this application.
Claims (10)
1. a kind of asynchronous schedule method for operation system, which is characterized in that asynchronous schedule component is embedded in operation system,
The described method includes:
In asynchronous process scene, event is submitted according to standard Event Processing Interface, wherein one or more events refer to
Conversion results by asynchronous schedule component to the business scenario for needing to carry out asynchronous process；
In event saving interface, by the data storage handled in asynchronous process scene to database；
Further include:
One or more events are handled in the asynchronous schedule component；
Event handling class is determined according to event type, and the event handling of the operation system is called according to the event handling class
Class；
The processing result that the operation system returns is received in the asynchronous schedule component.
2. the asynchronous schedule method according to claim 1 for operation system, which is characterized in that in asynchronous process scene
In, before standard Event Processing Interface submission event, further includes: asynchronous schedule assembly initialization step, the asynchronous tune
Spending assembly initialization step includes:
In operation system charging assembly, start assembly initialization；
Event handling class in component scans operation system, and bind the mapping of event handling class and event type；
Assembly initialization is completed in operation system.
3. the asynchronous schedule method according to claim 1 for operation system, which is characterized in that in the asynchronous schedule
Component receives the processing result that the operation system returns
It is to handle successfully by event handling status modifier if the processing result that the operation system returns is success；
Cold data is converted by event, completes event handling.
4. the asynchronous schedule method according to claim 1 for operation system, which is characterized in that in the asynchronous schedule
Component receives the processing result that the operation system returns
It is in processing by event handling status modifier if the processing result that the operation system returns is to retry；
The processing time next time of calculating event waits next event calling processing.
5. the asynchronous schedule method according to claim 1 for operation system, which is characterized in that in the asynchronous schedule
Component receives the processing result that the operation system returns
It is processing failure by event handling status modifier if the processing result that the operation system returns is failure；
The frequency of failure for increasing processing handles the time according to frequency of failure calculating, wherein the frequency of failure next time
It is more, it is bigger to calculate processing time interval next time.
6. the asynchronous schedule method according to claim 1 for operation system, which is characterized in that asynchronous schedule group is also wrapped
Include: alarm step, the alarm step include:
Whether the frequency of failure for judging that asynchronous schedule component receives in the processing result that the operation system returns is more than processing valve
Value；
If it is determined that it is more than processing valve that asynchronous schedule component, which receives the frequency of failure in the processing result that the operation system returns,
Value, then send processing failure and alert and terminate event handling.
7. the asynchronous schedule method according to claim 1 for operation system, which is characterized in that asynchronous schedule group is also wrapped
It includes: cleaning or the step of ArchivalEvent,
The processing received in the processing result that the operation system returns according to asynchronous schedule component successfully has been converted into cold number
According to event；
Cold data in event is periodically filed or cleared up.
8. a kind of asynchronous schedule device for operation system, which is characterized in that asynchronous schedule component is embedded in operation system,
Described device includes:
Module is submitted, for submitting event according to standard Event Processing Interface, wherein one or more in asynchronous process scene
A event refers to the conversion results by asynchronous schedule component to the business scenario for needing to carry out asynchronous process；
Preserving module is used in event saving interface, by the data storage handled in asynchronous process scene to database；
Further include:
Processing module, for handling one or more events in the asynchronous schedule component；
Calling module for determining event handling class according to event type, and calls the business according to the event handling class
The event handling class of system；
Return module, for receiving the processing result that the operation system returns in the asynchronous schedule component.
9. the asynchronous schedule device according to claim 8 for operation system, which is characterized in that further include: initialization
Module is used for
In operation system charging assembly, start assembly initialization；
Event handling class in component scans operation system, and bind the mapping of event handling class and event type；
Assembly initialization is completed in operation system.
10. the asynchronous schedule device according to claim 8 for operation system, which is characterized in that the asynchronous schedule
Component further include:
Alarm module is for judging that asynchronous schedule component receives the frequency of failure in the processing result that the operation system returns
No is more than processing threshold values；
If it is determined that it is more than processing valve that asynchronous schedule component, which receives the frequency of failure in the processing result that the operation system returns,
Value, then send processing failure and alert and terminate event handling；
Data filing or cleaning modul, for being received in the processing result that the operation system returns according to asynchronous schedule component
Processing successfully has been converted into the event of cold data；
Cold data in event is periodically filed or cleared up.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910583150.2A CN110321211B (en) | 2019-06-27 | 2019-06-27 | Asynchronous scheduling method and device for service system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910583150.2A CN110321211B (en) | 2019-06-27 | 2019-06-27 | Asynchronous scheduling method and device for service system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110321211A true CN110321211A (en) | 2019-10-11 |
| CN110321211B CN110321211B (en) | 2020-05-12 |
Family
ID=68121923
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910583150.2A Active CN110321211B (en) | 2019-06-27 | 2019-06-27 | Asynchronous scheduling method and device for service system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110321211B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112435004A (en) * | 2020-11-20 | 2021-03-02 | 金蝶软件（中国）有限公司 | Method and device for realizing service flow processing |
| CN114710569A (en) * | 2022-03-11 | 2022-07-05 | 珠海派诺科技股份有限公司 | Self-scaling TCP link maintenance method, system and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101425024A (en) * | 2008-10-24 | 2009-05-06 | 中国移动通信集团山东有限公司 | Multitasking method and device |
| US20100223620A1 (en) * | 2009-02-27 | 2010-09-02 | Yahoo! Inc. | Smart recovery of asynchronous processing |
| CN101882161A (en) * | 2010-06-23 | 2010-11-10 | 中国工商银行股份有限公司 | Application level asynchronous task scheduling system and method |
| CN106598705A (en) * | 2015-10-15 | 2017-04-26 | 阿里巴巴集团控股有限公司 | Asynchronous task scheduling method, device and system and electronic equipment |
| CN108073447A (en) * | 2016-11-15 | 2018-05-25 | 平安科技（深圳）有限公司 | Based on the asynchronous insurance task processing method and device under more applying |
| CN109118344A (en) * | 2018-07-06 | 2019-01-01 | 阿里巴巴集团控股有限公司 | A kind of business retries method and apparatus |
-
2019
- 2019-06-27 CN CN201910583150.2A patent/CN110321211B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101425024A (en) * | 2008-10-24 | 2009-05-06 | 中国移动通信集团山东有限公司 | Multitasking method and device |
| US20100223620A1 (en) * | 2009-02-27 | 2010-09-02 | Yahoo! Inc. | Smart recovery of asynchronous processing |
| CN101882161A (en) * | 2010-06-23 | 2010-11-10 | 中国工商银行股份有限公司 | Application level asynchronous task scheduling system and method |
| CN106598705A (en) * | 2015-10-15 | 2017-04-26 | 阿里巴巴集团控股有限公司 | Asynchronous task scheduling method, device and system and electronic equipment |
| CN108073447A (en) * | 2016-11-15 | 2018-05-25 | 平安科技（深圳）有限公司 | Based on the asynchronous insurance task processing method and device under more applying |
| CN109118344A (en) * | 2018-07-06 | 2019-01-01 | 阿里巴巴集团控股有限公司 | A kind of business retries method and apparatus |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112435004A (en) * | 2020-11-20 | 2021-03-02 | 金蝶软件（中国）有限公司 | Method and device for realizing service flow processing |
| CN114710569A (en) * | 2022-03-11 | 2022-07-05 | 珠海派诺科技股份有限公司 | Self-scaling TCP link maintenance method, system and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110321211B (en) | 2020-05-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108965164B (en) | Service request retransmission method and device based on message queue and readable storage medium | |
| CN102483705B (en) | User-level interrupt mechanism for multi-core architectures | |
| CN110321211A (en) | Asynchronous schedule method and device for operation system | |
| CN109992414A (en) | A kind of task processing method and device based on thread pool | |
| CN102387265A (en) | Calling connection method and calling platform | |
| CN109445954A (en) | A kind of execution method, terminal device and the storage medium of timed task | |
| CN103136047A (en) | Multithreading management method and framework | |
| CN105931112A (en) | Cross-border transaction liquidation method and system | |
| CN104052677A (en) | Soft load balancing method and apparatus of single data source | |
| CN208940010U (en) | A kind of intranet and extranet synchronization system | |
| CN107657326A (en) | A kind of matching system and matching process of On-line matching user and attendant | |
| CN110365517A (en) | Data processing method, device, storage medium and computer equipment | |
| CN100535864C (en) | Method of invalid time over message under system process scheduling | |
| CN104683460A (en) | Communication method, device and server for Internet of things | |
| CN110389976A (en) | A kind of dispatching method and device of multi-interface data | |
| CN1373954A (en) | Advanced service architecture for next generation network services and intelligent data network router | |
| CN107369088A (en) | The treating method and apparatus of account transaction | |
| CN107566297A (en) | Internet of Things service processing method and system | |
| CN107220129A (en) | Communication means and system between a kind of software module | |
| CN106933681A (en) | A kind of many object blocking methods and its system | |
| WO2010017688A1 (en) | Device of using the push mode to realize the non-real-time media routing and method thereof | |
| CN101136766B (en) | Task scheduling method for telecommunication network management system | |
| CN109618407A (en) | The service registration method and system based on ZigBee equipment of compatible TCP/IP network | |
| CN110493735A (en) | A kind of SMS processing method and device | |
| CN112134373A (en) | Metal foreign matter detection method, wireless charging equipment and receiving system |
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 |