V-Block – is it what SOA needs?

Every now and then you hear something that really makes you think! Well, it happened to me when I had Cisco, EMC, and VMware, talk me through their V-Block technology. It’s the launch product for their Virtual Computing Environment coalition, or VCE for short. Not heard of it? Well it’s only being launched today, November 3rd, and I think you certainly will be hearing about it as I expect it to make quite a splash on blogs and in the traditional press. After all it’s a pretty big news story in its own right when three strong players decide to get together: get the full background story from the three CIOs
We all know enterprises are changing in terms of their business and organisational models, driven by a variety of factors ranging from increased global competition, to expectations for more customisation of their products, even the introduction of online services and channels. This is placing much more emphasis on the way people both internally and externally communicate and interact to share expertise and make decisions faster in this dynamic environment; the collaboration and personalisation of the working place. This is the top layer in this diagram of functional activities and focuses on the connection and policy management of people and devices.


blog%20image V Block – is it what SOA needs?In the next layer down comes the business requirement to trade in differentiated ways to suit different markets, and access a bigger overall share of the potential overall market. You can think of it as how Volkswagen Audi Group, VAG, uses multiple brands: Audi, Volkswagen, Skoda, SEAT, to get more coverage of the overall market for cars and increase its share. In real life it’s likely to be even smaller granularisation such as positioning Volkswagen in a different way in Europe to South America, but you get the principle. Now think how the people and devices in the personalisation layer have to be flexibly connected to the differentiation layer? Extend that to think about this being all about the orchestration of clusters of ‘services’ rather than a handful of monolithic applications.
That’s going to be tough to manage and provide governance in this continually changing environment where change and flexibility is the key criteria for business success. It also has to connect in a reliable and policy managed manner to the third layer where the corporate processes that comprise the core competences of the enterprise. In the case of Volkswagen-Audi this is how they use common processes to design, build, ship, finance and service their products, in fact in many cases this is so well done that the same car platform supports multiple brands with a degree of differentiation over laying the common shared platform.
There needs to be a strong degree of stability here for an enterprise to operate effectively by optimising its core strengths. A point I covered in a previous post in which I emphasised the need for say twenty percent of an enterprise to be continually changing and adapting to the external market drivers in order to maximise competitive advantage, over eighty percent that should operate in a more stable manner that allows optimisation of resources and capabilities. Finally in the lowest fourth layer we have classic IT functionalities to record enterprise transactions and provide corporate compliance.
Okay now reflect on the provisioning for the two upper layers, a place of continual change based on people, and devices using services and not applications. Now reflect on why you would provision in the same way as for the classic IT around computers, and applications in a stable environment. It’s pretty clear that the only reasonable answer is that you wouldn’t do it the same way! Take some time to take a close look at the answer that the VCE coalition has come up with in its new V-Block technology. You can get behind some of the thinking by looking at two of their key technology leads views at Chuck Hollis’s blog and at Chad Sakac’s Blog.
Does it strikes you, as it struck me, that we really need to ask if provisioning with the current infrastructure optimised for applications, plus using some virtualisation, is going to be enough to handle a pure services environment with all that this means. V-Block might just be what we are looking for, and as a side affect it might answer a few questions about orchestration, and SOA issues too!

About the author

61.thumbnail V Block – is it what SOA needs? Capgemini Global Chief Technology Officer, Andy is a member of the Capgemini Group management board and advises on all aspects of technology-driven market changes, together with being a member of the Policy Board for the British Computer Society. Andy is the author of many white papers, and the co-author three books that have charted the current changes in technology and its use by business starting in 2006 with ‘Mashup Corporations’ detailing how enterprises could make use of Web 2.0 to develop new go to market propositions. This was followed in May 2008 by Mesh Collaboration focussing on the impact of Web 2.0 on the enterprise front office and its working techniques, then in 2010 “Enterprise Cloud Computing: A Strategy Guide for Business and Technology leaders” co-authored with well-known academic Peter Fingar and one of the leading authorities on business process, John Pyke. The book describes the wider business implications of Cloud Computing with the promise of on-demand business innovation. It looks at how businesses trade differently on the web using mash-ups but also the challenges in managing more frequent change through social tools, and what happens when cloud comes into play in fully fledged operations. Andy was voted one of the top 25 most influential CTOs in the world in 2009 by InfoWorld and is grateful to readers of Computing Weekly who voted the Capgemini CTOblog the best Blog for Business Managers and CIOs each year for the last three years.




This entry was posted in Uncategorized. Bookmark the permalink.

3 Responses to V-Block – is it what SOA needs?

  • Daniel Eason says:

    What a relieve to read a post/tweet/opinion which actually highlights what something like a Vblock stack can potentially do to fill current gaps between service and technology.
    Lets hope vblock in particular is not just another marketing exercise, will have eventual results, is affordable and is not just a technology mash up being employed in order to try and shift all the EMC(vmax) and Cisco(UCS) technology which has yet to start climbing the main stream adoption curve.

  • Mark Kerr says:

    Andy, I agree absolutely that you need dynamic service provisioning at different levels of the stack – the service you need to provision at the upper levels (eg a business service, or an application) is different from the lower levels (server, storage, network). But Im intrigued that you see a potential answer in V block – I am not really familiar with it but from reading the public material it looks like its firmly about infrastructure provisioning? I would suggest virtualisation at the application layer is more of a requirement?

  • Andy Mulholland andy mulholland says:

    Hi Guys – sorry about the last week of the CTO blog coming and going! Back to virtualisation – and more. Thats the point that made me interested, its really orchestration and abstraction that are the capabilities that we will b looking for to run the ‘services’ business layer over the technology layer, and that is a lot more than the simple virtualisaiton of hardware resources that we tend the term to mean today.
    So yes Mark in answer to your question if it were virtualisation in the currently accepted defintion of the term and use then i would nt see it as ‘the answer’! What i think V-Block is moving us towards is really orchestration and abstraction by extending the capabilities and way that virtualisation is used into a new dimension

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>