What Is Service Orchestration Architecture (SOA)

Services that make up enterprise software are like the instruments in the orchestra. If they are correctly timed and coordinated, the system will sing. Service Orchestration Architecture (SOA) is a set of principles for the development of enterprise systems like:

• enterprise resources planning (ERP) software
• project planning and design systems.
• customer relationship management software.

Zero-Touch Provisioning (ZTP) makes deploying and configuring network devices easier, faster and with no mistakes. Learn more in our blog Zero-Touch Provisioning: Faster Deployment, Fewer Mistakes.

Orchestration

Service orchestration optimally loosely coordinates:

• Interoperable services in the cloud.
• From different systems.
• Across different business domains.
• That perform discrete tasks.
• That add to a single result.

For example, if a broker is looking to provide financing to a business, he has to contact a number of systems:

• A credit agency.
• A service that lists possible lenders.
• A service to request rate quotes from different banks.
• A service to process quotes with the data from the other services.

Together, the orchestrated loan request service will give the broker a list of quotes from potential lenders. The orchestration takes all the individual parts and orchestrates them into a harmonious unit. Instead of having to create a complex new piece of software to carry out all these tasks, the service orchestration software uses the software of existing systems and integrates the parts. Effective orchestration automates the calling up and output generation of different business systems, putting the results in one place.

The term “service orchestration” came about because the cloud was developed around packages of already developed “services” which could be used in the creation of software if they could be reached, activated and “orchestrated” with each other.

Orchestration in the Cloud

Service orientation was developed with the growth of the cloud. Cloud automation arranges and coordinates automated tasks so they flow together, to make a single workflow. It takes advantage of cloud automation which performs tasks without human intervention. When IT teams create a standard process to make a new application work, they have to orchestrate several automated tasks. This involves:

• Auto-scaling.
• Elastic load balancers.
• Alarms.
• Deployment automation tools.
• Puppet scripts.

All of these functions are cloud automation processes. These cloud automation tools are employed in orchestration. They can be offered on an internet as a service (IaaS) platform or in a 3rd party software package. The orchestration tools collect and enumerate:

• The needed resources.
• The instance types.
• IAM roles that define the user for the needed software.
• Configurations.
• Interconnections among resources.

Cloud Orchestration Tools

Engineers can use tools like AWS CloudFormation or VMware’s vRealize Orchestrator to create templates that meld these processes into a single workflow so that the entire complex process is called up as one unit.

The creation of cloud orchestration templates that can be used on a regular basis is itself, time-consuming and challenging without sophisticated orchestration tools both simplify complex IT processes and take away much of the risk.

Service Orchestration in Practice

In the beginning, service orchestration at the level of the cloud was an expensive and time-consuming process since it required operators to write new code to orchestrate services in the cloud. The enterprise service bus (ESB) emerged as a mechanism for service orchestration. The ESB incorporates “lightweight solutions.” Many companies have turned to a standalone enterprise service bus ESB that simplifies their service orchestration needs. The cloud is organized around a family of “services.” Service orchestrators develop new applications by combining a collection of services, rather than building out an entire software program. This philosophy saves developers a great deal of time and eliminates code redundancies.

The ESB has been called a “Bottom-Up” approach to SOA . Many SOA projects failed at the beginning because they were too expensive, required years to deliver, and expensive consultants. The cloud was ready with its matrix of services, but attaching services to each other requires significant new code writing. The ESB came in as an integration platform as a service (IPasS). ESBs can power up the orchestration of services without requiring an application server or other high powered infrastructure components. An ESB can, therefore, be implemented in a very short time.

Zero-Touch Provisioning (ZTP) makes deploying and configuring network devices easier, faster and with no mistakes. Know it all on our blog Zero-Touch Provisioning: Faster Deployment, Fewer Mistakes.