web services tutorial pt. 1 - doveltech.com · the large upper petal of the flower of a pea or...

1

Copyright © 2001, ZapThink, LLC

Web Services Tutorial Pt. 1

Ronald SchmelzerSenior AnalystZapThink, LLC


2


The Changing World of Data

• Proliferation of Content• Increased Integration of

Applications• Automation of Paper-

based Systems• Shift to Customer-

Centric KM Model

BIG CHANGES BIG CHANGES AHEADAHEAD

1


The Data Tower of Babel

WordEDI

ASCII

PDF

COM

CORBA

GIF

JPEG

MPEG EBCDIC

ASN.1HTML

DBF

WAV

AIFF

ZIPExcel

TIFF

EJB

3


Standards…


NOUN:1. A flag, banner, or ensign, especially: a. The ensign of a chief of state, nation, or city. b. A long, tapering flag bearing heraldic devices distinctive of a person or corporation. c. An emblem or flag of an army, raised on a pole to indicate the rallying point in battle. d. The colors of a mounted or motorized military unit. 2a. An acknowledged measure of comparison for quantitative or qualitative value; a criterion. b. An object that under specified conditions defines, represents, or records the magnitude of a unit. 3. The set proportion by weight of gold or silver to alloy metal prescribed for use in coinage. 4. The commodity or commodities used to back a monetary system. 5. Something, such as a practice or a product, that is widely re5. Something, such as a practice or a product, that is widely recognized or employed, cognized or employed, especially because of its excellence.especially because of its excellence.6a. A degree or level of requirement, excellence, or attainment. b. A requirement of moral conduct. Often used in the plural. 7. Chiefly British A grade level in elementary schools. 8. A pedestal, stand, or base. 9. Botany a. The large upper petal of the flower of a pea or related plant. b. One of the narrow upright petals of an iris. Also called banner, vexillum. 10. A shrub or small tree that through grafting or training has a single stem of limited height with a crown of leaves and flowers at its apex. 11. Music A composition that is continually used in repertoires.

ADJECTIVE:1. Serving as or conforming to a standard of measurement or value.2. Widely recognized or employed as a model of authority or excellence: a standard reference work.3. Acceptable but of less than top quality: a standard grade of 3. Acceptable but of less than top quality: a standard grade of beef.beef.4. Normal, familiar, or usual: the standard excuse.5. Commonly used or supplied: standard car equipment.6. Linguistics Conforming to established educated usage in speech or writing.

ETYMOLOGY:Middle English, from Old French estandard, rallying placerallying place, probably from Frankish *standhard : *standan, to stand; see kar- in Appendix I.

Standards…

From the “American Heritage® Dictionary”:

4

4


XML for Computing (aka “Web Services”)

“What is 2+2?”“What is 2+2?”

“4”“4”


About Metadata

• Data that describes information• What does “15” Mean?

Photo Number=15

Resolution=640x480x16.7m

Image Size=80x175

Format=JPEG

Filename=paperhead.jpg

Category=Humorous

Caption=For that head cold…

Price=$0.05

Copyright=Wacky Photos, Inc.

Times Downloaded=5,553

Product Number=15

Category=Sanitary

Product Name=HeadWipes

Price=$15.95

Image=paperhead.jpg

Accessory=Toilet Paper

Quantity=1

Shipping Weight=5 lbs.

Shipping Size=6x6x9

5


Two Sides of the XML Coin

• Is Data Message or Document? Hint: Shelf-life

MESSAGE DOCUMENT


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?

6


Web Services: Make Friends with IT

• Does Implementation Matter Anymore?

Productivity!Efficiency!


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

7


Web Services in the Future…

New approaches to software development, engineering,

architecture, and management


Service-Oriented Architecture

ServiceRequesterService

RequesterServiceProviderServiceProvider

ServiceBroker

ServiceBroker

Find

Bind

Publish

8


The Web Services Stack

• Idea: Combine XML, HTTP, and SOA

Service Messaging: SOAP

