{section}
{column}
{multi-excerpt:name=features}

Several instance of the component can be deployed concurrently on Petals ESB. A sequence of service-based API invocations can be exploded on each component instances

An orchestration is sequence of automatic service invocations, and can be modeled as a sequence of service tasks in a BPMN2 description. Creating an instance of such a process will start automatically the sequence of service invocations. With BPMN2 it is possible to implement your orchestration as a process containing only service tasks. For example, the following orchestration can be an implementation of a service processing a "New Order":
!orchestration-sample.png|align=center!

*Process*

A process or workflow can be "servicized" at different levels:
* when creating a new instance of the process definition,
* when completing a task of the process instance
* when searching process instances or tasks

For example, the previous sample can be reworked replacing two service tasks by human tasks with such a process:
!process-sample.png|align=center!
Then created services are:
* the service "New Order" associated to a process instance creation,
* the service "Order Prepared" associated to the completion of the task "prepareOrder",
* the service "Order Delivered" associated to the completion of the task "deliverOrder".

*Concurrency*

Several instance of the component can be deployed concurrently on Petals ESB. So, you are able to deploy each process definitions on several component instances to get high availability.

{multi-excerpt}

{section}