CN111061458A - Application creation system with open pipeline architecture - Google Patents
Application creation system with open pipeline architecture Download PDFInfo
- Publication number
- CN111061458A CN111061458A CN201910959231.8A CN201910959231A CN111061458A CN 111061458 A CN111061458 A CN 111061458A CN 201910959231 A CN201910959231 A CN 201910959231A CN 111061458 A CN111061458 A CN 111061458A
- Authority
- CN
- China
- Prior art keywords
- task
- task execution
- application
- execution unit
- unit
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Abstract
The invention discloses an application creation system with an open type pipeline architecture, which comprises a task creation unit, a plurality of primary task execution units and secondary task execution units, wherein the task creation unit is used for creating a task; a plurality of secondary task execution units are sequentially coupled to form a task queue, and each primary task execution unit corresponds to one task queue; the task creating unit receives an application creating request sent by a client, divides an application to be created into a plurality of subtasks and respectively issues the subtasks to the primary task execution unit; the first-level task execution unit monitors the subtasks distributed by the task creation unit, divides the subtasks into a plurality of stage tasks according to the execution logic of the subtasks, and sequentially sends the stage tasks to each second-level task execution unit through the task queue; the execution of the next stage task is triggered by chain transmission among the multiple secondary task execution units; the invention supports the user to expand the characteristic application according to the service characteristic of the user, does not need to change the existing pipeline architecture, and reduces the workload of service expansion.
Description
Technical Field
The invention belongs to the technical field of computer software, and particularly relates to an application creation system with an open pipeline architecture.
Background
Development operation and maintenance integration (DevOps) is a culture, sport or practice that attaches importance to the communication and cooperation between software developers (Dev) and IT operation and maintenance technicians (Ops). Through the automatic flow of 'software delivery' and 'architecture change', the software can be constructed, tested and released more quickly, frequently and reliably, and the DevOps can be regarded as the intersection of development (software engineering), technical operation and Quality Assurance (QA).
With the development of new economy of the internet, the continuous evolution of new technologies such as cloud computing, internet of things, big data, block chains, AI, 5G, and the like, how to easily cope with rapidly changing business requirements, make full use of existing IT resources and reduce operation cost, how to centralize, standardize, manage, and rapidly copy precipitated solutions, and the like, become a serious problem that enterprises need to solve urgently. The 2018 DevOps status report, published by DORA in collaboration with Google Cloud, states that: in 2014, only 16% of survey participants represented themselves at the DevOps team. And at 2018 this number has grown to 27%. Research in DORA emphasizes the critical practices for technology transformation, including versioning, automated deployment, persistent integration (CI), backbone-based development, and loosely-coupled architectures. Gartner magic quadrant report puts DevOps into importance in several fields (e.g., automated testing, automated operations and maintenance) and generalizes the development trend of IT information-based architectures to a gradually decoupled process.
Mainstream fortune dimension integration platform's pipeline design, more common have the mode that adopts dynamic concatenation pipeline script, be divided into a plurality of stages for the pipeline task, every stage carries out the task through serial or parallel mode, whole pipeline is called pipeline job, colludes the stage of arranging the custom through the end user and comes the dynamic final pipeline job of assembling out, and this kind of mode has following several drawbacks:
1. the complexity of the Pipeline jobgrammar determines the high probability of errors in the execution of the finally assembled Pipeline task, and the influence of preconditions in the stages possibly introduced on the Pipeline structure needs to be comprehensively considered, such as: a certain stage needs a basic environment to be defined in a pipeline header, but other stages do not need the definition, and the stage is optional;
2. the complexity of error rollback in the integral pipeline execution mode is exponentially multiple of stages, and as a plurality of stages in the pipeline are formed by dynamically splicing scripts, namely adjacent stages are closely related, once a certain stage makes an error to rollback, the normal operation of other stages on the pipeline is influenced;
3. due to the fact that the complexity of the Pipeline script for the dynamic splicing of the Pipeline and the error rollback is high, the expansibility of the Pipeline job is poor, and the later maintenance cost is high.
Disclosure of Invention
Aiming at least one defect or improvement requirement in the prior art, the invention provides an application creation system and an application creation method with an open pipeline architecture, which support a client to flexibly customize and freely expand application functions according to the service characteristics of the client, and improve the concurrent development efficiency of products and the capability of third-party product docking and integration.
To achieve the above object, according to one aspect of the present invention, there is provided an application creation system having an open pipeline architecture, including a task creation unit, a plurality of primary task execution units, and a secondary task execution unit; a plurality of secondary task execution units are sequentially coupled to form a task queue, and each primary task execution unit corresponds to one task queue;
the task creating unit is used for receiving an application creating request sent by a client, splitting an application to be created into a plurality of subtasks according to the application creating request and respectively issuing the subtasks to the primary task execution unit;
the primary task execution units monitor the subtasks distributed by the task creation unit through the registered behavior interfaces, and each primary task execution unit divides the subtasks into a plurality of stage tasks according to the execution logic of the subtasks and sequentially sends the stage tasks to each secondary task execution unit through the task queues;
each secondary task execution unit correspondingly executes a stage task, and the execution of the next stage task is triggered by chain transmission among the secondary task execution units.
Preferably, in the application creation system, when receiving an application expansion request sent by a client, the task creation unit creates a new primary task execution unit according to the application expansion request and issues an application to be expanded as a subtask to the new primary task execution unit.
Preferably, in the application creation system, when receiving a subtask expansion request sent by a client, the task creation unit issues a subtask to be expanded to a corresponding primary task execution unit according to the subtask expansion request;
and the primary task execution unit inserts a new secondary task execution unit into the task queue and takes the subtask to be expanded as a stage task to be issued to the newly-built secondary task execution unit.
Preferably, in the application creation system, the behavior interface of the primary task execution unit includes a first execution interface; the behavior interface of the secondary task execution unit comprises a second execution interface and a withdrawal interface.
Preferably, in the application creation system, the task creation unit calls the first-level task execution unit through the first execution interface based on a multi-thread manner to execute the sub-tasks;
and the primary task execution unit calls the secondary task execution unit through the second execution interface to enable the secondary task execution unit to execute the stage task.
Preferably, in the application creation system, when an error occurs in the execution process of any subtask, the primary task execution unit corresponding to the subtask reversely withdraws each stage task according to the coupling sequence of the secondary task execution units in the task queue, and the withdrawal of the stage task is realized based on the withdrawal interface.
Preferably, in the application creation system, in the stage task withdrawal process, the rollback of the previous stage task is triggered by chain transmission between the second-stage task execution units.
Preferably, in the application creation system, a plurality of the primary task execution units may execute their respective corresponding subtasks in a serial or parallel manner.
Preferably, in the application creation system, the application creation request includes an application name and an execution parameter set of the application.
In general, compared with the prior art, the above technical solution contemplated by the present invention can achieve the following beneficial effects:
(1) the application creation system with the open type pipeline architecture realizes the unified issuing and rollback of tasks through the centralized event delegation of the task creation units, each primary task execution unit customizes own sub-processes through a task queue, and the primary task execution units independently receive and process the sub-tasks broadcasted by the task creation units; the task queue corresponding to the primary task execution unit supports insertion and removal operations, a user can insert the secondary task execution unit into the existing task queue according to the service characteristics of the user to expand the characteristic application of the user, and the customization capability is strong.
(2) According to the application creation system with the open type pipeline architecture, the application creation request sent by the client is decomposed into each independent and closed subtask which can be executed by a plurality of step-by-step units, the concurrency capability of the subtask can be horizontally expanded in a distributed mode by adding the primary task execution unit, the service logicality of the subtask can be longitudinally expanded by inserting the secondary task execution unit, the expansibility is good, the later maintenance is facilitated, and the maintenance cost is reduced.
(3) According to the application creation system with the open pipeline architecture, the loose-coupling open pipeline architecture is arranged among the task creation unit, the primary task execution units and the secondary task execution units, and the open pipeline architecture ensures the independence and the pluggable performance of each primary task execution unit and the closed-loop integrity of the secondary task execution units, so that the parallel and serial flexibility of subtasks is ensured; compared with the traditional pipeline architecture, the pipeline architecture can improve the cycle efficiency of pipeline execution, and can ensure independent rollback and selective full rollback of the subtasks under abnormal conditions.
(4) The application creation system with the open type pipeline architecture provided by the invention realizes the control of all the links of the pipeline in a parallel and serialized manner, ensures the controllability of the dependence between the links of the pipeline on one hand, and improves the concurrency performance of the product on the other hand.
Drawings
Fig. 1 is a schematic diagram illustrating an application creation system with an open pipeline architecture according to an embodiment of the present invention;
fig. 2 is a topology diagram of task decomposition and issue in an application creation process according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. In addition, the technical features involved in the embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.
Fig. 1 is a schematic diagram illustrating an application creation system with an open pipeline architecture according to an embodiment of the present invention; as shown in fig. 1, the application creation system includes a task creation unit, a plurality of primary task execution units, and a secondary task execution unit; a plurality of secondary task execution units are sequentially coupled to form a task queue, each primary task execution unit corresponds to one task queue, and the secondary task execution unit at the head of the task queue is coupled with the primary task execution unit;
the task creating unit is used for receiving an application creating request sent by the client, splitting an application to be created into a plurality of subtasks according to the application creating request and respectively issuing the subtasks to the primary task execution unit; the application creating request comprises an application name and an application execution parameter set;
the primary task execution units monitor the subtasks distributed by the task creation unit through the registered behavior interfaces, and each primary task execution unit divides the subtasks into a plurality of stage tasks according to the execution logic of the subtasks and sequentially sends the stage tasks to each secondary task execution unit through the task queues;
each secondary task execution unit correspondingly executes a stage task, and the execution of the next stage task is triggered by chain transmission among the secondary task execution units.
The number of the secondary task execution units in the task queues corresponding to different primary task execution units may be equal or different, depending on the logic steps required when the sub-tasks accepted by the primary task execution units are executed.
In this embodiment, the task creating unit splits the application creating task into a plurality of independent subtasks and performs centralized publishing/pushing, each subtask has a unique ID, and each primary task execution unit is delegated to process each subtask; the primary task execution units monitor the subtasks issued by the task creation unit in an interface registration mode, and the primary task execution units are independent to each other and cooperate with each other to complete the delegated task; the task creating unit may control the plurality of primary task execution units to execute the respective corresponding subtasks in a serial or parallel manner.
Each primary task execution unit is provided with a task queue consisting of a plurality of secondary task execution units, and the primary task execution units divide the received subtasks into a plurality of stage tasks; the stage tasks are closely related in business logic and need to be executed by the corresponding secondary task execution units in sequence according to the execution logic of the subtasks; referring to fig. 1, a primary task execution unit splits its subtasks into a plurality of stage tasks and sends the plurality of stage tasks to a first secondary task execution unit directly coupled to the primary task execution unit, the first secondary task execution unit executes the first stage task and sends the remaining stage tasks to a second secondary task execution unit after the execution is completed, the second secondary task execution unit executes the second stage task and sends the remaining stage tasks to a third secondary task execution unit after the execution is completed, and according to the process, all the stage tasks are distributed completely; and the execution of the next stage task is triggered by chain transmission among the secondary task execution units, and the multiple stage tasks are processed and executed asynchronously.
When an application expansion request sent by a client is received, a task creating unit creates one or more primary task execution units according to the application expansion request, and issues an application to be expanded as a subtask to the newly-created primary task execution unit; the new primary task execution unit is created only by registering the behavior interface, the expansion capability is strong, a user can perform service expansion according to self requirements in the application development or later operation and maintenance process without changing the existing pipeline architecture, and the workload of application expansion is greatly reduced.
When a subtask expansion request sent by a client is received, a task creating unit issues a subtask to be expanded to a corresponding primary task execution unit according to the subtask expansion request; and the primary task execution unit inserts one or more secondary task execution units into the task queue, and issues the subtask to be expanded as a stage task to the newly-built secondary task execution unit. The new secondary task execution unit is created only by registering a behavior interface, the task queue supports insertion and deletion operations, customization capability is strong, a user is supported to expand own characteristic application in the existing pipeline architecture according to own service characteristics, the existing pipeline architecture does not need to be changed, and workload of service expansion is greatly reduced.
The task creating unit, the primary task execution unit and the secondary task execution unit all realize the issuing and execution of tasks through registering behavior interfaces, wherein the registered behavior interfaces of the primary task execution unit comprise a first execution interface; the task creating unit is coupled with each first-level task execution unit through a first execution interface, and the task creating unit calls the first-level task execution unit through the first execution interface based on a multithreading mode to enable the first-level task execution unit to execute the subtasks;
the behavior interface registered by the secondary task execution unit comprises a second execution interface and a withdrawal interface; the first-stage task execution units are coupled with the second-stage task execution units and adjacent second-stage task execution units through second execution interfaces, the first-stage task execution units call the second-stage task execution units directly coupled with the first-stage task execution units through the second execution interfaces so as to enable the first-stage task execution units to execute stage tasks, and the adjacent second-stage task execution units trigger the execution of next-stage tasks through the second execution interfaces.
When an error occurs in the execution process of any subtask, the primary task execution unit corresponding to the subtask reversely withdraws each stage task according to the coupling sequence of the secondary task execution units in the task queue, and the withdrawal of the stage task is realized based on the withdrawal interface; in the stage task withdrawing process, the rollback of the previous stage task is triggered by chain transmission among all the second-stage task execution units.
In the embodiment, unified issuing and rollback of tasks are realized through centralized event delegation of the task creating units, each primary task executing unit customizes own sub-processes through a task queue, and the primary task executing units independently receive and process the sub-tasks broadcast by the task creating units; the task creation unit supports pre-receive (preposition), do (process) and post-receive (post) multi-section hook event registration, and has strong expansion capability; the task queue corresponding to the primary task execution unit supports insertion and removal operations, a user can insert the secondary task execution unit into the existing task queue according to the service characteristics of the user to expand the characteristic application of the user, and the customization capability is strong. The embodiment realizes the control of all the links of the production line in parallel and in serialization, on one hand, the controllability of dependence among the links of the production line is ensured, and on the other hand, the concurrency performance of the product is improved.
The following describes the application creation system with an open pipeline architecture provided by the present application through a specific application creation case; fig. 2 is a topological diagram of task tapping and issuing in the application creation process provided in this embodiment, and as shown in fig. 2, when a client initiates a request for creating an application, a task creation unit decomposes the application to be created into a plurality of independent subtasks, such as an "a-creation warehouse", "b-creation automation task", "c-creation deployment environment", and the like, and issues each subtask to a primary task execution unit, so that each primary task execution unit executes one subtask correspondingly; taking the subtask "a-created warehouse" as an example for explanation, the primary task execution unit subdivides the subtask "a-created warehouse" into a plurality of step functions with strong business relevance, such as: "a.1-creating code base", "a.2-prefabricating basic code", "a.3-registering tangent function", etc.;
in response to the demands of the extended application by the customer, for example: the client proposes to use the on-line IDE for development, and the task creating unit registers the extended application'd-IDE environment preparation' as a subtask delegated by the task creating unit; when dealing with the needs of a client to expand any one of the subtasks, for example: when a client issues a task and notifies a corresponding group member after proposing a requirement for creating an application, a step of 'a.4-development task allocation' is inserted, and a task creating unit firstly issues a subtask to be expanded 'a.4-development task allocation' to a corresponding primary task execution unit; the first-level task execution unit inserts the step of 'a.4-development task allocation' into the task queue.
The application creation system with the open type pipeline architecture realizes the unified issuing and rollback of tasks through the centralized event delegation of the task creation units, each primary task execution unit customizes own sub-processes through a task queue, and the primary task execution units independently receive and process the sub-tasks broadcasted by the task creation units; the task queue corresponding to the primary task execution unit supports insertion and removal operations, a user can insert the secondary task execution unit into the existing task queue according to the service characteristics of the user to expand the characteristic application of the user, and the customization capability is strong. The concurrency capability of the subtasks can be horizontally expanded in a distributed mode by adding the primary task execution unit, the business logicality of the subtasks can be longitudinally expanded by inserting the secondary task execution unit, the expansibility is good, the later maintenance is facilitated, and the maintenance cost is reduced.
It will be understood by those skilled in the art that the foregoing is only a preferred embodiment of the present invention, and is not intended to limit the invention, and that any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (9)
1. An application creation system with an open pipeline architecture is characterized by comprising a task creation unit, a plurality of primary task execution units and a secondary task execution unit; a plurality of secondary task execution units are sequentially coupled to form a task queue, and each primary task execution unit corresponds to one task queue;
the task creating unit is used for receiving an application creating request sent by a client, splitting an application to be created into a plurality of subtasks according to the application creating request and respectively issuing the subtasks to the primary task execution unit;
the primary task execution units monitor the subtasks distributed by the task creation unit through the registered behavior interfaces, and each primary task execution unit divides the subtasks into a plurality of stage tasks according to the execution logic of the subtasks and sequentially sends the stage tasks to each secondary task execution unit through the task queues;
each secondary task execution unit correspondingly executes a stage task, and the execution of the next stage task is triggered by chain transmission among the secondary task execution units.
2. The application creation system of claim 1, wherein when receiving an application expansion request sent by a client, the task creation unit creates a new primary task execution unit according to the application expansion request and issues an application to be expanded as a subtask to the newly created primary task execution unit.
3. The application creation system of claim 2, wherein when receiving a subtask expansion request sent by a client, the task creation unit issues a subtask to be expanded to a corresponding primary task execution unit according to the subtask expansion request;
and the primary task execution unit inserts a new secondary task execution unit into the task queue and takes the subtask to be expanded as a stage task to be issued to the newly-built secondary task execution unit.
4. The application creation system of any of claims 1-3, wherein the behavior interface of the primary task execution unit comprises a first execution interface; the behavior interface of the secondary task execution unit comprises a second execution interface and a withdrawal interface.
5. The application creation system of claim 4, wherein the task creation unit invokes a primary task execution unit to execute a subtask through the first execution interface based on multithreading;
and the primary task execution unit calls the secondary task execution unit through the second execution interface to enable the secondary task execution unit to execute the stage task.
6. The application creation system according to claim 1 or 5, wherein when an error occurs in the execution process of any one of the subtasks, the primary task execution unit corresponding to the subtask reversely withdraws the stage tasks according to the coupling order of the secondary task execution units in the task queue.
7. The application creation system of claim 6, wherein during the withdrawal of a stage task, the rollback of a previous stage task is triggered by chain transfer between the execution units of the secondary tasks.
8. The application creation system according to claim 1 or 7, wherein a plurality of the primary task execution units can execute respective corresponding subtasks in a serial or parallel manner.
9. The application creation system of claim 8, wherein the create application request includes an application name, a set of execution parameters for the application.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910959231.8A CN111061458A (en) | 2019-10-10 | 2019-10-10 | Application creation system with open pipeline architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910959231.8A CN111061458A (en) | 2019-10-10 | 2019-10-10 | Application creation system with open pipeline architecture |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111061458A true CN111061458A (en) | 2020-04-24 |
Family
ID=70298353
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910959231.8A Pending CN111061458A (en) | 2019-10-10 | 2019-10-10 | Application creation system with open pipeline architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111061458A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112036677A (en) * | 2020-06-08 | 2020-12-04 | 宁波志成信息技术有限公司 | Multi-level task scheduling method and device and storage medium |
| CN112766889A (en) * | 2021-01-10 | 2021-05-07 | 武汉乐谷在线科技有限公司 | Work task dynamic classification management method and device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104462370A (en) * | 2014-12-09 | 2015-03-25 | 北京百度网讯科技有限公司 | Distributed task scheduling system and method |
| CN104572261A (en) * | 2014-12-17 | 2015-04-29 | 北京可思云海科技有限公司 | Method for dynamically generating reminding information |
| CN105653365A (en) * | 2016-02-22 | 2016-06-08 | 青岛海尔智能家电科技有限公司 | Task processing method and device |
| CN105700958A (en) * | 2016-01-07 | 2016-06-22 | 北京京东尚科信息技术有限公司 | Method and system for automatic splitting of task and parallel execution of sub-task |
| CN106528295A (en) * | 2016-11-07 | 2017-03-22 | 广州华多网络科技有限公司 | System task scheduling method and device |
-
2019
- 2019-10-10 CN CN201910959231.8A patent/CN111061458A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104462370A (en) * | 2014-12-09 | 2015-03-25 | 北京百度网讯科技有限公司 | Distributed task scheduling system and method |
| CN104572261A (en) * | 2014-12-17 | 2015-04-29 | 北京可思云海科技有限公司 | Method for dynamically generating reminding information |
| CN105700958A (en) * | 2016-01-07 | 2016-06-22 | 北京京东尚科信息技术有限公司 | Method and system for automatic splitting of task and parallel execution of sub-task |
| CN105653365A (en) * | 2016-02-22 | 2016-06-08 | 青岛海尔智能家电科技有限公司 | Task processing method and device |
| CN106528295A (en) * | 2016-11-07 | 2017-03-22 | 广州华多网络科技有限公司 | System task scheduling method and device |
Non-Patent Citations (1)
| Title |
|---|
| 潘建南: "Fork/Join框架解析", 《HTTPS://BLOG.CSDN.NET/PANGE1991/ARTICLE/DETAILS/85235006》 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112036677A (en) * | 2020-06-08 | 2020-12-04 | 宁波志成信息技术有限公司 | Multi-level task scheduling method and device and storage medium |
| CN112766889A (en) * | 2021-01-10 | 2021-05-07 | 武汉乐谷在线科技有限公司 | Work task dynamic classification management method and device |
| CN112766889B (en) * | 2021-01-10 | 2023-06-20 | 武汉乐谷在线科技有限公司 | Dynamic classification management method and device for work tasks |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108304271B (en) | Distributed transaction manager and management method under micro-service architecture | |
| CN112379995B (en) | DAG-based unitized distributed scheduling system and method | |
| US7174381B2 (en) | Parallel computing system, method and architecture | |
| EP2442265A2 (en) | Method and server cluster for MapReducing FLOW services and large documents | |
| CN110825511A (en) | Operation flow scheduling method based on modeling platform model | |
| CN110362315B (en) | DAG-based software system scheduling method and device | |
| JP2017534131A (en) | Compiling program specifications based on graphs | |
| CN111061458A (en) | Application creation system with open pipeline architecture | |
| CN108255592A (en) | A kind of Quartz clusters timing task processing system and method | |
| JPH03230225A (en) | Process dispersion system | |
| CN111209092A (en) | Distributed transaction processing method based on Saga mode | |
| Samuel et al. | Test sequence generation from UML sequence diagrams | |
| CN104243617A (en) | Task scheduling method and system facing mixed load in heterogeneous cluster | |
| CN110569113A (en) | Method and system for scheduling distributed tasks and computer readable storage medium | |
| CN106681820A (en) | Message combination based extensible big data computing method | |
| CN114756357B (en) | Non-blocking distributed planned task scheduling method based on JVM (Java virtual machine) | |
| CN110134533B (en) | System and method capable of scheduling data in batches | |
| CN109756565A (en) | A kind of Multitask Data method for pushing based on statistical form | |
| CN111930492B (en) | Task flow scheduling method and system based on decoupling task data model | |
| CN113723931B (en) | Workflow modeling method suitable for multi-scale high-flux material calculation | |
| CN111612155A (en) | Distributed machine learning system and communication scheduling method suitable for same | |
| Lastovetsky | Parallel testing of distributed software | |
| CN111611089A (en) | Asynchronous declaration type micro-service scheduling method | |
| CN115056234A (en) | RPA controller scheduling method and system based on event driving and infinite state machine | |
| CN114237858A (en) | Task scheduling method and system based on multi-cluster network |
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 | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20200424 |
|
| WD01 | Invention patent application deemed withdrawn after publication |