1
00:00:00,270 --> 00:00:04,870
In this video, we are going to learn a list of function workflow types.

2
00:00:04,890 --> 00:00:09,510
These are the standard and express workflows when we create a state machine.

3
00:00:09,540 --> 00:00:13,590
We should select a type of the state machine which are the standard and X race.

4
00:00:13,620 --> 00:00:18,180
In both cases, we define our state machine with using the Amazon State language.

5
00:00:18,810 --> 00:00:21,520
So the first part is the standard workflows.

6
00:00:21,540 --> 00:00:27,630
We can choose a standard workflow for processing that are long running and require the human intervention

7
00:00:27,630 --> 00:00:30,930
tasks or workflows in the standard workflows.

8
00:00:31,080 --> 00:00:35,520
They are the ideal for long running, durable and auditable workflows.

9
00:00:36,120 --> 00:00:42,900
They can run up for up to a year and we can retrieve the full execution history using the step function

10
00:00:42,900 --> 00:00:43,500
API.

11
00:00:43,530 --> 00:00:50,910
Some that workflows works as exactly one model and the another type is express workflows.

12
00:00:51,060 --> 00:00:57,420
Express workflows are well suited for short running about fewer than 5 minutes high volume processes.

13
00:00:57,900 --> 00:01:04,440
Express workflows are ideal for high volume event processing workloads, for example, Iot data ingestion,

14
00:01:04,470 --> 00:01:08,780
streaming data processing and transformation and mobile application backends.

15
00:01:09,300 --> 00:01:12,030
They can run up for up to 5 minutes.

16
00:01:12,060 --> 00:01:20,520
Express Workflows works as a at least once model, and it is possible to run one more time in the express

17
00:01:20,520 --> 00:01:21,390
workflows.

18
00:01:22,770 --> 00:01:28,230
Also, there are two types of express workflows that you can choose asynchronous express workflow and

19
00:01:28,230 --> 00:01:30,000
synchronous express workflow.

20
00:01:30,120 --> 00:01:35,460
If you talk about the asynchronous express workflow, it basically returned confirmation that the workflow

21
00:01:35,460 --> 00:01:36,360
was started.

22
00:01:36,360 --> 00:01:40,980
But don't wait for the workflow to complete in order to get the result.

23
00:01:41,010 --> 00:01:43,950
We have to pull the service cloud workflows.

24
00:01:44,070 --> 00:01:50,250
Asynchronous express workflows can be used when you don't require immediate response output, for example,

25
00:01:50,250 --> 00:01:54,720
messaging services or data processing that other services don't depend on.

26
00:01:55,020 --> 00:02:00,630
Asynchronous express workflows can be started in response to an event by nested workflow in the step

27
00:02:00,630 --> 00:02:03,450
function or using start execution API call.

28
00:02:03,960 --> 00:02:06,900
And there is also synchronous step function workflow.

29
00:02:06,930 --> 00:02:11,880
It is basically start a workflow, wait until it completes, then return the result.

30
00:02:11,910 --> 00:02:18,240
Synchronous Express workflows can be used to orchestrate microservices and allow you to develop applications

31
00:02:18,240 --> 00:02:23,400
without need to develop additional code to handle errors, retries or execution.

32
00:02:23,400 --> 00:02:24,450
Parallel tasks.

33
00:02:24,690 --> 00:02:30,510
Synchronous Express workflows can be invoked from the Amazon API gateway a the way is lambda or using

34
00:02:30,510 --> 00:02:33,780
the starting execution API call from the step function.
