Conductor – A microservices orchestration engine that runs in the cloud

I'm a bit conflicted in how I feel about how much attention tools like this get. While it's absolutely a really neat tool, I think it gives a largely false idea that it's normal to need tools like this. The huge majority of companies aren't dealing with 1% of the traffic and complexity that Netflix handles. And for that vast majority of these companies, microservices and their orchestration tools are unnecessary.

I found the title a bit misleading. As I understood this is more of a workflow engine, using microservices for each step of the workflows.

Quite interesting, seeing this join Airlfow, Luigi, and other task orchestration tools, with a different approach to the deployment.

Oh no, Thats the name for my microservice orchestration https://github.com/flurdy/philharmonic/tree/master/conductor

Ok, not a total surprise that other projects will pick that name for orchestration. Though more upsetting is that theirs is probably near complete and actually well made, as opposed to mine which was mostly hacked out in anger at current orchestration tools.

:(

I get that they were trying to avoid this:

> Process flows [were] “embedded” within the code of multiple application.

But why did they choose a "JSON DSL" (which fortunately seems to mean JSON and not a DSL) as the best way to accomplish that? Seems to me that a builder pattern could have achieved the same thing without dropping compile time checks in probably the one place where they are most useful.

The workflow here -Isn't it similar to AWS Lambda Step functions?

The name is really close to Lightbend's ConductR : https://conductr.lightbend.com/

How does this compare to what's possible with Celery?