03. stycznia 2010 08:02:00
A few weeks ago I completed a series of posts describing the ways that cloud computing will change the way we utilize virtual machines and operating systems. The very heart and soul of software systems design is being challenged by the decoupling of infrastructure architectures from the software architectures that run on them.
(Credit: Flickr/Ross Berteig)
Over the last few weeks, I've been slowly trying to get a grip on what the state of the union is with respect to software "packaging" architectures in cloud computing environments. Specifically, I've been focusing on infrastructure-as-a-service (IaaS) and platform-as-a-service (PaaS) offerings, and the enabling infrastructure that will handle application deployment to these services in the future. How will they evolve to make deployment and operations as simple as possible?
My search started innocently enough. After writing the "big rethink" series, I formed a theory that there are really only two interface points that IaaS and PaaS services needed to standardize:
The management interfaces that enable a wide variety of tools to monitor and manipulate the resources and services being offered
The "unit of delivery" that includes the software to be hosted and any required supporting data, configuration, and policy required to allow that software to work.