8.4 QA: A final reprise and recap


8.4 Q&A: A final reprise and recap

Q: Can the value proposition of XML Web services be summarized in one pithy sentence ?

 a : yes. web services provide a standards-based mechanism that provides new e-business applications with the programmatic equivalent of the now familiar, explore-and-locate, interactive web experience-albeit with the sought-after services being delivered by xml-speaking, modular software components.

Q: Is the XML Web services model flawed in any way?

 a : no. the core xml model, consisting of xml, soap, wsdl, and uddi, is not technically flawed and by now has been repeatedly validated in multiple ways and in diverse forums by the acknowledged doyens of the computer industry, including ibm, microsoft, sun, oracle, sap, and h-p-not to mention w3c, the guardians of the web. the fact that some of the security-, management-, and transaction processing related specifications that pertain to web services are still being worked on does not, in any way, mean that the fundamental model is flawed. the new specifications are enhancements. given that web services facilitate web-based distributed computing, the core web-services specifications will continue to be complemented and augmented with new initiatives as technology and usage trends evolve.

Q: Is there any reason to steer clear of Web services?

 a: no, not really. the core web-services model is technically very sound and becomes even more powerful and compelling as additional functionality is introduced via new versions of the key specifications such as soap 1.2 and uddi version 3. in addition, the work being done to ensure seamless interoperability by ws-i, as well as the various test suites (e.g., soap 1.2 and j2ee 1.4), gilds the lily even further. yes, there are data security and privacy-related concerns, but these in the end are no different from those already addressed in the realms of e-commerce, online banking, and web trading. obviously, if sensitive data is going to be sent or received from a web service, one must use proven authentication and encryption technology such as digital certificates and ssl. but there is no reason to steer clear of web services.

Q: Why have Web services been so slow to live up to their expectations?

 a: web services provide an enabling technology. as a software component methodology they simplify and expedite application development. consequently, the fortunes of web services are directly tied to the health of the application development industry. the key specifications for xml web services came to be in september 2000. thus, realistically, web services were not ready for prime-time use until mid-2001. but after the billions, if not trillions, of dollars that were spent on y2k around the globe, enterprises had by then slowed down on their it spending, partly to take a breather after the y2k exertions and also to compensate for all the monies spent. however, before it budgets and spending could be reevaluated and reenergized there was the dot.com implosion, followed by 9/11. suffice to say that enterprises have not spent lavishly on it expansion during the global economic slowdown that came on the heels of 9/11. with not too many new applications being developed, the demand for the nascent web-services technology has, understandably, not lived up to the original predictions and ensuing expectations.

Q: What is a killer application for Web services?

 a: portal-related applications, whether for corporate or public portals, continue to be an obvious, fertile field for web-services exploitation. portal applications thrive on functionality. a portal, particularly public portals, cannot ever have enough functionality. portal users demand and devour new functionality. providing value-added, best-of-breed functionality is the primary raison d tre for web services. thus, web services are ideally poised to provide portal application developers with the value-added functionality that they constantly crave. portal technology is now being extended to accommodate voice applications as well as specific services for wireless, handheld devices-in particular, smart phones. web services, yet again, provide an ideal, standards-based mechanism for acquiring some of the required functionality-especially given that there is already a well-established standard, voicexml, for making internet content and information accessible via voice and phone.

Q: Is it possible that there will be derivatives of the current XML Web-services model?

 a: yes-and this is already happening. there are some who wish to use the xml model directly over http or a similar transport protocol without resorting to soap. there are others who advocate the basic software component invocation model, across the web, but without xml. obviously, any move away from xml will limit the global applicability and extensibility of such a service. but non-xml-based, industry- or application-specific schemes could be optimized to be very efficient for designated scenarios. this, however, would be deja vu. but given the dynamics and politics of the web, such derivatives are inevitable and attest to the inherent innovation within this industry.

Q: What is the real cost associated with Web services?

 a: the real cost one needs to be always cognizant of when it comes to web services is that of the lost opportunity costs one could incur by not exploiting web services! this lost opportunity cost will, invariably, far outweigh the cost of using or providing web services. in other words, shying away from web services could cost you more money than what you spend on embracing them. this is not mere hyperbole. web services are an enabling technology. creatively exploiting best-of-breed, third-party web services when developing new applications will compress development and test schedules-and thus reduce overall development costs. it will also be possible to offer more functionality and get to market faster. web services will thus enhance competitiveness. if you already own application software, not investigating the possibility of offering some functionality from those applications as possible revenue-producing web services could also cost you money. so when it comes to web services, rather than asking what will web services cost me, instead ponder on what will i stand to lose if i don t embrace web services.

Q: Is there any good reason for procrastinating further in terms of making use of Web services?

 a : no. web-services technology in late 2003 is viable, proven, and powerful. the new specifications that are being worked on, even those related to security and management, are embellishments, as opposed to replacements, for the existing model. the new specifications will provide tighter, xml-centric integration. however, existing security and management solutions, in particular digital certificates, ssl, and total enterprise management, can be used very effectively with web services, albeit in implementation-specific flavors, irrespective of where the new specifications stand. thus, there is really nothing to be gained by procrastinating.

Q: Is there a Web site that will provide updates to the material covered in this book?

 a: www.xmlweb.org is a new vendor-neutral web site committed to propagating xml and web services related information targeted at an executive-level audience.

Q: What is the bottom line when it comes to XML Web services?

 a : xml web services represent the latest iteration when it comes to contemporary software component technology. it is xml based and geared for use across the internet, though it can also be used very effectively on intranets and extranets. web services are modular, self-contained, self-describing, self-advertising software components. thus, one can build new applications by reusing or assembling components from within and outside of an enterprise. web services dramatically and positively alter everything related to applications, both on the supply and the demand side. web services expedite, simplify, and reduce the cost of new application development. they also allow valuable software functionality embedded within existing applications to be isolated and reused. since they are totally web-centric, developers looking for sources for best-of-breed software functionality now have ready access to the entire worldwide software community without the hindrance of geographical, political, or trade boundaries. the bottom line is that web services have the power and reach to revolutionize application development, from ground up, in the years to come. the web browser opened up hitherto unimagined vistas of information for people. web services are poised to do the same on a programmatic basis for applications.

Answers

A : Yes. Web services provide a standards-based mechanism that provides new e-business applications with the programmatic equivalent of the now familiar, explore-and-locate, interactive Web experience ”albeit with the sought-after services being delivered by XML-speaking, modular software components .

A : No. The core XML model, consisting of XML, SOAP, WSDL, and UDDI, is not technically flawed and by now has been repeatedly validated in multiple ways and in diverse forums by the acknowledged doyens of the computer industry, including IBM, Microsoft, Sun, Oracle, SAP, and H-P ”not to mention W3C, the guardians of the Web. The fact that some of the security-, management-, and transaction processing “ related specifications that pertain to Web services are still being worked on does not, in any way, mean that the fundamental model is flawed. The new specifications are enhancements. Given that Web services facilitate Web-based distributed computing, the core Web-services specifications will continue to be complemented and augmented with new initiatives as technology and usage trends evolve .

A: No, not really. The core Web-services model is technically very sound and becomes even more powerful and compelling as additional functionality is introduced via new versions of the key specifications such as SOAP 1.2 and UDDI Version 3. In addition, the work being done to ensure seamless interoperability by WS-I, as well as the various test suites (e.g., SOAP 1.2 and J2EE 1.4), gilds the lily even further. Yes, there are data security and privacy-related concerns, but these in the end are no different from those already addressed in the realms of e-commerce, online banking, and Web trading. Obviously, if sensitive data is going to be sent or received from a Web service, one must use proven authentication and encryption technology such as digital certificates and SSL. But there is no reason to steer clear of Web services.

