Cloud Computing: The Nine Features of an Ideal PaaS Cloud
Popularity Report
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
URL Tag Cloud
Bookmark History
Saved by 1 people (0 private), first by anonymouse user on 2008-07-22
- Marbux on 2008-07-22 - Tags cloud computing , interop , platform as a service , PAAS
Public Sticky notes
What sort of cloud computer(s) should we be building or expecting from vendors? Are there issues of lock-in that should concern customers of either SaaS clouds or PaaS clouds? I’ve been thinking about this problem as the CEO of a PaaS cloud computing company for some time. Clouds should be open. They shouldn’t be proprietary. More broadly, I believe no vendor currently does everything that’s required to serve customers well.
What’s required for such a cloud? I think an ideal PaaS cloud would have the following nine features:
What’s required for such a cloud? I think an ideal PaaS cloud would have the following nine features:
Highlighted by marbux
1. Virtualization Layer Network Stability
Highlighted by marbux
2. API for Creation, Deletion, Cloning of Instances
Highlighted by marbux
3. Application Layer Interoperability
Highlighted by marbux
4. State Layer Interoperability
Highlighted by marbux
5. Application Services (e.g. email infrastructure, payments infrastructure)
Highlighted by marbux
6. Automatic Scale (deploy and forget about it)
Highlighted by marbux
7. Hardware Load Balancing
Highlighted by marbux
8. Storage as a Service
Highlighted by marbux
9. “Root”, If Required
Highlighted by marbux


Public Comment