First Steps to Building a Single View of an SOA. Introducing the SOA Implementation Framework

Transcription

1 First Steps to Building a Single View of an SOA Introducing the SOA Implementation Framework Ronald Schmelzer Senior Analyst ZapThink, LLC

2 Introduction & Agenda Implementing a -Oriented Architecture is a journey Moving from proprietary interfaces to standardsbased ones is just the first step SOAs require a combination of security, management, integration, process, and architecture tools

3 Business Constant: Change Competition Changing Marketplace Customer Demands Mergers & Acquisitions Business Partners CHANGE Optimizing Processes New Technologies A Business is Never STATIC

4 Making Agility Work: Loose Coupling Coupling the level of common knowledge necessary in a distributed computing exchange Tight coupling one participant must have detailed knowledge about the other participant Full decoupling the two participants need have no knowledge about each other in order to interact Loose coupling the two participants may have specific, limited knowledge about each other

5 What is -Oriented Architecture? Access software via discoverable, loosely coupled s Users can compose s into business processes that are also s SOA!= Web s! SOA is a practice not a product!

6 Tools: Development vs. Architecture Architecture is The fundamental organization of a system embodied by its components, their relationships to each other and to the environment and the principles guiding its design and evolution. (IEEE P1471/D5.3) Developer tools different from architect tools No real SOA tools market (yet)

7 Introducing the SOAIF The SOA implementation framework is a product or set of products that offer everything companies need to build, run & manage their SOA No vendor offers a complete SOAIF (yet) Leverages orientation for modularity Today s markets are converging on the SOAIF

8 The Road to the SOAIF Integration Brokers Message- Oriented Middleware Transaction Monitors B2Bi EAI ESB App Server "Platforms" Application Servers BPI BPM SOAI Systems Management PKI Application Frameworks Modeling Tools RAD Arch. Tools SOA Tools SO Development SO Process SOA Implementation Framework SOA Enablement SO Mgmt SOII BAM WS Management SO Security BI WS Security XML Appliances Analytics IAM Network Appliances WS Tools SO Content EII Semantic Integration Established Markets IDEs Portals CMS Operational Data Stores Data Integration Transitional WS Markets Markets Remaining Distinct Presentation Tools NXDs Data Warehouses ETL Core SO Markets Copyright 2003 ZapThink LLC Databases OLAP

9 How Technology Segments Fit In Legacy integration Key: wrap legacy systems with Standards-based interfaces to enable them to participate in an SOI Products: EntireX Communicator, XML Gateways, XML Adapters Enterprise Bus Key: provide a reliable, messaging infrastructure to enable s to communicate and be composed into business applications Products: EntireX Mediator Business process Management (BPM) Key: Allow businesses to achieve agility by defining processes that can be translated into executable s Products:EntireX Mediator Enterprise Information integration (EII) Key: Aggregate information from disparate sources and present a interface Products Tamino

10 Why Should -Oriented Architectures be Asynchronous? Fundamental tenet of loose coupling: not being aware of end point requirements Composited (virtualized) Web s may require greater time for processing, requiring asynchrony B2B processes are often asynchronous Distributed systems can be more reliable when they are asynchronous Heterogeneous systems, especially those with limited bandwidth devices, function better asynchronously. Support human involvement in processes

11 Invocation Mechanisms in SOA SOA is more flexible than client/server supports multiple invocation mechanisms Request/Reply consumer Reply Reply channel Request channel Request provider Publish/Subscribe provider Input channel Event Message server Output channel Output channel Event Event consumer consumer Topic Data store Subscribe Routed Events provider Input channel Message Content-based Router Output channel consumer Output channel consumer Reliable Messaging provider Message bus consumer Message Message Data store Data store

12 An ESB makes a SOA Possible THREE fundamental tenets of SOA: Loose Coupling, Coarse Granularity, and ASYNCHRONY Making SOAs work - the Enterprise Bus Container Container Container Container MQ MQ Standards-based Ubiquitous Communication Infrastructure

13 The SOA Implementation Roadmap -Oriented Process Business-Oriented s Just-In-Time Integration - Oriented Enterprise Implement the SOA Metamodel Dynamic Discovery Manage s Heterogeneous Systems with Proprietary Interfaces Wrap Legacy Systems in s Interfaces Secure Interfaces

14 The State of the Market All balls must be in the air at once Security Integration Management Tools Process Web s do not create a permanent, distinct market New entrants jockeying for position while incumbents wait/build/acquire

15 SOA Culture Shock SOA crosses product, project, and business responsibility boundaries Who is qualified to be an architect anyways? What happens to the packaged app. Vendors? Just who pays for SOA anyways? Incremental vs. Enterprise-Wide

16 Next Steps? Take iterative approach to reduce risk Security & management usually come first Conceive of the SOA top-down (architectural plan) BUILD the SOA bottom-up (build s from existing resources) SOA leverages existing resources, so use them! Moving to standards-based interfaces first step Adopting standards-based infrastructure helpful

17 ZapThink is an industry analysis firm focused exclusively on XML, Web s, and -Oriented Architectures. Thanks! Take Credit for attending this presentation! Go to and enter the code SWAGSOA. Download a digital copy of the presentation Sign up for our ZapFlash newsletter Get a ZapCredit good toward free research and ZapGear! Ronald Schmelzer rschmelzer@zapthink.com