This also allows you to get rid of a lot of middleware.
Show this thread
Don't use the saga messaging pattern. We're deleting about 30 classes from our standard stack. Majority of patterns in "Enterprise software" and "messaging patterns" are just "Todo lists" as expressed in @EventModeling. Embrace simplicity.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Yes if you are using it wrong, or if you don’t understand what SAGA is,especially when working with messaging. Problem:It is not easy to identify Saga. This is another explanation of saga and what it is. Think of it as aggregate and long running process.https://docs.particular.net/nservicebus/sagas/ …
-
"You're using it wrong" is just fodder to sell consulting and create an artificial market for superfluous middleware. Deny its existence; it's an imposter. I don't describe a saga in the diner, it's a receipt that's used from start to finish - just another view.
- 20 more replies
New conversation -
-
-
Normally I would agree, Saga’s are guilty until proven innocent.. But, in integration scenario’s with legacy services/systems I found them still useful to keep track (and reacting) of happy/unhappy outcomes, so what would be the alternative?
-
A Todo list does that.
- 1 more reply
New conversation -
-
-
Could you describe the case? In which situation you could simplify the system by removing sagas?
-
Any case. They're not needed.
- 2 more replies
New conversation -
-
-
How to express compensation in a todo?
-
What are you compensating for?
- 2 more replies
New conversation -
-
-
Didn't realize how much clutter the "Enterprise architects" needed to clean up from their heads - judging by the questions.
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.