Comments on: Enumeration of PaaS container types http://stage.vambenepe.com/archives/1078 IT management in a changing IT world Tue, 09 Mar 2010 22:10:17 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: William Vambenepe — Is Business Process Execution the killer app for PaaS? http://stage.vambenepe.com/archives/1078#comment-102588 William Vambenepe — Is Business Process Execution the killer app for PaaS? Wed, 10 Feb 2010 09:26:41 +0000 http://stage.vambenepe.com/?p=1078#comment-102588 [...] execution engines are useful, as are other core services like storage (here is my proposed list of PaaS container types). I just wanted to bring some attention to business process execution because I think PaaS is the [...] [...] execution engines are useful, as are other core services like storage (here is my proposed list of PaaS container types). I just wanted to bring some attention to business process execution because I think PaaS is the [...]

]]> By: William Vambenepe — PaaS as the path to MDA? http://stage.vambenepe.com/archives/1078#comment-101056 William Vambenepe — PaaS as the path to MDA? Tue, 29 Dec 2009 07:42:23 +0000 http://stage.vambenepe.com/?p=1078#comment-101056 [...] the other hand, you are mapping to something that is higher level than byte code. Depending on what types of PaaS containers you envision, some of the abstractions provided by these containers (e.g. business process [...] [...] the other hand, you are mapping to something that is higher level than byte code. Depending on what types of PaaS containers you envision, some of the abstractions provided by these containers (e.g. business process [...]

]]> By: William Vambenepe http://stage.vambenepe.com/archives/1078#comment-99202 William Vambenepe Tue, 10 Nov 2009 19:59:30 +0000 http://stage.vambenepe.com/?p=1078#comment-99202 William Louth: both views are valid, it depends on what you're after. The first two bullets in my <a href="http://stage.vambenepe.com/archives/1096" rel="nofollow">follow up post</a> ("an application component model that supports deployment/configuration across all PaaS container types" and "explicit interactions/invocations between application components") address what you describe and I think they are indeed critical. But while "I don't care about the container, just do what my app needs" is great for the developer, from the POV of the people operating the PaaS framework they need to know exactly what sets of resources they need to provide and the minimal functional contract of each. I am trying to define a PaaS contract that is both useful to the app and manageable/doable for the provider. William Louth: both views are valid, it depends on what you’re after. The first two bullets in my follow up post (“an application component model that supports deployment/configuration across all PaaS container types” and “explicit interactions/invocations between application components”) address what you describe and I think they are indeed critical.

But while “I don’t care about the container, just do what my app needs” is great for the developer, from the POV of the people operating the PaaS framework they need to know exactly what sets of resources they need to provide and the minimal functional contract of each. I am trying to define a PaaS contract that is both useful to the app and manageable/doable for the provider.

]]> By: William Louth http://stage.vambenepe.com/archives/1078#comment-99189 William Louth Tue, 10 Nov 2009 12:59:41 +0000 http://stage.vambenepe.com/?p=1078#comment-99189 I am a little bit surprised that you took a rather implementation specific container perspective rather than something a little bit more abstract (in terms of deployment) like services/connectors/buses. I understand the need to partition & classify different workloads but does this need a particular container type itself? Would it not be better to have a single container-service contract that allows discovery (or injection) of internal or external cloud services such of wich might also acts as containers for particular work/activity migration (grid computation service)? I am a little bit surprised that you took a rather implementation specific container perspective rather than something a little bit more abstract (in terms of deployment) like services/connectors/buses. I understand the need to partition & classify different workloads but does this need a particular container type itself? Would it not be better to have a single container-service contract that allows discovery (or injection) of internal or external cloud services such of wich might also acts as containers for particular work/activity migration (grid computation service)?

]]> By: William Vambenepe — Desirable technical characteristics of PaaS http://stage.vambenepe.com/archives/1078#comment-99178 William Vambenepe — Desirable technical characteristics of PaaS Tue, 10 Nov 2009 10:14:01 +0000 http://stage.vambenepe.com/?p=1078#comment-99178 [...] technical characteristics of a given PaaS container, they are shared characteristics that go across all container types, no matter what the operational capabilities of the containers [...] [...] technical characteristics of a given PaaS container, they are shared characteristics that go across all container types, no matter what the operational capabilities of the containers [...]

]]>