SOA enhancements through XML Networking

From Computing and Software Wiki

(Difference between revisions)

Revision as of 00:23, 7 April 2008

Service Oriented Architecture (SOA) enhancements through Extensible Markup Language (XML) Network has been a very discussed topic in the last few years. The performance and scalability of current SOA models are not sufficient to satisfy the increasing business demand of today's world. Web services for major companies are faced with extreme throughput issues that affect all the underlying applications that depend on such services. [1] This wiki discusses the approaches that can be taken to accelerate this service-sharing process by expanding the use of XML technologies throughout the middleware of the SOA framekwork. [2]

SOA Overview

Figure 1
Client and server interaction within a SOA framework. [8 ]

The web services concept provides a framework for sharing services across a network (such as the internet). Each of these services represent a group of objects and resources that are combined to provide a tool for business applications. Service-oriented architectures use these tools to build their custom applications: various services are grouped together to form the desired product (see figure 1). Therefore naturally the key factor for the success of SOA is interoperability. This means that services must be reachable from within any development framework: Java SE, .NET, etc. For such concept to become true various standards and regulations must be specified. [3] Such components will be discussed in the following section.

SOA Components

Figure 2
Messaging layer of a common SOA framework. [2 ]

The main "ingredients" for a web service layer, and essentially a service-oriented architecture are: UDDI, WSDL, SOAP and HTTP. Together they specify what the web service is and how to reach it, which is all the client application needs to know.

UDDI

Stands for Universal Description,Discovery and Integration.
Sponsored by OASIS.
An XML-based registry that allows businesses to list and search for web services. [4]

WSDL

Stands for Web Services Description Language.
An XML-based language that describes a web service.
The 2.0 version is a W3C recommendation. [5]

SOAP

Stands for Simple Object Access Protocol.
A protocol for exchanging XML-based messages over a network.
Provides a standard message format for services to use. [6]

HTTP

Stands for Hypertext Transfer Protocol.
It is used to transfer information through a network (intranet, of world wide web).
Allows for a communication channel between a client and a server. [7]

Enhancements through XML Networking

As noted above, all aspects of a service-oriented architecture are based on the XML standard. However it is strange to realize that a large number of existent SOA-based frameworks do not take advantage of the growing arsenal of XML-related technologies. [1]

Overview of Technologies

XSD

The XML Schema Technology is a W3C Standard that specifies the rules and structure of the related instances. Its initial design was to replace Document Type Definition (DTD), allowing for more complex internal structures. [1]

XSLT

XPath

XQuery

XML Encryption

Integrating XML Network

Integration of XML technologies inside a service-oriented architecture. [2 ]

FastSOA: the next step

References

1. Frank Cohen FastSOA: Accelerate SOA with XML, XQuery, and native XML database technology IBM.com February 7, 2006.
2. Silvano Da Ros Boosting the SOA with XMLNetworking, Cisco.com December 1, 2006.
3. Service-oriented architecture, Wikipedia April 6, 2008.
4. UDDI, Wikipedia March 25, 2008.
5. WSDL, Wikipedia March 7, 2008.
6. SOAP, Wikipedia April 3, 2008.
7. HTTP, Wikipedia April 6, 2008.
8. Hugo Haas SOA Diagram, W3C.org May 21, 2003.

0. Hao He What Is Service-Oriented Architecture, XML.com September 30, 2003

8.' Simon St. Laurent Describing your Data: DTDs and XML Schemas, XML.com December 1, 1999.

External Links

Signature

Demagaal 19:34, 6 April 2008 (EDT)

@@ Line 5: / Line 5: @@
 ==SOA Overview==
 [[Image:Soa_general_2.png|thumb|250px|right|'''Figure 1''' <br> Client and server interaction within a SOA framework. [http://www.w3.org/2003/Talks/0521-hh-wsa/slide5-0.html [8] ]]]
-The web services concept provides a framework for sharing services across a network (such as the internet).  Each of these services represent a group of objects and resources that are combined to provide a tool for business applications.  Service-oriented architectures use these tools to build their custom applications:  various services are grouped together to form the desired product (see figure 1).  The key factor for the success of SOA is interoperability.  This means that services must be reachable from within any development framework: Java SE, .NET, etc.  For such concept to become true various standards and regulations must be specified. [http://en.wikipedia.org/wiki/Service-oriented_architecture [3]]  Such components will be discussed in the following section.
+The web services concept provides a framework for sharing services across a network (such as the internet).  Each of these services represent a group of objects and resources that are combined to provide a tool for business applications.  Service-oriented architectures use these tools to build their custom applications:  various services are grouped together to form the desired product (see figure 1).  Therefore naturally the key factor for the success of SOA is interoperability.  This means that services must be reachable from within any development framework: Java SE, .NET, etc.  For such concept to become true various standards and regulations must be specified. [http://en.wikipedia.org/wiki/Service-oriented_architecture [3]]  Such components will be discussed in the following section.
 ===SOA Components===
 [[Image:Soa_general.jpg|thumb|250px|right|'''Figure 2''' <br> Messaging layer of a common SOA framework. [http://www.cisco.com/web/about/ac123/ac147/archived_issues/ipj_9-4/xml_networking.html [2] ]]] The main "ingredients" for a web service layer, and essentially a service-oriented architecture are:  UDDI, WSDL, SOAP and HTTP.  Together they specify what the web service is and how to reach it, which is all the client application needs to know.