Web Services A look to the future

1
Web Services A look to the future

• By Dr Colin Adam

2
WebServices.Org

• 33K members
• 12 Sponsors
• Over 1000 articles
• 300K page views per month
• All Open Source
• Editorials by Alan Kotok, David Orchards, Eric
  Newcomer.

3
Web Services Today

• SOAP provides message interoperability between
  software components
• WSDL provides description of service to provide
  interoperability between development tools
• These successes have lead to developers wanting
  more capabilities
• So where do we go from here?

4
We Need More Standards

• WS-AcknowledgementWS-ActiveProfileWS-Addre
  ssingWS-AttachmentsWS-AuthorizationWS-Atomic
  TransactionWS-BusinessActivityWS-CAFWS-Callb
  ackWS-Coordination WS-FederationWS-Inspectio
  nWS-Manageability WS-PassiveProfile
  WS-EndpointResolutionWS-MessageData
  WS-MetadataExchange WS-PolicyWS-PolicyAsserti
  onsWS-PolicyAttachment WS-ProvisioningWS-Pri
  vacyWS-ReferralWS-ReliabilityWS-ReliableMess
  aging WS-RoutingWS-ReferralWS-SecureConversa
  tionWS-SecurityWS-SecurityPolicyWS-Transacti
  onWS-TransmissionControlWS-TrustBPEL4WSWS-
  ChoreographyWSRPWSXL

5
Standards are good..

• "These are the infrastructure pieces that will
  lead to an explosion in web services Bill Gates
• BUT
• We face a key engineering challenge How do we
  give Web services new security, reliability, and
  transaction capabilities without adding more
  complexity than needed Donald Ferguson, IBM

6
A basis for the future

• A general-purpose, composable protocol framework
• Protocols are factored from both transports and
  application semantics
• Architecture is metadata-driven, policy-based
• Broad industry partnership

7
The Protocol Framework
SecurityWS-Security WS-Trust WS-Federation
ReliabilityWS-Reliable Messaging
TransactionsWS-Transaction WS-Coordination
Metadata WSDL, WS-Policy,
Messaging SOAP, WS-Addressing,
XML XML, XSD, XPath,
Transports HTTP, UDP,

8
Composing a message
ltSEnvelope gt ltSHeadergt ltwsaReplyTogt
ltwsaAddressgthttp//business456.com/User12lt/
wsaAddressgt lt/wsaReplyTogt
ltwsaTogthttp//fabrikam123.com/Trafficlt/wsaTogt
ltwsaActiongthttp//fabrikam123.com/Traffic/Stat
uslt/wsaActiongt ltwssecSecuritygt
ltwssecBinarySecurityToken
ValueType"wssecX509v3"
EncodingTypewssecBase64Binary"gt     
dWJzY3JpYmVyLVBlc..eFw0wMTEwMTAwMD
lt/wssecBinarySecurityTokengt
lt/wssecSecuritygt ltwsrmSequencegtzzz
ltwsuIdentifiergthttp//fabrikam123.com/seq1234lt/ws
uIdentifiergt ltwsrmMessageNumbergt10lt/wsrm
MessageNumbergt lt/wsrmSequencegt
lt/SHeadergt ltSBodygt ltappTrafficStatus
xmlnsapp"http//highwaymon.org/payloads"gt
ltroadgt520Wlt/roadgtltspeedgt3MPHlt/speedgt
lt/appTrafficStatusgt lt/SBodygt lt/SEnvelopegt
Addressing
Security
Reliability
9
Then What?

• Assume we have the standards and architecture
• Standards are no good without implementations
• Standards need to be policed
• How will any developer possibly use them since
  they are complicated and numerous?

10
Implementations

• Java Community Process lots of JSRs on the go
• Microsofts Indigo
• New tools such as Sun Java Studio Creator (out
  soon), Microsoft Visual Studio, BEA WebLogic
  Workshop, Eclipse

11
Developer Utopia

• Drop down menu of Web services specific to
  his/her IDE settings
• Intellisense Web services calls
• Automatic serialisation of data into XML
• Automatic performance tweaking
• Orchestration/Business Logic mapping
• Visual Data Mapping to legacy
• Automatic handling of security, reliability,
  transactions.
• Constraints placed on declarations possible

12
BEAs Weblogic Workshop
13
Indigo

• Indigo unifies a wide range of transports (HTTP,
  TCP, UDP, IPC), security mechanisms (public and
  symmetric keys, certificates), topologies
  (point-to-point, end-to-end through
  intermediaries, peer-to-peer, publish-and-subscrib
  e), and assurances (transacted, reliable,
  durable) enabling Indigo to provide rich
  connectivity to many existing systems. Don Box

14
What Microsoft Says

• "Indigo" is a new approach to building and
  running connected systems built from the ground
  up around the Web services architecture. BillG
• You can either do a lot in declarative
  statements to let you build these services. If
  you go to the next level down in the
  architecture, there are connectors and channels
  for you to import Jim Allchin

15
Policing The Standards

• Standards are held at different organisations
• Implementations need to interoperate
• Vendors needs somewhere to talk
• Test tools for compatibility

WS-I fulfills a need by providing clarifications
and constraints on those de facto standards that
will enable vendors and developers to implement
and use these technologies in an interoperable
manner. Chris Ferris speaking to ws.org
16
A few challenges for the future

• Extensibility - Need to avoid big-bang upgrades
  The Web does this well
• Evolvability Need to work on versioning
  forwards-backwards compatibility
• Early binding re-use tried and trusted
  semantics and stick to them
• Asynchronous lets not wait for each other

17
My predications

• 2004 will see some final specifications on QoS
  going through OASIS/W3C
• 2005 Indigo will go head to head with Java and
  win a lot of hearts and minds
• 2006 80 code on new projects will be WS-I
  complaint
• 2007 Peoples lives will be made easier with Web
  services
• 2010 nearly all software created from within a
  SOA and XML natural language tools
• 2020 NHS changes its name to NHWS (National
  Health Web Service)
• 2030 - Last mainframe sold.

18
NHS -gt NHWS

• The NHS requires new protocols and
  implementations now, not later.
• Stay away from RYO approaches.
• Open source has a lot of advantages and is just
  as good, if not better
• Think in terms of loose coupling and constraints
  therein
• Get some good IT Architects
• Decide what will join the web services together

19
The end

• Any Questions?

20
The Future is in Clear Definition

• An application accessible by others over the
  Web M Fisher Sun Tutorial
• self-contained modular business applications
  that have open Internet orientated, standards
  based interfaces UDDI.org
• standardized way of integrating web applications
  using XML, SOAP, WSDL and UDDI over an Internet
  backbone -Webopedia

21
The W3C Gets It Right

• A Web service is a software system designed to
  support interoperable machine-to-machine
  interaction over a network. It has an interface
  described in a machine-processable format
  (specifically WSDL). Other systems interact with
  the Web service in a manner prescribed by its
  description using SOAP-messages, typically
  conveyed using HTTP with an XML serialization in
  conjunction with other Web-related standards

22
(No Transcript)