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.
-
Show this thread
-
Replying to @adymitruk @EventModeling
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/ …
3 replies 0 retweets 1 like -
Replying to @dotnetninja @EventModeling
"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.
1 reply 0 retweets 3 likes -
"it's a really good thing, it's just really hard to find". Sounds like a great strategy for consulting and middleware sales. It's a racket that's way too common and probably wastes 50% of government budgets that could go to housing the homeless. Padding the pockets of friends.
1 reply 0 retweets 2 likes -
Replying to @adymitruk @EventModeling
Yes, it is hard. Instead of going in defensive mode read article and then comment. If it was easy to find boundaries of service or domain & then aggregates inside domain we would have majority of IT project working. Truth is different.
2 replies 0 retweets 0 likes
This is one big mistake. Your "correct" boundaries are plain impossible because business changes all the time. The right aggregate is a pipe dream. So adding a bunch of patterns just paralyzes you from the only thing you should be good at: continually adjusting to your business.
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.

