feat: optimize queue usage for follow endpoints #6856
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes are being made and why?
This PR introduces improvements to the follow endpoints for executions and logs in Kestra. It focuses on optimizing queue usage to enhance scalability and resource efficiency.
Key Changes:
Centralized Queue Management:
Implemented a singleton ExecutionStreamingService to manage a single queue consumer for all execution updates.
Reduces the creation of multiple queue consumers and threads for each connection.
Subscriber Pattern:
Introduced a subscription mechanism where clients (UI connections and wait=true executions) register as subscribers for specific execution IDs.
Updates are selectively broadcasted to relevant subscribers using a ConcurrentHashMap.
Addresses #6777