1 / 8

Service Orchestration

Service Orchestration. June 8, 2004. Atul Saini CEO and CTO, Fiorano Software, Inc. Atul@fiorano.com www.fiorano.com. Services - a source of much confusion. Activities (used in most typical BPEL flows) Synchronous functions that accept an input and return an output

braden
Download Presentation

Service Orchestration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Service Orchestration June 8, 2004 Atul Saini CEO and CTO, Fiorano Software, Inc. Atul@fiorano.com www.fiorano.com

  2. Services - a source of much confusion • Activities (used in most typical BPEL flows) • Synchronous functions that accept an input and return an output • Typically executed within a thread context • Coarse-Grained Services • Event-driven inputs and outputs (multiple, asynchronous) • Typically execute in a process-context • Service-Abstraction has dramatic impact on usability and benefits to end-users

  3. Activity Orchestration Fundamental Problems • Focused on Control-flow • Most BPEL engines do not implement event/data flow visually; requires programming • Low-Level • Function-call interface implies “too many moving parts” • Single-process coordination • Control process is centralized • Typically uses request/reply interactions with external systems (inefficient)

  4. Orchestration of Coarse-Grained Services • Focused on Event-Flow • Enables event-driven business processes without programming • High-Level • Maps to problems at a business-level • Allows the creation of a single-view for Business and IT • Accomodates BPEL control flow • Internal structure of service-abstraction is a BPEL process • Combination of event(data) and control flow

  5. Coarse-Grained Service Orchestration Example

  6. Orchestration of Coarse-Grained Services • Focused on Event-Flow • Enables event-driven business processes without programming • High-Level • Maps to problems at a business-level • Allows the creation of a single-view for Business and IT • Accomodates BPEL control flow • Internal structure of service-abstraction is a BPEL process • Combination of event(data) and control flow

  7. Coarse-Grained Service Orchestration Benefits • Easy change-management, extensibility • Logical design maps directly to the physical implementation • Business Process model isthe implementation • Loosely-Coupled Service Composition • Dynamically setup and auto-reconfigured middleware • Event-Driven Business Processes Unified Business/Technical views lead to dramatic savings!

  8. Summary • Impedance mismatch between Business and Technology users reduced • Faster turnaround times, dynamic adaptability • Enhanced Reuse of existing software and hardware • Event-Driven Business Process via composed services • Implementation Cycle-Times • 4-5 months to 4-5 weeks Coarse-Grained, Event-Driven Services offer key benefits

More Related