NServiceBus vs Temporal, Conductor, Camunda etc


I’m interested if anyone has a perspective on how NServiceBus compares from a feature set perspective for microservices orchestration / BPM / workflow type systems such as Temporal, Conductor, Camunda etc. I understand some of the obvious points on ability to execute BPM visual models etc. Outside of that what are the big differences?


Good day @Matt, and welcome to the Particular discussion forum.

I don’t have any direct experience with any of the mentioned workflow or orchestration engines. I read a bit on their respective websites [1], and they all seem to solve the microservices orchestration problem. We tend to favor a saga-based approach over an orchestration one, even though sagas can be easily used to build a microservices orchestrator (with no visual support).

I wrote about orchestration in the past: There is no such thing as orchestration, and also gave a talk about sagas: Welcome to the (State) Machine • Particular Software

Let me know if that helps, and if you have any further questions, please, do not hesitate to contact me.

[1] websites: