acm - an acm publication


XML, web services and the changing face of distributed computing

Ubiquity, Volume 2002 Issue April, April 1- April 30, 2002 | BY Frank P. Coyle 


Full citation in the ACM Digital Library

A new kind of network offers a world of possibilities for moving data and building application architectures centered around common Internet protocols.

A new kind of network offers a world of possibilities for moving data and building application architectures centered around common Internet protocols.

The face of distributed computing is changing. The client server networks that dominated the 1980s and early 1990s are giving way to a new kind of network built around the Web using open protocols and a new data representation language called XML. The implication of this shift is that organizations, instead of focusing on networks and transport, can now shift their attention to data and its role in cementing relationships with customers, partners and suppliers using the global Web already in place.

This shift in focus from transport to data has been underway since the early 1990s when Tim Berners-Lee augmented an in-place Internet network with a file request protocol called HTTP, a file format known as HTML, and software called a browser for retrieving and displaying HTML. The result was the Web. But it wasn't until the emergence of the XML in the mid-1990s, that the Web began to be seen as a vehicle for distributed enterprise computing. Interestingly, Microsoft was early seeing the writing on the wall and in a deft move, re-engineered itself from a desktop applications and operating system company to one focused on delivering XML-based Web solutions and services. Microsoft's current .NET initiative, centered on the notion of software as a Web service, is changing how companies now build enterprise software. Not to be outdone by Microsoft, Sun and its Java juggernaut have fully embraced XML and Web Services as crucial to the success of the enterprise Java initiative. Both the standard Java platform (J2SE) and its industrial strength enterprise cousin, J2EE, have embraced XML, as have J2EE implementers including IBM, BEA, Oracle, Sun and HP.

What's amazing in all of this is that in just a short period of time, XML, a very simple data description language, in combination with the same simple protocols we use to surf the Web, has changed the name of the game in distributed computing.

What is XML

XML, the Extensible Markup Language, is a metalanguage (literally a language about languages) defined by the World Wide Web Consortium (W3C), one of the main organizations driving the push to open Web standards.

The story behind XML is very much the story of the Web. Just as the Web, in a few short years, has influenced almost every aspect of our lives, from work, to play, to social interaction, so has XML, a universal data description language, affected the distributed computing landscape. The result has been the opening up of new opportunities for gaining competitive advantage by moving XML using accepted Internet standards.

In its simplest sense, XML is a set of rules and guidelines for describing structured data in plain text rather than proprietary binary representations. However, as a phenomenon, XML goes beyond its technical specification. Since its standardization by the W3C in 1998, XML has been the driving force behind numerous other standards and vocabularies that are forging a fundamental change in the software world.

Much of XML's success stems from its simplicity. Technically, it's a language for creating other languages based on the insertion of tags to help describe data. However, XML is actually more than just tags. To see what we mean by this, let's look at a simple XML document that describes the purchase of 100 shares of Zorkon stock.

<?xml >

<order transaction="buy">

<company>Zorkon Ltd</company>



There are several important basic points to observe about this XML:

-- It's readable. Except for the first line which is required for all XML documents, it's easy to figure out what's going on. It doesn't take a degree in computer science to figure out that the data relates to the purchase of 100 shares of stock.

-- There are three elements: order, company and shares.

-- The order element contains the attribute transaction.

-- Data may be stored in either elements or attributes.

-- Elements and attributes are named to give the data meaning.

-- Start tags (e.g. ) and end tags (e.g. ) define elements that are the basis for XML tree-structured representations of documents.

-- Elements can contain text data and/or other elements.

Although there is more to XML than the few simple rules listed above, XML's strength is that its essence can be grasped and understood quite easily. As a simple dta description language, XML forms the core of a family of supporting technologies that can be combined in a variety of ways to meet a wide range of requirements. Figure 1 illustrates XML and its technology family.

Figure 1. The XML Technology Family

Much of the XML advantage is that widespread industry support exists for XML. Numerous tools and utilities are available with Web browsers, databases, and operating systems, making it easier and less expensive for small and medium-sized organizations to import and export data in XML format. A large family of XML support technologies is available for the interpretation and transformation of XML data for Web page display and report generation, and major relational database vendors now have the native capability to read and generate XML data.

This widespread support for XML has opened the door to creative ideas about delivering XML over standard web protocols such as HTTP, FTP or Simple Mail Transfer Protocol (SMTP).

XML: The Three Revolutions

To understand XML's impact, it's helpful to look at XML in the context of three revolutions centered on XML and the Web. These include a revolution in how we think about and use data, a revolution in software architecture that has moved us from tightly coupled networks to a more loosely coupled, open Web space, and a revolution in how we build complex software.

The Data Revolution

Prior to XML, data was very much proprietary, closely associated with applications that understood how data was formatted and how to process it. Now, XML-based industry-specific data vocabularies provide alternatives to specialized Electronic Data Interchange (EDI) solutions by facilitating B2B data exchange and playing a key role as a messaging infrastructure for distributed computing. XML's strength is its data independence. XML is pure data description, not tied to any programming language, operating system or transport protocol. In the grand scheme of distributed computing this is a radical idea. The implication is that we don't require lock-in to programmatic infrastructures to make data available to Web-connected platforms. In effect, as Figure 2 illustrates, data is free to move about globally without the constraints imposed by tightly coupled transport dependent architectures. XML's sole focus on data means that a variety of transport technologies may be used to move XML across the Web. As a result, protocols such as HTTP have had a tremendous impact on XML's viability and have opened the door to alternatives to CORBA, RMI and DCOM, which don't work over TCP/IP. XML does this by focusing on data and leaving other issues to supporting technologies.