A: Web services provide an enabling technology. As a software component methodology they simplify and expedite application development. Consequently, the fortunes of Web services are directly tied to the health of the application development industry. The key specifications for XML Web services came to be in September 2000. Thus, realistically , Web services were not ready for prime-time use until mid-2001. But after the billions, if not trillions, of dollars that were spent on Y2K around the globe, enterprises had by then slowed down on their IT spending, partly to take a breather after the Y2K exertions and also to compensate for all the monies spent. However, before IT budgets and spending could be reevaluated and reenergized there was the dot.com implosion, followed by 9/11. Suffice to say that enterprises have not spent lavishly on IT expansion during the global economic slowdown that came on the heels of 9/11. With not too many new applications being developed, the demand for the nascent Web-services technology has, understandably, not lived up to the original predictions and ensuing expectations.

A: Portal-related applications, whether for corporate or public portals, continue to be an obvious, fertile field for Web-services exploitation. Portal applications thrive on functionality. A portal, particularly public portals, cannot ever have enough functionality. Portal users demand and devour new functionality. Providing value-added, best-of-breed functionality is the primary raison d tre for Web services. Thus, Web services are ideally poised to provide portal application developers with the value-added functionality that they constantly crave. Portal technology is now being extended to accommodate voice applications as well as specific services for wireless, handheld devices ”in particular, smart phones. Web services, yet again, provide an ideal, standards-based mechanism for acquiring some of the required functionality ” especially given that there is already a well-established standard, voiceXML, for making Internet content and information accessible via voice and phone.

A: Yes ”and this is already happening. There are some who wish to use the XML model directly over HTTP or a similar transport protocol without resorting to SOAP. There are others who advocate the basic software component invocation model, across the Web, but without XML. Obviously, any move away from XML will limit the global applicability and extensibility of such a service. But non-XML-based, industry- or application-specific schemes could be optimized to be very efficient for designated scenarios. This, however, would be deja vu. But given the dynamics and politics of the Web, such derivatives are inevitable and attest to the inherent innovation within this industry.

A: The real cost one needs to be always cognizant of when it comes to Web services is that of the lost opportunity costs one could incur by not exploiting Web services! This lost opportunity cost will, invariably, far outweigh the cost of using or providing Web services. In other words, shying away from Web services could cost you more money than what you spend on embracing them. This is not mere hyperbole. Web services are an enabling technology. Creatively exploiting best-of-breed, third-party Web services when developing new applications will compress development and test schedules ”and thus reduce overall development costs. It will also be possible to offer more functionality and get to market faster. Web services will thus enhance competitiveness . If you already own application software, not investigating the possibility of offering some functionality from those applications as possible revenue-producing Web services could also cost you money. So when it comes to Web services, rather than asking What will Web services cost me, instead ponder on What will I stand to lose if I don t embrace Web services.

A : No. Web-services technology in late 2003 is viable , proven, and powerful. The new specifications that are being worked on, even those related to security and management, are embellishments, as opposed to replacements , for the existing model. The new specifications will provide tighter, XML-centric integration. However, existing security and management solutions, in particular digital certificates, SSL, and total enterprise management, can be used very effectively with Web services, albeit in implementation-specific flavors, irrespective of where the new specifications stand. Thus, there is really nothing to be gained by procrastinating.

A: www.xmlweb.org is a new vendor-neutral Web site committed to propagating XML and Web services “related information targeted at an executive-level audience.

A : XML Web services represent the latest iteration when it comes to contemporary software component technology. It is XML based and geared for use across the Internet, though it can also be used very effectively on intranets and extranets. Web services are modular, self-contained, self-describing , self-advertising software components. Thus, one can build new applications by reusing or assembling components from within and outside of an enterprise. Web services dramatically and positively alter everything related to applications, both on the supply and the demand side. Web services expedite, simplify, and reduce the cost of new application development. They also allow valuable software functionality embedded within existing applications to be isolated and reused. Since they are totally Web-centric, developers looking for sources for best-of-breed software functionality now have ready access to the entire worldwide software community without the hindrance of geographical, political, or trade boundaries. The bottom line is that Web services have the power and reach to revolutionize application development, from ground up, in the years to come. The Web browser opened up hitherto unimagined vistas of information for people. Web services are poised to do the same on a programmatic basis for applications.




Web Services[c] Theory and Practice
Web Services[c] Theory and Practice
ISBN: 1555582826
EAN: N/A
Year: 2006
Pages: 113

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net