This blog post explains what an orchestration processor is in the context of the Orchex enterprise orchestration engine (EOE).
Update 15.Dec.2025: After years of frustration with WordPress, I am finally abandoning this blog. The content will likely stay here for some time, but new content will appear here:
This blog post is a member of a collection:
Before investigating orchestration processors, it may help to understand orchestration processes:
In short, an orchestration process:
- Accepts an input JSON payload.
- Invokes one or more orchestration processors.
- Generates an output payload.
An orchestration processor is a step in an orchestration process. An orchestration process begins with an orchestration processor. Invoking a processor through the EOE API invokes an orchestration process.
Each orchestration processor can invoke a webservice API or access any other HTTP endpoint that optionally accepts and returns JSON. Orchestration processors typically include JavaScript fragments that manipulate the input payload before sending it to the webservice API and often transform its result.
In fact, an orchestration processor defines an orchestration process that may consist of multiple processors. Every orchestration process begins with the invocation of an orchestration processor.
The orchestration process determines any other processors on which the invoked processor depends, and invokes those processors in the order required, including any orchestration processors on which they depend.
Unlike a pipeline, which is generally involves a sequence of processors, an orchestration process can involve one or more orchestration processors that run in parallel when possible and in sequence when the output of one depends on input from another. An orchestration process determines dependencies between processors and invokes processors sequentially where needed and in parallel where appropriate.
Technically, all processors are the same, because they all use the same infrastructure. From another perspective, there are two types of orchestration processors: those that invoke Webservice APIs and those that don’t. Any orchestration processor can include JavaScript fragments.
Processors consist of a series of stages configured by elements in the processor definition. Most steps consume a payload and return a payload. The final processor determines the response payload for the Webservice API call that invoked the orchestration process.
deliverystack.net 
2 thoughts on “-What Is an Orchestration Processor?”