Figure 2. The Data Revolution

The Architectural Revolution

The architectural revolution surrounding XML is reflected in a move from tightly coupled systems based on established infrastructures such as CORBA, RMI and DCOM, each with their own transport protocol, to loosely coupled systems riding atop standard Web protocols such as TCP/IP. Although the transport protocols underlying CORBA, RMI, and DCOM provide for efficient communication between nodes, their drawback is their inability to communicate with other tightly coupled systems or directly with the Web. Loosely coupled Web-based systems, on the other hand, provide what has long been considered the Holy Grail of computing: universal connectivity. Using TCP/IP as the transport, systems can establish connections with each other using common open-Web protocols. Although it is possible to build software bridges linking tightly coupled systems with each other and the Web, such efforts are not trivial and add another layer of complexity on top of an already complex infrastructure. As illustrated in Figure 3, the loose coupling of the Web makes possible new system architectures built around message- based middleware or less structured peer-to-peer interaction.

Figure 3. The Architecture Revolution

XML plays a key role in this new architecture for distributed computing through a new XML protocol language called SOAP, the Simple Object Access Protocol. Although SOAP has the word object as part of its acronym, the protocol is not object-oriented in the sense of C++ or Java. Rather, SOAP simply defines a set of XML tags for moving XML data around the Web using standard Web protocols, accomplishing in one simple initiative what client-server computing had been trying to do for over a decade. Associated with this ability to move data freely across the Web is the rise in the use of messaging servers and software that sit between conversational participants. These servers, supporting what is known as Message Oriented Middleware, are playing an increasingly important role in the new extended enterprise by providing guarantees of delivery and the ability to broadcast communications to multiple recipients.

The Software Revolution

The reason this happened so quickly relates to the third revolution, the software revolution -- a new way of thinking about how to build complex systems.

During the 1970s and 1980s, software was constructed as monolithic applications built to solve specific problems. The problem with large software projects is that, by trying to tackle multiple problems at once, the software is often ill suited to adding new functionality and adapting to technological change. In the 1990s a different model for software emerged based on the concept of simplicity. Instead of trying to define all requirements up front, this new philosophy was built around the concept of creating building blocks capable of combination with other building blocks that either already existed or were yet to be created. Figure 4 illustrates the software revolution.

A case in point is the Web. After decades of attempts to build complex infrastructures for exchanging information across distributed networks, the Web emerged from an assemblage of foundational technologies such as HTTP, HTML, browsers and a longstanding networking technology known as TCP/IP that had been put in place in the 1970s.

Figure 4. The Software Revolution

Web Services

One aspect of the new extended enterprise is the emergence of Web services. Web services is an ambitious initiative that is moving the Web to new levels of B2B (that is, software-to-software) interaction while trying to fulfill object technology's promise of reusable components from a service interface. For some, Web services represents the next evolutionary step for the Web, extending it from a network that provides services to humans to one that provides services to software looking to connect with other software.

A Web service can be anything from a movie review service, to a real-time weather advisory, to an entire hotel- and airline-booking package. The Web services technical infrastructure ensures that services even from different vendors will interoperate to create a complete business process. Web services take the object-oriented vision of assembling software from component building blocks to the next level. With Web services, however, the emphasis is on the assembly of services that may or may not be built on object technology.

From an enterprise perspective, a Web service is both a process and set of protocols for finding and connecting to software exposed as services over the Web. By building on standard Internet protocols such as HTTP and SOAP, developers can concentrate on what data to exchange instead of worrying about how to get it from point A to point B. To make things even easier, SOAP also defines an XML envelope to carry XML data, as well as a convention for doing remote procedure calls. This RPC capability allows Web service providers to advertise "call me here" so that a program (not a human) will be able to do so without concern for language or platform.

Figure 5. Web Services

As illustrated in Figure 5, XML, SOAP and Web Services define a new landscape for distributed computing that includes XML as the data, SOAP and HTTP as the protocols for moving data across the Web, and Web Services protocols such as UDDI and WSDL for the discovery and connection to those services. Playing a central role in this automatic Web-based discovery and lookup is a shift to a central repository that maintains data described in yellow pages for category search, white pages for direct name search, and green pages for details about making a connection. Whether these repositories exist behind or outside firewalls is up to the application implementation. However, the basic idea that companies or departments with services to offer can register and be discovered by clients seeking those services, is changing the face of the enterprise. While it remains to be seen how all this plays out, the bottom line is that we're moving into a new era of distributed interaction, driven by the Web and fueled by XML.


The simplicity of XML in combination with the Web has opened up new possibilities for moving data and for building new application architectures centered around common Internet protocols. Some of the changes brought about by XML include:

-- A reduced dependence on proprietary data formats for applications

-- A new way to do B2B data exchange using XML instead of the formats defined by traditional EDI systems

-- A shift from relying on tightly coupled systems such as CORBA, RMI, and DCOM to a more loosely coupled Internet-based framework centered around XML and SOAP

-- A change in focus from object-oriented to service-oriented software

-- The emergence of Web services as technology for discovering and connecting to Internet-based services

-- A move away from monolithic applications that attempt to do it all to a more organic software model that derives new capabilities from the combination of well-defined, limited in scope, software components.

Frank Coyle is a senior lecturer and director of the Software Engineering Program at Southern Methodist University in Dallas, Texas. He received his BS from Fordham College, an MS from Georgia Tech and a PhD from SMU. His recent book, XML, Web Services and the Data Revolution is published by Addison-Wesley.


how to compute the xml based distributed computing....?

��� kowsi, Mon, 25 Apr 2011 10:50:39 UTC

Leave this field empty