VP Innovation at Axway, Co-founder at Vordel

Mark O'Neill

Subscribe to Mark O'Neill: eMailAlertsEmail Alerts
Get Mark O'Neill via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn

Related Topics: Virtualization Magazine, SOA & WOA Magazine

Virtualization: Article

What Happens When SOA and Virtualization Intersect?

Service Virtualization in a Web Services World

Virtualization is a buzzword that is living up to its hype as it takes hold in IT. It has spawned magazine covers, conferences, and analyst reports, and all with good reason. Virtualization allows applications to be deployed in a highly efficient manner. By taking the physical servers out of the equation, virtualization allows applications to be deployed across a number of servers, or for multiple operating systems to run simultaneously on one server. In this way, an organization can scale its applications by seamlessly adding hardware, or by adding more instances of operating systems to its servers.

In the world of Web Services, in a "service-oriented architecture" (SOA), applications are deployed as services over the network. This means that if an application wants to use components of another application, it simply accesses this other application over the network. The services in an SOA are both language- and platform-neutral, so they can be called from .NET applications or Java applications, in Windows, Linux, or Solaris. How does virtualization apply to SOA? In this article, we look at the intersection of SOA and virtualization, which is service virtualization.

"Service virtualization" is made possible by XML gateways. Over the past three years, XML gateways have emerged as a prime delivery platform for XML applications. An XML gateway is either delivered as an appliance or as software. It proves functionality that is essential to the successful delivery of Web Services, such as security, XML processing acceleration, and XML routing. XML gateways effectively "front" back-end Web Services by creating so-called "virtual services" that act as proxies in front of the real services. For example, if an organization has used .NET to create a Web Service called "calculateStateSalesTax", then an XML gateway can be used to create a virtual service in front of the service. Then, the client accesses the virtual service at the XML gateway rather than the actual Web Service.

This architecture is depicted in Figure 1. Clients can now connect to the virtual services rather than directly to the Web Services. The XML gateway makes this possible.

More Stories By Mark O'Neill

Mark O'Neill is VP Innovation at Axway - API and Identity. Previously he was CTO and co-founder at Vordel, which was acquired by Axway. A regular speaker at industry conferences and a contributor to SOA World Magazine and Cloud Computing Journal, Mark holds a degree in mathematics and psychology from Trinity College Dublin and graduate qualifications in neural network programming from Oxford University.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.