ricardozanini commented on PR #2214: URL: https://github.com/apache/incubator-kie-kogito-apps/pull/2214#issuecomment-2842620946
Hey @elguardian, I’d like to highlight the potential impact this change would have on our current architecture. By removing the reactive layer, we lose the benefits of non-blocking I/O, which means that instead of leveraging I/O threads, the system would start using worker threads for job execution. This has important performance implications. In our setup, the Jobs Service is a singleton that handles job execution for all workflows. Given this shared responsibility, non-blocking I/O provides clear advantages, especially under high load when multiple jobs are being processed concurrently. Reactive execution helps preserve thread resources and improves scalability. In contrast, in the compact architecture (where one Jobs Service instance is embedded per workflow runtime), the performance characteristics are different — they benefit from tight in-process listener calls, while we rely on HTTP calls between the Jobs Service and the workflows. For us, having non-blocking I/O is critical and even critical for performance in those scenarios. Please reconsider this change or move the reactive configuration to an optional plugin or extension instead. That way, we can preserve current behavior for use cases that rely on reactive execution. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
