Archive for June, 2009

The layered model forever?

Monday, June 29th, 2009

By Stefan Wesner

The Service Oriented Knowledge Utility (SOKU) vision expressed in the 3rd version of the Next Generation Grid expert group report anticipated a future where the layered architecture model is replaced by an aggregation of “capabilities” to deliver a complex service. These “capabilities”, called Service Oriented Knowledge Utilities, are expected to be self-describing, discoverable, and provided by different providers. These “capabilities” can be combined and the capabilities mix can be changed as needed. The original text says: “The primary difference to earlier approaches is a switch from a prescribed layered view to a multi-dimensional mesh of concepts, applying the same mechanisms along each dimension across the traditional layers.“ See here for more on this. While the opinion that a layered model has to be considered harmful and is not the perfect solution is not new and the very strict ISO/OSI layered model is often implemented in a more relaxed fashion layered architectures are still dominating the solutions in Service Grids.

Nevertheless abstracting architectures of many Service Grid solutions can be summarized on a high level as shown in the figure below.

The Network is assumed to be only a transport mechanism, the Service Grid middleware layer is the focus of investigation and covers several components responsible for realizing some core function. They are combined to a set of services for realizing infrastructure services such as Service Discovery or packages to realize consumer or provider services such as SLA Management. All these service are combined to applications e.g. by the means of a workflow.

So what is wrong with this solution?

The layered model is trying to split the responsibilities quite strictly in order to allow the design and implementation of the different layers independent from each other. The communication is done via well defined APIs and allow a replacement of them. While this is beneficial from a viewpoint of design and implementation of functionality this leads to a duplication of functionality across the layers and lead consequently to more static solutions. The figure below shows how a non-layered approach could be realized to build a more complex service.

In this view a set of capabilities such as identity, transport, content, access to resources (e.g. computing, storage, …) is combined in a service mix by a virtual aggregated service provider to deliver a service to the consumer. The aggregation is realized with the help of a set of supporting services such as service discovery etc. During the collaboration between this provider and the consumer the service mix can be changed as needed such as new resource providers can be added, new transport mechanisms are added or exchanged and so on. So again what is the difference? Instead of having different identities on the different layers to get access to network, service etc you use a single identity for all “levels”. While the capabilities are of quite different nature (visualized by the different shapes on the left side and the different colors) they support in a similar way (unified shapes on the right side) the aggregation.

So why are layered models still dominating? In order to realize the solution presented above one need a complete virtualisation of services from the different levels, need standardized Aggregation APIs and need capabilities realized as building blocks expecting to be used across the “layers”. Research on this has just started as “Infrastructure as a Service” or clouds are mostly still limited to storage and computing. But without having other core services such as Network Infrastructure as a Service, Identity validation as a Service and so on this vision cannot be realized. A further problem is that while “Everything as a Service” would be there all these services must follow a standardized API and usage model. Activities on this have started in the Cloud Interoperability Forum (CCIF) but still limited to computing and storage resources.

So I think the layered model will not stay forever but for making the SOKU vision a reality enabling a dynamic service mix across the “layers” it will take a bit longer than 2010 as originally anticipated in the NGG3 report. Mostly as the virtualisation concept is still used in a too limited way and need to be extended to a broader context, the possibilities for making services really self-described must become more powerful and commercial virtualisation offers are using non compatible APIs and methods. I think the SOKU vision is still very valid even if has been invented ways before Clouds and Infrastructure as a Service had been there. Looking forward to dynamic world of non layered architectures…

Bookmark and Share

Cloud Computing – a bolt out the blue? Not quite, the writing was on the wall

Tuesday, June 16th, 2009

By Daniel Field

Many are of the impression that cloud computing is a new phenomenon, invented the other side of the pond and which came as a surprise to the traditional Grid technologies research community.

This is simply not true. Cloud computing is the rebranded, well marketed natural evolution of the ideas that were already being discussed and predicted by the grid community before the cloud entered the radar and took the industry by storm. And before you all jump in with discussions on the technical nuances between the two, let me make clear that I’m talking about the service offered to the end user, ie, the value proposition, and the business model behind the idea.

Whilst the torrent of media attention for all things cloud has undoubtedly cast a shadow over the traditional grid areas, the market analysis of many of these projects anticipated the coming of the cloud, albeit not in its current shape or form.

