This document outlines an agenda for a MuleSoft Day4 session on Mule flows. It defines Mule flows as how Mule applications are built and processed, with messages received by inbound endpoints and then routed through flows and subflows for processing. The document notes flows can process messages synchronously or asynchronously and lists advantages like asynchronous flows for long tasks and breaking applications into smaller flows for readability. It concludes by stating the next session will cover flow examples and variables.

1. ABHISHEK JAIN
MuleSoft Day4
Mule Flow

2. Agenda
Mule Flow
High Level Picture
Type of Flows
Advantages
Topic for next session
Reference

3. Mule Flow
Mule applications are built around one or more flows. A Mule
application begins processing a message it is received by an
inbound endpoint in a flow. This flow can then either implement all
processing stages, or route the message to other flows or subflows
to perform specific tasks. Relative to the flow which triggered its
execution, a flows and sub flows can process messages
either synchronously or asynchronously
Ref:
https://developer.mulesoft.com/docs/display/current/Flows+and+Subflows

4. High Level Picture

5. Type of Flows

6. Advantages
-Asynchronous flow can perform time consuming tasks
-Flows can maintain their own threading and exception strategies
-Break large application into small for readable perspective
-Less documentation
-Self Explanatory

7. Next Session
Examples of Mule Flow
Mule Variables

8. References
www.mulesoft.com
Mule in Action

9. Thank You

10. Thank You