You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my thinking I have come to the conclusion that we should only use the streamId. The problem I was thinking about was that producer A and producer B (different regions) would use the same streamId and then consumer in C would setup streams to both A and B. The commands would then be propagated to both A and B.
My thinking is that if that is not desired one should use different streamId in A and B even though it may be the same service and same entityType.
In my thinking I have come to the conclusion that we should only use the streamId. The problem I was thinking about was that producer A and producer B (different regions) would use the same streamId and then consumer in C would setup streams to both A and B. The commands would then be propagated to both A and B.
My thinking is that if that is not desired one should use different streamId in A and B even though it may be the same service and same entityType.
Originally posted by @patriknw in #826 (comment)
The text was updated successfully, but these errors were encountered: