The SOA (Service-Oriented Architecture) strategy of application delivery can create profound competitive value by aligning and integrating technologies more flexibly around business goals. Enterprises strive to align development, integration and testing activities in an agile way to achieve expected cost and time-to-market benefits by collaborating and sharing technology assets across teams.

However, realizing the value of SOA on a larger, enterprise-wide scale can be difficult, if not impossible, without also leveraging Virtualization. Once you split up development teams to deliver SOA, you realize that all these teams still need access to the system to complete their development and testing jobs if you are going to realize that cost and agility benefit. Like SOA, Virtualization is not something you simply buy -- it is something you must do.

Let's take a look at the 4 ways IT departments are currently leveraging Virtualization:

1. Hardware Virtualization, which is the most often mentioned type of virtualization, is the process of running multiple copies of the operating system as Virtual Machines (VMs) within one physical hardware device. This offers some great cost, flexibility and risk management benefits for the internal applications running in the data center.

2. Test Bed Virtualization is an extension of virtualizing hardware, by Replicating a target server as a test environment, which can enable a given server to quickly be re-provisioned for a team's use, and/or "rolled back" to a previous Virtual Test Bed version if a problem arises with the current application. This is extremely valuable, though it is intended for use within a controlled server environment - attempting to replicate all the distributed components and apps that make up SOA would be tough.

3. Virtual Endpoints allow the SOA to define virtual locations for Services that need to be invoked, when in fact you’re completely shielded from the actual end point of the service itself. This is ideal for the dynamic processes inherent in SOA applications, as the physical address (or URL) of a Service may need to change dynamically depending upon when and how it is used as part of a given workflow. Often the Virtual Endpoint and necessary lookup information is stored as a definition in a centralized UDDI Registry, so the address can be routed according to the specific needs of the workflow.

4. Virtualized Services are the last and most SOA-centric instances of Virtualization. Virtual Services are either constructed synthetically from WSDL, or modeled from existing Services and underlying implementations. This newer use of Virtualization attempts to streamline development and deployment practices as a whole, by allowing teams to simulate the behavior of the distributed SOA application. This becomes important with SOA, as teams seek to collaborate on delivering and consuming a changing live application environment that is becoming increasingly constrained.

So, we can see that Virtualization happens at the data center, but it can also happen within your application design, development and deployment process.

Often when people ask me about virtualization, they are only thinking of the hardware benefits - when there are a lot more ways to leverage it in enterprise architectures to streamline the rest of the application lifecycle. I'll post more articles on Virtualization and SOA in the near future, and your questions or comments on this topic are welcome.

You do not have flash or javascript support.

Average (2 votes)

Reply