ORCHESTRATOR: MUCH MORE THAN A CONNECTOR
An orchestrator is:
A piece of software independent both from internal systems and channels. It is used to centralizes processes and exchanges in the architecture. That is why it needs to manage processes along time and to store situations and contexts to achieve it.
The management of complex systems, with several channels, multiple back-ends, different partners…
An incremental recovery of internal systems, a.k.a. digital decoupling.
Orchestration is a business responsibility:
To manage orchestratrion, business areas need autonomy: a system with a visible behavior, with a minimal involvement of technical areas to adapt it.
A VISIBLE BEHAVIOR IN A HIERARCHY OF PROCESSES.
EMERGENT BEHAVIORS DETECTED AND DEFINED AS HIGH VARIETY PROCESSES
In a complex system, some processes in different components may overlap.
Concurrency gives birth to an emergent behavior. Its variety grows exponentially with the number of components involved.
Artifact-Centric is the model specifically suited for this need.