CloudFlow allows you to create a workflow in standard mode or in express mode. This topic describes how to select a mode to create workflows for your business.
Terms
Standard mode: This mode is suitable for conventional offline workflow orchestration and execution. This mode supports the persistent storage of execution step status and the execution status circulation of long-running workflows.
Quick mode: This mode is suitable for common online workflow orchestration and quasi-real-time workflow orchestration in latency sensitive and load intensive scenarios such as microservices API orchestration, glue layer API orchestration, and stream processing.
Mode comparisons
Item | Standard mode | Express mode |
Maximum execution duration | 1 year | 5 minutes |
Flow start rate | 100 QPS | 1,000 QPS by default. If you require a higher QPS, submit a ticket. |
Concurrency | 10000 | 10,000 by default. If you require a higher concurrency, submit a ticket. |
Execution history and observability | API operations such as querying and listing are supported. The system records all execution information. | Queries in Simple Log Service are planed to be supported. Queries only by calling API operations are supported during public preview. |
Execution syntax | Asynchronous executions. The At Least Once rule is followed by the executions. Data is not lost during the executions but data may be processed repeatedly in special conditions. | Synchronous executions. Retries are performed by default upon system errors. You can configure retries on clients based on your business requirements. |
Service integration | All integration methods are supported. For more information, see Overview. | All integration methods are supported. For more information, see Overview. |
Integration modes | The following modes are supported. For more information, see Integration modes.
| Only RequestComplete is supported. |