System Orchestration Task

An System Orchestration Task is a Middleware (Distributed Applications) that ...

• AKA: Automated Workflow Management.
• Context:
  • It can be solved by an Orchestration System (possibly based on an orchestration platform).
• See: Middleware (Distributed Applications), Logistics.

---

---

References

2017

• (Wikipedia, 2017) ⇒ https://en.wikipedia.org/wiki/Orchestration_(computing) Retrieved:2017-4-7.
  • Orchestration is the automated arrangement, coordination, and management of computer systems, middleware, and services.

---

2017

• (Wikipedia, 2017) ⇒ https://en.wikipedia.org/wiki/Orchestration_(computing)#Usage Retrieved:2017-4-7.
  • Orchestration is often discussed as having an inherent intelligence or even implicitly autonomic control, but those are largely aspirations or analogies rather than technical descriptions. In reality, orchestration is largely the effect of automation or systems deploying elements of control theory.

    This usage of orchestration is often discussed in the context of service-oriented architecture, virtualization, provisioning, converged infrastructure and dynamic datacenter topics. Orchestration in this sense is about aligning the business request with the applications, data, and infrastructure. It defines the policies and service levels through automated workflows, provisioning, and change management. This creates an application-aligned infrastructure that can be scaled up or down based on the needs of each application. Orchestration also provides centralized management of the resource pool, including billing, metering, and chargeback for consumption. For example, orchestration reduces the time and effort for deploying multiple instances of a single application. And as the requirement for more resources or a new application is triggered, automated tools now can perform tasks that previously could only be done by multiple administrators operating on their individual pieces of the physical stack.

    A somewhat different usage relates to the process of coordinating an exchange of information through web service interactions. (See also service-oriented architecture, and web service choreography.) Applications that decouple the orchestration layer from the service layer are sometimes called agile applications.A distinction is often made between orchestration (a local view from the perspective of one participant) and choreography (coordination from a global multi-participant perspective, albeit without a central controller).