All three Flow types can be referenced from a Flow Reference component.
Flow is a message processing block that has its own processing strategy and exception handling strategy. Used in integration tasks, data processing, connecting applications, event processing, etc.
Subflow always processes messages synchronously but inherits processing strategy and exception handling strategy from the calling flow. It can be used to split common logic and be reused by other flows.
Private flow does not have source define. It can be synchronous or asynchronous based on the processing strategy selected. Also, they have their own exception handling strategy. Allows you to define different threading profile.
====
Flow is a message processing block that has its own processing strategy and exception handling strategy. Used in integration tasks, data processing, connecting applications, event processing, etc.
Subflow always processes messages synchronously but inherits processing strategy and exception handling strategy from the calling flow. It can be used to split common logic and be reused by other flows.
Private flow does not have source define. It can be synchronous or asynchronous based on the processing strategy selected. Also, they have their own exception handling strategy. Allows you to define different threading profile.
====
Processing strategy
While sub-flow is always synchronous the private flow behavior depends on the processing strategy
Performance
Sub-flow has a better performance when using request-response exchange pattern as they are actually a new processor chain injected in the flow at configuration time. Private flows are instead useful for asynchronous call provided you configured their processing strategy properly
Exception strategy
Private flow: the exception will be trapped by the local ES the exception will not be propagated to that main flow.
Sub-flow: will use the exception strategy defined in the main flow and it will have the exception got in the sub-flow.
Message Properties
In both case all properties, regardless their scope, are preserved from the main flow.
Threading profile
Private flows: allows you to define a different threading profile, but if you don't they will use the default one, not inherit the invoking flow one
Sub-flows: they will share the parent flow threading profile configuration
Overall
Sub-flows run within the same execution context (exception handler, transaction, properties) of its main flow, while private flow will initiate a new execution context.
To summarize, sub-flow is always recommended except in the case the exception needs to be handled in a separate flow different from the main flow or you are implementing an asynchronous pattern
No comments:
Post a Comment