An Optimized Design of Service Orchestration

Service Oriented Architecture (SOA) is a computer system's architectural style for creating and using business processes, pack-aged as services, throughout their lifecycle. These services communicate with each other by passing data from one service to another, or by coordinating an activity between two or more services. SOA Integration leverages the benefits Service Oriented Architecture (SOA) to solve one of the most fundamental challenges IT is facing today. SOA Integration behaves as a completely integrated solution. Components for set-vice integration, process integration, set-vice orchestration, data services, connectivity, and unified tooling, each work together to provide the necessary integration patterns needed for abstracting multiple integration scenarios. Service Orchestration is part of SOA integration solution, which provides central process controlling and message exchanging, typically like BPEL. These Service, Orchestration mechanisms have a common pitfall, that it's not distributed, so from the point of end user, it wastes much time in "irrelative" data exchanging. This paper describes an optimized way for Set-vice Orchestration which separates controlling and data, making Service Orchestration more distributed, to reduce the "irrelative" data exchanging time consumes.