I imagine flowable quite capable in using REST tasks to communicate with different micro services and so orchestrate them into a coherent whole and this is what I have in mind when I use the term orchestration. So for example building a camel integration as a separate spring boot/docker process rather than have it run in the same JVM as flowable.
I guess my core interest is in what people who have done this use for service discovery and how they manage that in the design for processes. For example using the HTTP task you can communicate with a REST (loose definition of it) service, but one puts the url and port in at design time, and this probably needs to be less fragile and more flexible.
But then service discovery becomes an extra layer and would take 2 HTTP tasks, one for discovery and one for the actual call to complete one function. eg. HATEOAS REST where links are returned from main resource pointing to others along with media types.
Or one would have a configuration service that adds global configuration to each process on start, but here is fragility as changes only take affect on new processes, or one has to replace many, and some might be running at the time.
These are the things I hoped others have maybe already tackled in one or other fashion and have some titbits to share…