These are chat archives for jdubray/sam
My point is that most of the time node is pictured like an unique and magic runtime, but in the end it's only a reactor pattern runtime, with more weaknesses than strengths
I don't disagree with you. It's just this stack works for me. Nothing seems hard to achieve (up to the 1k - 10kTPS range), but perhaps I have not worked on "things that are hard to achieve".
but at the end the catch is that an event-driven orchestration is the way to go
I'll beg to disagree. That does not scale (in scope), you can use the SAM pattern for that (since it is stateful) https://www.ebpml.org/blog15/2015/06/designing-a-reliable-api-call-component-with-sam/
You can use SAM either as a central coordinator, or as a event handler (I was the lead editor of ebXML Business Process, which was the precursor to WS-CDL). You cannot underestimate the difficulty in managing long running state. Talking about "events" is like talking about a car from a wheel perspective without ever mentioning you need an engine too.
when we develop a strong culture around it
This can only happen when there is enough insight to recognize what's broken and what's not. There is just too my hype and not enough thinking in the software industry.
it does not impose any particular semantics to how you define State, Type, Action and Relation.
that's the main problem though.. we NEED to impose something at some point, and give it an altisonant name, and make that kind of artificial hype that is needed today to capture the attention