Child Process Flow distribution
The application executing all Child Process Flows along with their Parent Process Flow on a single pod, even when other pods are available, can often lead to resource bottlenecks and slower execution.
To overcome this limitation, Adeptia introduces Child Process Flow distribution.
What is Child Process Flow distribution
Child Process Flow distribution allows Child Process Flows to be distributed across runtime pods that are available and ready to accept them for execution.
Key Benefits:
-
Scalability and Performance:
Distributes workloads across multiple pods, preventing resource bottlenecks and significantly improving the overall execution speed of process flows. -
Better Resource Utilization:
Ensures even distribution of workloads across runtime pods based on their availability, leading to optimized use of system resources.
How it works
Adeptia includes Redis as part of the application to support this feature. Redis functions as a high-performance caching system that stores the Parent Process Flow context. The Child Process Flows retrieve the context from Redis enabling their distributed execution across available pods.
![]() | Fetching the context from Redis is the default behavior. This ensures that the context info being used is up to date. You can however cache this context in the Child context which can be used by the Child Process Flows for their distributed execution. For more details, refer to this page. |
How to enable this Child Process Flow distribution
To enable and use Child Process Flow distribution:
- Deploy Redis as part of your environment.
- Enable Child Process Flow distribution in the application settings.
![]() | Process Flow recovery and reprocessing aren’t currently supported when Child Process Flow distribution is enabled. |

