1 / 15

Web Service Future

Web Service Future. CS409 Application Services. Even Semester 2007. Web Service Roadmap. Three phases of Web Service evolution: Age of invention the past. Age of development the past and current. Age of mainstream acceptance the current and future

shasta
Download Presentation

Web Service Future

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. Web Service Future CS409 Application Services Even Semester 2007

  2. Web Service Roadmap • Three phases of Web Service evolution: • Age of invention • the past. • Age of development • the past and current. • Age of mainstream acceptance • the current and future • until when …?How long is the cycle for this technology…?

  3. Age of Invention • This is when WS has just been invented. • The concept of using XML as the basis of message exchange format for distributed computing has just began. • Introduction of 1st version “core” specifications: SOAP 1.1, WSDL 1.1, UDDI 1.0 • Reach its peak at 2002-2003 when lots of specifications with “WS” in their names were introduced. • Initial product and tool to support WS were also released.

  4. Age of Development • This is when the age of pragmatic effort to make the technology useful for serious business computing. • 2nd iteration of “core” specifications: SOAP 1.2, WSDL 2.0, UDDI 3.0 • Final standardization of specifications began to emerge, e.g. WS-Security. • The vendor product is getting maturity and usefulness, focusing on the practical of implementing secure, reliable, and manageable web services.

  5. Age of Mainstream Acceptance • This is when the underlying technology (Java) and concept of WS will start become “boring” (no excitement with the new features). • Dominated by broad adoption of WS and SOA by businesses and non-businesses organizations. • Most of the innovation will be in best practice. • Main issues: pragmatic product features and interoperability among products.

  6. Short-Term Trends of WS • Combination of specifications • Problem: hidden cost of adopting and understanding new specifications. • Option: use new specification or stay with current one? • Key consideration: when will we have “enough” specifications? Is it worth it to implement the new one? How about just mix them? • Complexity • Problem: too many specifications  too complex infrastructure ! • Key consideration: base specification is a must (XML, SOAP, WSDL). How about the others (UDDI vs internal registry, WS-Security vs WSRM)? Is there any overlapping? Which specifications that we need to focus on?

  7. Short-Term Trends of WS (2) • Composability • Problem: which specifications can be well-fitted to one another? • Key consideration: don’t use specs that will lock you. • Performance • Problem: XML is so flexible  incorporate too many stuffs in it  decreasing performance. • Option: using other core technology? ebXML? XML-Binary? Fast Infoset? New protocol? • Key consideration: how about interoperability?

  8. Short-Term Trends of WS (3) • Interoperability • Problem: should we use existing or build new? • Key consideration: only use WS-I organization approved specifications. • Security • Problem: WS supposedly open standard but security is a must. • Key consideration: is WS-Security specification enough? Are all products out there comply with WS-Security? Do we need to improve the network infrastructure security?

  9. Medium-Term Trends of WS • Embedded Web Service • WS will be deep-rooted into vendor’s integration runtimes, tooling, and system management. • WS integration into commercial products will be seamless and becoming “must-have” feature, e.g. XML-aware firewall. • Emerging best practices • Focus will shift from development of new technology and standards into how to best use them. • Widespread adoption of BPEL, BPEL-oriented business process will become market trend.

  10. Medium-Term Trends of WS (2) • Policy-based interoperability • Manage diversity through policy. • Combination of WSDL 2.0 and WS-Policy will boost interoperability and exploit WS composability. • Service-Level Agreement [SLA] • How well WS is talking to one another. How to measure the QoS? • New specification: WS-Agreement (probably imposed monetary and compensation term for failure scenarios).

  11. Medium-Term Trends of WS (3) • On-Demand computing in WS • More flexible WS infrastructure with affordable cost. • Business Level Standards • Specifications will break down into specific line-of-business level. • Increasing role of Enterprise Service Bus • Enable plug-and-play WS features, enforce policy and specifications, etc.

  12. Medium-Term Trends of WS (4) • SOA based portals • Portal will adapt WS technologies, such as WS Remote Portlets. • Easier to create portal to exploit services offered by businesses. • Business Activity Monitoring (BAM) • Analyzing message traffic to detect certain patterns then issue logical warnings. • When WS is a common gateway of message flows, company can focus on it to build business early-warnings capable system.

  13. Long-Term Trends of WS • SOA based application architecture • Existing software will be wrapped by WS. • Existing software will be decomposed into collections of WS. • New software will be created from scratch with collaborating WS in mind. • Value networks • Multiple business partners fulfilling customers’ needs together. • WS will be the core approach for companies to participate in value network.

  14. Long-Term Trends of WS (2) • Semantics Web Service • Automatically detect that two WS provide the same functionalities although their port types, operations, and messages are named differently. • Increase the “loose-coupling” of WS and improve the independency.

  15. Thank You Doddy Lukito dlukito@infinitechnology.com dlukito@alumni.carnegiemellon.edu

More Related