Grid computing traditionally concentrated on the high performance aspect of parallel computing, and the popular examples given were reams of computers slogging away number crunching financial derivatives or modeling the structures of proteins. However, by 2006 many of the business analysts were already pointing at other aspects of the Grid, such as trust and security, distributed programs running in diverse locations and advanced service level agreement components as enablers of new forms of business models, of collaboration within and between different companies and even of advanced virtual organizations capable of coming together to share resources for a limited time to achieve a specific goal. This is confirmed quite simply by looking at the pilot implementations of the BEinGRID project, many of which leverage these aspects to enable new services or business models.

Later, in early 2007, the analysts commented that the utility computing vision that inspired the original (electricity) Grid analogy back in the day, was starting to come to fruition. The inherent flexibility and decentralized nature of Grid was enabling what was starting to be labeled as Software-as-a-Service.

The CHALLENGERS workshop, dating to that time, concluded:

Grid infrastructure still promises to attract and enable new businesses and radically change the relationships between a customer and its supply chain offering a flexible platform for a global collaboration. Grids lead to competitive advantage through better utilization of heterogeneous, resources by converting them to virtualized services. As a result, such innovative Grid-enabled applications have become offered as “Software as a Service (SaaS)”. (Although this term has been around since at least 2000, it would appear to have met significant mainstream use[1] only around January 2007, see below). The initial success of [the] SaaS model appears based on the supply of the service to new customers: small and medium sized enterprises (SMEs) that could not otherwise have been served profitably.

Reading between the lines, the potential of virtualized resources offered to remote third parties, and of software ran remotely and provided on a pay per use model, was already recognized. Indeed, looking at early FP7 projects, such as SMART LM, (proposed in May 2006) we see an attempt by the community to evolve the world of software and services towards a more flexible approach that encompasses SaaS. (SmartLM handles the licenses as services and works with flexible models like extension, aggregation of licenses and introduces others that make prices become effectively independent of the underlying hardware).

Although, in contrast cloud computing does not exclusively claim a long-tail approach, it IS defined in terms of simplifying the provision for the end user and it seems that cloud has overtaken SaaS in the marketing terminology, an observation backed up the Google Trends image below and the current tendency to describe many of Google’s services as “in the cloud”. Perhaps then, it is fair to say that, if not the conclusion of this change, Cloud computing is at least the most notable manifestation at present of this change in focus of Grid.

So whilst cloud enjoys its lofty position at the peak of the Gartner hype cycle, let’s have a look at some of the reasons why that Cloud eclipsed its bigger brother.

Firstly cloud is defined in terms of user benefits, not what it is or how it works. Indeed, analysis I conducted in February 2009 showed that the first paragraphs of the Wikipedia pages for such terms as Grid computing, distributed computing, high performance computing, parallel computing and utility computing all defined the term in question in reference to the architecture or manner in which the computation is done. Cloud computing, on the other hand, defined itself in terms of delivering “scalable and often virtualized resources … as a service over the Internet. Users need not have knowledge of, expertise in, or control over the technology infrastructure “in the cloud” that supports them”.

Secondly, cloud computing as provided by Amazon was repackaged, rebranded, and extracted from the researchers who built it to be offered as a business service. Although the restricted beta of its first year of life was open only to researchers, it was clear from the outset that this was to be a professional and commercial service.

Thirdly, the cloud revolution was spear-headed by well known and trusted companies. Amazon itself is often credited with being one of the companies that inspired confidence in e-commerce. By being the pioneers of a new wave of commercial services, they instilled a customer confidence in cloud that would have been impossible for a start-up or a spin-off to generate. Additionally, having a mega-infrastructure, like Google and Yahoo! also, they were able to keep up with demand and grow at the market’s pace, not their rate of infrastructure acquisition.

And finally, cloud is so much more catchy than grid! Grid is an alright word, but admittedly somewhat utility. Like utility computing itself, it makes a good analogy to the electricity grid, sure, and a functional word suits a field that describes itself with a technical description, rather than what it does for its customers. But come to cloud, now that’s in a whole new stratosphere! There is an endless source of weather related metaphors and puns to whet the appetites of the wordsmithing marketers. And whilst I hasten to add that something as fickle as a name change is not generally sufficient to make a technology take off, one cannot deny that the marketing buzz that has been created around cloud is nothing short of electric.

So to conclude this post, and without raining on Amazon and co’s parade any further, I ask a final question: What will be the heir to the cloud? Who knows? Perhaps we will need some more blue sky thinking!

With thanks to Csilla Zsigri of The 41 Group for discussion and comments.

[1] Defined as having a search frequency in Google was high enough to register with Google Trends

Technorati Profile

Bookmark and Share