Platform as a Service (PaaS) and complexity

When discussing the emerging complexity topic, we assume that initiatives will have to manage “platform<>component” relationships.  In other words, we will have to lead the construction/upgrade of a platform and lead the construction of components that plug into the platform.

Platform as a Service (PaaS) turns this assumption on its head.  Larry Dignan posts on an interview with Bill Appleton, CTO of DreamFactory (here).  Appleton looks at cloud platforms less as technical toolboxes and more as distribution channels:

There are a lot of differences in what they do, but there are also different audiences. We look at four main issues: How viral is the platform? How open is the platform for new users and building new apps? What’s the pricing model? And what is the anchor tenant of the platform. What will bring people there?” says Appleton.

These factors imply that instead of having one platform<>many application; it will be multiple platforms<>one application.  That implication is explicit in Appleton’s mind:

A company that solely makes “cloudware,” DreamFactory’s term of choice, has to be available on multiple clouds. “We look to publish the application widely,” says Appleton.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: