Allow assigning multiple sagas to a single event processor

The current way of creating event processors for Sagas, as I’m seeing it, is to create a single tracking event processor for a single Saga. This works quite well on a microservice scale, but might turn out to be a problem in big monolithic applications which may implement a lot of Sagas. Since I’m writing such application, I want to have a better control over number of existing threads, which in turn will give me better control over usage of database connection pool (I’m using tracking event processors with JPA token store), context switching and memory usage.

Ideally, I would like to have at most as many tracking event processors as CPU cores where each event processor executes multiple sagas.

As stated by answer to this SO question, such configuration is currently not possible. The reason being that event processor creation logic is currently hardcoded into SagaConfiguration for both subscribing and tracking event processors.

[smcvb]

@mjagus as you might have been notified of, this feature is now contained in the framework. As off release 3.3 you should be able to configure a single Event Processor for several Event Handling Components (like Sagas for example).

[smcvb]

Thanks for elaborating, understanding your point of view, which doesn’t sound like a weird request. We’ll discus this further here and update this issue for any progress around the decision making of it.