Hi Jason (and others), Thanks for the input. We are also considering that option, but in our scenariowe have some concerns:
- We have several independent consumers of the messages incl. the large one (pub-sub scenario) each consumer with its own message processing logic. This means that every consumer should implement the sequencing saga. This could to some degree be resolved by providing some common saga handling with hooks for the custom parts. - What if one of the sequencing messages fail? Can I retry that one message? I guess perhaps I can if I can make the message arrival order indepedent I feel the databus approach would be a more general solution to the problem. We have a few more message types which may exceed the limit in some scenarios. -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To view this discussion on the web visit https://groups.google.com/d/msg/rhino-tools-dev/-/NCZLWHABTdAJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
