The current implementation of the mysql saga store, when fetching saga instances by sage type, fetches all saved instances in one round trip which may cause a performance issue when there are large amounts of saga instances that need to be fetched.
In order to prevent a potential performance hit the fetching logic should be optimized to include paging and potentially parallel the fetching using a set of goroutines
The current implementation of the mysql saga store, when fetching saga instances by sage type, fetches all saved instances in one round trip which may cause a performance issue when there are large amounts of saga instances that need to be fetched.
In order to prevent a potential performance hit the fetching logic should be optimized to include paging and potentially parallel the fetching using a set of goroutines