Comments on: Cloud catalog catalyst or cloud catalog cataclysm? http://stage.vambenepe.com/archives/889 William Vambenepe's stage Tue, 07 Feb 2012 23:33:47 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: William Vambenepe http://stage.vambenepe.com/archives/889#comment-591 William Vambenepe Tue, 28 Jul 2009 16:41:21 +0000 http://stage.vambenepe.com/?p=889#comment-591 William L, I agree, especially the part about the "programming model and component/service architecture". It's fine to have these catalogs of services, but if you don't know how they relate (and what rules apply to the composition) then you're out of luck. Similar to how in SOA the focus seems to have moved from reg/rep to a component model like SCA. William V. William L,

I agree, especially the part about the “programming model and component/service architecture”. It’s fine to have these catalogs of services, but if you don’t know how they relate (and what rules apply to the composition) then you’re out of luck. Similar to how in SOA the focus seems to have moved from reg/rep to a component model like SCA.

William V.

]]> By: William Louth http://stage.vambenepe.com/archives/889#comment-590 William Louth Tue, 28 Jul 2009 08:46:17 +0000 http://stage.vambenepe.com/?p=889#comment-590 Yes but those catalogs have always been used by educated/learned men rather than dynamically from some IT executing runtime which is were this all breaks down. Before we try to achieve this level of dynamism we should probably look to define & develop a suitable programming model and component/service architecture that reflects the nature of the cloud in terms of scalability and elasticity which will allow us to build blocks & layers on top of each other whilst ensuring such capabilities permeate up and down the stack and across service (cloud) interactions. We need to concentrate on building a good & maintainable marriage of scalability and elasticity revolving around resource management (metering, distribution, ....) and cost management (I assume there are limits to ones purse) at least to some degree. Yes but those catalogs have always been used by educated/learned men rather than dynamically from some IT executing runtime which is were this all breaks down.

Before we try to achieve this level of dynamism we should probably look to define & develop a suitable programming model and component/service architecture that reflects the nature of the cloud in terms of scalability and elasticity which will allow us to build blocks & layers on top of each other whilst ensuring such capabilities permeate up and down the stack and across service (cloud) interactions.

We need to concentrate on building a good & maintainable marriage of scalability and elasticity revolving around resource management (metering, distribution, ….) and cost management (I assume there are limits to ones purse) at least to some degree.

]]>