Hi All,
We have a use case where from parent process we will call a webapi and based on the data received the webapi triggers subprocesses dynamically and consider the subprocesses count is pretty high.
We need the child processes to communicate back the parent process as well
One way to implement this is using a send message and receive message, do we have any other alternative way which doesn't include DB intervention. Please suggest
Discussion posts and replies are publicly visible
Do you plan to keep alive these parent processes for a longer time? Does not feel like a best practice design.
sujithak806 said:send message and receive message
This is the way to go.
Please consider best practices. For certain use cases like setting up data/data migration this design works well and try to avoid this design for apps.
Yes Stefan, we need to keep them alive.
OK. I have no idea what your goal is. Long running processes are to be avoided.
Data migration scenarios are a different scenario. Starting a large number of processes with messaging going back and forth puts high load on the system, conduct a load test and keep an eye on health check. Do that outside business hours.
Thanks Stefan and Shyam,
Is there any other way to have a communication for an asynchronous sub process and parent process. Please suggest.