[PERF] Optimize Message Handling in `IWorkflowInbox` to Reduce Workflow Dispatch Latency about elsa-core HOT 1 CLOSED

To address the issue of significant delays when initiating multiple dispatched workflows concurrently due to excessive messaging within the IWorkflowInbox service, it is indeed necessary to optimize the dispatch mechanism. The proposed solution to modify the IWorkflowInbox service to conditionally send messages only when there are relevant bookmarks in the database is a valid approach. This would prevent the generation of unnecessary messages and reduce the load on the messaging infrastructure.

However, implementing this solution requires careful consideration of the workflow engine's internal mechanisms to ensure that no dispatched workflows are missed and that the system remains reliable. It may involve changes to the way bookmarks are managed and how messages are correlated with them.

Before proceeding with this optimization, it would be important to review the current implementation of the IWorkflowInbox service, the bookmark management system, and the messaging infrastructure to identify the best approach for conditional messaging. Additionally, thorough testing would be required to ensure that the changes do not introduce new issues or negatively impact existing workflows.

If you are looking for guidance on how to implement this change or if you need further assistance with the specifics of the Elsa Workflow system, please provide more details or clarify your requirements.

This comment was generated by Glime.

from elsa-core.