Cloud Orchestration

In past 6 years Jasper has designed, managed and implemented more than 30 Cloud Orchestration projects. Our solutions are design to meet our customer requirements and with emphasis on security.

Orchestration and Choreography for Cloud Computing:

Cloud computing introduces more-granular and specific meanings of these terms: "workflows" and "processes" are used in different domains. At one level there are inter-company business processes, and at another level there are processes to get the wide area network ("the cloud") operational. To keep matters simple, we will define "an orchestrator" as: the entity that manages complex cross domain (system, enterprise, firewall) processes, and that handles exceptions. Since an orchestrator is valuable in the fulfillment, assurance as well as billing processes, service-aware incarnations of an orchestrator should be capable of adjustments based on feedback from monitoring tools. At the most basic level, an orchestrator is a human.

The main difference, then, between a workflow "automation" and an "orchestration" (in the context of cloud computing), is that workflows are processed and completed as processes within a single domain for automation purposes, whereas orchestration includes a workflow and provides a directed action towards larger goals and objectives. In this context, and with the overall aim to achieve specific goals and objectives (described through Quality of Service parameters), e.g., meet application performance goals using minimized cost and maximize application performance within budget constraints, cloud management solutions also encompass frameworks for workflow mapping and management.

Key cloud service orchestration elements: