Talk:Cloud computing: Difference between revisions
imported>Bruce M. Tindall m (New page: {{subpages}}) |
imported>Howard C. Berkowitz (→Concerned about scope and precision: new section) |
||
| Line 1: | Line 1: | ||
{{subpages}} | {{subpages}} | ||
== Concerned about scope and precision == | |||
To me, cloud computing is a form of distributed processing that emphasizes the computing resources, not the applications, beyond the technologies (e.g., intelligent DNS redirectors) that send transactions/sessions to resources. There is absolutely no non-buzzword reason to link SaaS, for example, with clouds. Clouds, grids, and other distributed infrastructures that are ''ad hoc'' or demand-driven are radically different than SaaS built for high availability. So far, when I've done SaaS architectures with any concept of a service level agreement, as in healthcare, the computing infrastruture is far more specific than a cloud, with extensive load distribution, fault tolerance, and capacity planning. | |||
I'd hate to see us drifting into one of the "Web 2.0" styles that makes everything so general that it provides no engineering guidance. [[User:Howard C. Berkowitz|Howard C. Berkowitz]] 19:11, 11 March 2009 (UTC) | |||
Revision as of 13:11, 11 March 2009
Concerned about scope and precision
To me, cloud computing is a form of distributed processing that emphasizes the computing resources, not the applications, beyond the technologies (e.g., intelligent DNS redirectors) that send transactions/sessions to resources. There is absolutely no non-buzzword reason to link SaaS, for example, with clouds. Clouds, grids, and other distributed infrastructures that are ad hoc or demand-driven are radically different than SaaS built for high availability. So far, when I've done SaaS architectures with any concept of a service level agreement, as in healthcare, the computing infrastruture is far more specific than a cloud, with extensive load distribution, fault tolerance, and capacity planning.
I'd hate to see us drifting into one of the "Web 2.0" styles that makes everything so general that it provides no engineering guidance. Howard C. Berkowitz 19:11, 11 March 2009 (UTC)