Subscribe: Comments on FAST and FAST Cache for the Service Provider
http://vmforsp.typepad.com/vm-for-service-providers/2011/11/fast-and-fast-cache-for-the-service-provider/comments/atom.xml
Preview: Comments on FAST and FAST Cache for the Service Provider

Comments on FAST and FAST Cache for the Service Provider





Updated: 2011-11-01T15:16:42Z

 



Chuck, I've definitely seen both of those offerings as well. The fundamental differences between selling individual tiers of disk, selling...

2011-11-01T19:33:35Z

Chuck, I've definitely seen both of those offerings as well. The fundamental differences between selling individual tiers of disk, selling...

Chuck, I've definitely seen both of those offerings as well. The fundamental differences between selling individual tiers of disk, selling "service levels" of auto-tiered disk and selling a FAST Cache-enabled offering are the speed at which the data ends up being demoted/promoted (hint: 24 hours isn't fast enough!) and how directly the service provider has to (wants to) tie the COST of the higher price tiers to the revenue generated. There's a fair bit of the financial side of the equation in the post coming (hopefully) later this week.




Hi Jeramiah I wanted to link this discussion to the revenue side of SPs for just a moment. SPs can...

2011-11-01T19:17:30Z

Hi Jeramiah I wanted to link this discussion to the revenue side of SPs for just a moment. SPs can...

Hi Jeramiah

I wanted to link this discussion to the revenue side of SPs for just a moment. SPs can differentiate their services around service level delivered. One of the big differentiators is, of course, performance -- and, as we both know, storage can have a lot to do with perceived performance.

So, I've seen this FAST Cache capability used in a couple of clever ways by SPs.

First, there's the "premium-ness" of the service: minimal I/O, moderate I/O, intense I/O. These I/O requirements may or may not be correlated with capacity, which is a different discussion. Behind the scenes, the SP dials up different FAST policies to get the "premium-ness" of the I/O service -- and charges for it.

Second, there's one guy offering "burst insurance" -- the ability to handle a 3x-10x spike in I/O traffic for 24 hours that wasn't planned for. Again, the SP charges a small premium for this, and again, it's dialing in a generous FAST policy. The SP bet here is that not everyone will need it at the exact same time.

Either way, I think the new technologies create new options for SPs to create differentiated services that customers will pay for.

-- Chuck




This is a very interesting post Jeramiah - definitely looking forward to the FAST VP post and specifically the comparison...

2012-02-26T08:24:54Z

This is a very interesting post Jeramiah - definitely looking forward to the FAST VP post and specifically the comparison...

This is a very interesting post Jeramiah - definitely looking forward to the FAST VP post and specifically the comparison / driver for going heavier on the FAST cache versus a EFD tier pool.


Thanks!