Comments on: Desirable technical characteristics of PaaS

By: William Vambenepe — The battle of the Cloud Frameworks: Application Servers redux?

Thu, 22 Apr 2010 17:37:06 +0000

[...] Cloud Frameworks will need to go through the equivalent of all the other stages. First, the IaaS APIs will get more optimized and capable (stage 2). Then, at stage 3, we will focus on higher-level, more productive abstraction layers (generally referred to as PaaS) at which point we should expect a thousand different approaches to bloom, and several of them to survive. I will not hazard a guess as to what stage 4 will look like (here is my guess for stage 3, in two parts). [...]

By: William Vambenepe

William Vambenepe — Tue, 10 Nov 2009 20:00:48 +0000

William Louth: you’re right, metering+billing should also be there. Oversight on my part. I like the way AWS has been thinking out of the box about different ways to charge users, including ways that map directly to the consumed resources.

By: William Vambenepe — Enumeration of PaaS container types

William Vambenepe — Enumeration of PaaS container types — Tue, 10 Nov 2009 17:02:45 +0000

[...] next post will list desired characteristics of the PaaS environment (meta-capabilities that go across all the [...]

By: William Louth

William Louth — Tue, 10 Nov 2009 13:12:58 +0000

You seem to be ignoring billing and resource metering (note: metering != billing) which is required by one or more services in support of the “cloud” like qualities hinted at including scalability, reliability and work migration. The container needs to expose runtime resource meters. The cloud services interactions need to expose metering usage. All in a uniform way and correlated with component activity work flows – with flows having multiple cost (chargeback) structures supporting billing/metering from multiple perspectives both operational & non-operational.