Service Description: WSDL

Service Discovery: UDDI

Transport: HTTP, SMTP, FTP, …


Service-Oriented Integration

““ServiceServiceServiceServiceServiceServiceServiceService--------Oriented Integration (SOI) Oriented Integration (SOI) Oriented Integration (SOI) Oriented Integration (SOI) Oriented Integration (SOI) Oriented Integration (SOI) Oriented Integration (SOI) Oriented Integration (SOI) simplifies system integration by simplifies system integration by simplifies system integration by simplifies system integration by simplifies system integration by simplifies system integration by simplifies system integration by simplifies system integration by providing an architectural framework providing an architectural framework providing an architectural framework providing an architectural framework providing an architectural framework providing an architectural framework providing an architectural framework providing an architectural framework based on Web Services in which to based on Web Services in which to based on Web Services in which to based on Web Services in which to based on Web Services in which to based on Web Services in which to based on Web Services in which to based on Web Services in which to build, deploy, and manage system build, deploy, and manage system build, deploy, and manage system build, deploy, and manage system build, deploy, and manage system build, deploy, and manage system build, deploy, and manage system build, deploy, and manage system integration.integration.integration.integration.integration.integration.integration.integration.””

---- ZapThinkZapThink

9


The Integration “Zipper”


Implementing SOA

Initial Costs Configuration UpgradesMaintenance

Custom IntegrationTraditional EAI, B2BiService-Oriented Integration

Copyright (C) 2002 ZapThink, LLC

Rel

ativ

e C

osts

10


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


Static Components Dynamic Services

Today:• Component-based development: build &

integrate components• Assemble to customer’s specificationsTomorrow:• Web Services dynamically described with

WSDL files• Developer indicates where WSDL file can be

found

11


System Integration Service Exposure & Reflection

Today:• System requirements architecture

component specificationsTomorrow:• System requirements Service assembly• Access dynamic descriptions


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

12


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


Top-Down Scalability Bottom-Up Scalability

UDDI

Today:Scalability carefully planned from top down

Tomorrow:Scalability grows from bottom up• Use UDDI registry to locate extra resources

13


Platform Dependence Platform Irrelevance

.Net Java J2EE

Today:Platform independence is an unrealized dream• DCOM & CORBA not cost-effective cross-platform• EAI very expensive & complexTomorrow:Systems communicate via Web Services interfaces• Platforms provide development & execution

environments only


Dictatorship Model Federation Model

Today:• Tightly coupled enterprise application suitesTomorrow:• Loosely coupled collections of federated Services

SAP

Siebel

14


A Web Services Roadmap

ZapThink Web Services RoadmapPr

imar

y ro

adbl

ocks

Invo

catio

n st

yle

Prim

ary

use

2003-2004 2004-2005 2005+2002-2003

Internal Focus

External (B2B) Focus

Full embedding of Web Services

Static binding to static Services

Dynamic binding to static Services

Discover & bind at runtime (JIT integration)

Security

Management

Transactions

Billing & Metering

Business WebProcess Automation

Orchestration & Workflow

Source: Copyright © 2002 ZapThink LLC

Robust registry services


WS Sizing and Growth

Total Market: Total Market: $15.5B by 2005$15.5B by 2005

Web Services Market Aggregate

0

2

4

6

8

10

12

14

16

18

2000 2001 2002 2003 2004 2005

Source: ZapThink, LLC

($ B

illio

n)

Web Services Management

Web Services ApplicationDevelopmentWeb Services Platforms

WEB SERVICES MARKET SIZE ($B)2000 2001 2002 2003 2004 2005

Web Services Platforms 0.1 0.3 0.8 2 4.2 7.9Web Services Application Development 0.02 0.05 0.1 1 2.5 5Web Services Management 0.01 0.03 0.08 0.3 1 2.5

15


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 www.zapthink.com

Ronald [email protected]

web services tutorial pt. 1 - doveltech.com · the large upper petal of the flower of a pea or...

Documents