What s Hot with Web Services?

Transcription

1 What s Hot with Web Services? Ronald Schmelzer Senior Analyst ZapThink, LLC 1

2 The Changing World of Data Proliferation of Content Increased Integration of Applications Automation of Paperbased Systems Shift to Customer- Centric KM Model BIG CHANGES AHEAD 1 A Web Services Roadmap ZapThink Web Services Roadmap Primary roadblocks Primary use Invocation style Static binding to static Services Internal Focus Security Management Dynamic binding to static Services External (B2B) Focus Robust registry services Transactions Discover & bind at runtime (JIT integration) Full embedding of Web Services Orchestration & Workflow Billing & Metering Business Web Process Automation Source: Copyright 2002 ZapThink LLC 2

3 Why do we Integrate? Respond to Business Drivers Get a better understanding of customers and business operations Connect organizations Lower the cost of ownership Allow systems to evolve Value-add existing applications The Integration Zipper 3

4 Implementing SOI Custom Integration Traditional EAI, B2Bi Service-Oriented Integration Relative Costs Initial Costs Configuration Maintenance Upgrades Copyright (C) 2002 ZapThink, LLC So, Where s the ROI? Web Service Implementation Quadrants I = Investment Hardware and Software Time and Effort R = Return Cost Savings Revenue Enhancing Time to Return Externallydeployed Web Services Immediate Value Internally-deployed Web Services Revenue-enhancing Cost-saving Client-side Web Services Long-term Value Web Serviceenabled Applications Source: 4

5 Old Wine in New Bottles? Web Services as a generic API, XML as a generic data format good, but good enough? Where are the services?? Is there really ROI in standards-based APIs? Web Services in the Present Web Services are in the horseless carriage phase Where new technology is applied in the patterns of the earlier technology Web Services are used to simplify integration 5

6 Web Services in the Future New approaches to software development, engineering, architecture, and management Service-Oriented Architecture Find Service Broker Publish Service Requester Bind Service Provider 6

7 Static Components Dynamic Services Today: Component-based development: build & integrate components Assemble to customer s specifications Tomorrow: Web Services dynamically described with WSDL files Developer indicates where WSDL file can be found System Integration Service Exposure & Reflection Today: System requirements architecture component specifications Tomorrow: System requirements Service assembly Access dynamic descriptions 7

8 Coding for Reusability Coding for Broad Applicability Today: Reusability is a pillar of OO programming, but Takes more time No guarantee of reusability Developer working beyond requirements Agile methodologies (like Extreme Programming XP) Code only what customer needs at the time Refactor whenever extra functionality creeps in Resulting code is broadly applicable Tomorrow: Develop Service-oriented architectures following Agile principles Ongoing, iterative process that involves customers/users Services constructed to be simple and broadly applicable Disruptive Upgrades Ad Hoc Upgrades Today: Modularity is a great idea, but largely a myth Components often not fully encapsulated APIs have semantic ambiguities Tomorrow: Modularity loose coupling Expose dynamic Service descriptions Web Service consumers adjust to changes at runtime System upgrades will be ad hoc 8

9 Top-Down Scalability Bottom-Up Scalability Today: Scalability carefully planned from top down Tomorrow: Scalability grows from bottom up Use UDDI registry to locate extra resources UDDI Platform Dependence Platform Irrelevance Today: Platform independence is an unrealized dream DCOM & CORBA not cost-effective cross-platform EAI very expensive & complex Tomorrow: Systems communicate via Web Services interfaces Platforms provide development & execution environments only.net Java J2EE 9

10 Dictatorship Model Federation Model Today: Tightly coupled enterprise application suites Tomorrow: Loosely coupled collections of federated Services Siebel SAP Web Services: Make Friends with IT Productivity! Efficiency! Does Implementation Matter Anymore? 10

11 BPEL4WSOITJATLA? Transactions Business Process Workflow Web Services Management Quality of Service Managing Web Services end-points Long lived, asynchronous transactions Billing and Metering Repositories WEB SERVICES TESTING? B2B vs. EAI-type Web Services Management 11

12 Web Services Platforms IDE Component Wrapping Service Def. Registration Runtime Environment Choices: Single-vendor platform: Microsoft.NET J2EE-based platform: IBM, Sun, HP, many others None of the above: Scripting Languages, etc. Many Entrants Hardware / OS Platform vendors Microsoft.NET, IBM, HP, Sun ONE, Application & Integration Server vendors BEA, Oracle, IONA New Entrants Cape Clear, Systinet, Infravio Web Services Operations Management Runtime Management QoS & SLA Billing & Metering A Third-generation market But, necessary for WS in a mission-critical role Vendors WEST Global, Primordial, LogicLibrary 12

13 Web Services App. Suites Web Web Service Web Service Service Work- Service + Flow + Flow Interface = Aggregate Web Services Vendors: App. Suites: Avinon, Instantis, Bowstreet Portals: Epicentric, Plumtree, Oracle, et. al. WS Sizing and Growth Web Services Market Aggregate 18 ($ Billion) Source: ZapThink, LLC Web Services Management Web Services Application Development Web Services Platforms Total Market: $15.5B by 2005 WEB SERVICES MARKET SIZE ($B) Web Services Platforms Web Services Application Development Web Services Management

14 Take Away Web Services is just at the beginning Many roadblocks yet to overcome Need vision of destination in order to point in right direction Thank You! Jason Bloomberg & Ron Schmelzer of ZapThink are coauthors of XML and Web Services Unleashed. ZapThink is an industry analysis firm focused exclusively on XML and Web Services. Find out more about ZapThink at Ronald Schmelzer 14