Comments on: Monday’s Musings: Lessons Learned From Amazon’s Cloud Outage http://blog.softwareinsider.org/2011/04/25/mondays-musings-lessons-learned-from-amazons-cloud-outage/ Your buy side advocate for enterprise apps strategies, vendor selection, & contract negotiations Tue, 22 May 2012 17:35:47 +0000 hourly 1 http://wordpress.org/?v=3.1.3 By: R "Ray" Wang http://blog.softwareinsider.org/2011/04/25/mondays-musings-lessons-learned-from-amazons-cloud-outage/comment-page-1/#comment-12078 R "Ray" Wang Thu, 28 Apr 2011 06:31:16 +0000 http://blog.softwareinsider.org/?p=7575#comment-12078 Doug - great points here. we need to get to more meaningful metrics. what do other people think? - Ray Doug – great points here. we need to get to more meaningful metrics. what do other people think? – Ray

]]> By: Doug Hadden http://blog.softwareinsider.org/2011/04/25/mondays-musings-lessons-learned-from-amazons-cloud-outage/comment-page-1/#comment-12062 Doug Hadden Wed, 27 Apr 2011 16:14:12 +0000 http://blog.softwareinsider.org/?p=7575#comment-12062 <b>Cloud SLAs</b> One of the disconnects between service providers and users is the SLA meter. Cloud providers can meet SLAs for uptime (especially not including scheduled maintenance), bandwidth, "average response time" and availability. Yet, the the page-to-page response time to the user may not meet expectations. That's because response time might be based on pinging tests or averaging pages with no database call with those that do. <i>potential action item</i>:collect a set of meaningful to users SLAs prior to negotiation. <b>TCO of usability vs. uptime</b> One of the attractions of many cloud providers has been more intuitive usability. Those considering cloud services may discover that traditional on-premises systems introduces cognitive latency as users hunt for hard-to-remember functions, navigate through too many pages, and demand internal IT support. <i>potential action item</i>: analysis by analyst group to create usability benchmark to uptime conversion Cloud SLAs
One of the disconnects between service providers and users is the SLA meter. Cloud providers can meet SLAs for uptime (especially not including scheduled maintenance), bandwidth, “average response time” and availability. Yet, the the page-to-page response time to the user may not meet expectations. That’s because response time might be based on pinging tests or averaging pages with no database call with those that do.

potential action item:collect a set of meaningful to users SLAs prior to negotiation.

TCO of usability vs. uptime
One of the attractions of many cloud providers has been more intuitive usability. Those considering cloud services may discover that traditional on-premises systems introduces cognitive latency as users hunt for hard-to-remember functions, navigate through too many pages, and demand internal IT support.

potential action item: analysis by analyst group to create usability benchmark to uptime conversion

]]> By: Performance Architecture for Cloud « A Passion for Research http://blog.softwareinsider.org/2011/04/25/mondays-musings-lessons-learned-from-amazons-cloud-outage/comment-page-1/#comment-12023 Performance Architecture for Cloud « A Passion for Research Tue, 26 Apr 2011 06:08:02 +0000 http://blog.softwareinsider.org/?p=7575#comment-12023 [...] media on the AWS outage, the following are the three best I’ve seen.  Ray Wang’s post, Monday’s Musings: Lessons Learned From Amazon’s Cloud Outage is excellent along with George Reese’s thorough and excellent blog post  AWS Outage: The [...] [...] media on the AWS outage, the following are the three best I’ve seen.  Ray Wang’s post, Monday’s Musings: Lessons Learned From Amazon’s Cloud Outage is excellent along with George Reese’s thorough and excellent blog post  AWS Outage: The [...]

]]>