News for hackers. Stuff that matters.
Re:Netflix Conductor: Open-source workflow orchestration engine by extrapickles on Thursday August 20, 2020 @01:48AM (#24220286)
Yes. The only difference from what I can tell is that each service/node on the bus is a VM/Container rather than a bespoke built machine.
Re:Netflix Conductor: Open-source workflow orchestration engine by swyx on Thursday August 20, 2020 @03:40PM (#24227806)
dragonwriter below you says the opposite - based on a plane-level analysis. would be interested if that changes your mind.
Re:Netflix Conductor: Open-source workflow orchestration engine by extrapickles on Thursday August 20, 2020 @06:57PM (#24229992)
The real answer is it depends on what you think what responsibilities exactly ESB or Workflow Orchestration should have. dragonwriter is of the reasonable opinion that ESBs focus should be a message plane. If your of my opinion, ESBs generally include some of the features found in workflow. devonkim is also right in that ESBs in general let the business data/process bleed into the rest of the stack, where as with workflow, its completely agnostic to the business data/process.

The most accurate answer would be from comparing various ESB products to Workflow Orchestration products, as every vendor/product will have slightly different opinions on where their responsibilities are.

Re:Netflix Conductor: Open-source workflow orchestration engine by swyx on Thursday August 20, 2020 @07:52PM (#24230383)
fair enough. appreciate the thoughts!