For any utility, profitability hinges on using your capital assets – your installed capacity – as efficiently as possible, and the way you do that is through sophisticated pricing schedules. In essence, you want to reward those customers whose usage patterns allow you to use your installed capacity efficiently (by cutting their prices) while penalizing those customers whose usage patterns undermine your ability to use your installed capacity efficiently (by raising their prices). If you do this effectively, you get the best possible return on every dollar of capital you invest in infrastructure and, as you grow, you get more profitable. If you do it poorly, you become less profitable as you grow and, ultimately, you croak.<\/p>\n
By all accounts, Amazon Web Services’ path-breaking computing utilities, particularly its S3 storage utility, are fabulously popular. But they don’t yet seem to be profitable, and as Amazon CEO Jeff Bezos recently disclosed<\/a>, they are now capacity-constrained. In other words, to continue to grow Amazon is having to expand its installed capacity through investments in data centers, drives, processors, bandwidth, and other plant and equipment. In order to become profitable as it makes those capital investments, it has to begin to more aggressively shape the way its services are used by customers. It can no longer treat all customers as equals.<\/p>\n In this light, Amazon’s original flat-rate pricing for its utility services, while having the advantage of simplicity, becomes unsustainable. Electric utilities, to take an earlier example, started off with flat-rate pricing, but they only became hugely successful when they began to customize their pricing schedules to the usage patterns of individual customers. So it’s no surprise that Amazon has announced<\/a> that it will abandon its flat-rate pricing schedule for S3 on June 1 and introduce a more complex pricing schedule with tiered fees for bandwidth usage and a new fee for the number of requests made on the system. (Storage fees themselves will remain fixed – for the time being.) Amazon puts a customer-friendly spin<\/a> on the change:<\/p>\n With Amazon S3 recently celebrating its one year birthday, we took an in-depth look at how developers were using the service, and explored whether there were opportunities to further lower costs for our customers. The primary area our customers had asked us to investigate was whether we could charge less for bandwidth.<\/p>\n There are two primary costs associated with uploading and downloading files: the cost of the bandwidth itself, and the fixed cost of processing a request. Consistent with our cost-following pricing philosophy, we determined that the best solution for our customers, overall, is to equitably charge for the resources being used – and therefore disaggregate request costs from bandwidth costs.<\/p>\n Making this change will allow us to offer lower bandwidth rates for all of our customers. In addition, we’re implementing volume pricing for bandwidth, so that as our customers’ businesses grow and help us achieve further economies of scale, they benefit by receiving even lower bandwidth rates. Finally, this means that we will be introducing a small request-based charge for each time a request is made to the service.<\/p>\n The end result is an overall price reduction for the vast majority of our customers. If this new pricing had been applied to customers’ March 2007 usage, 75% of customers would have seen their bill decrease, while an additional 11% would have seen an increase of less than 10%. Only 14% of customers would have experienced an increase of greater than 10%.<\/p><\/blockquote>\n That’s all well and good, but the real reason for the pricing change is to shift usage patterns to Amazon’s benefit. It’s true, though, that ultimately the shift in usage patterns will generate broad benefits to customers, because the more efficiently Amazon uses its installed capacity, the lower it will be able to push its prices. (When a utility is in its early growth phase, it makes more money by cutting prices than by raising them – if it’s well managed.)<\/p>\n In the immediate term, though, some users, particularly those using S3 to store large quantities of fairly large files, will make out well, while other users, particularly those using the service as a web server for lots of small files, will get a whack to the wallet. You can see the contrast by reading, on the one hand, the response<\/a> of SmugMug CEO Don MacAskill (a beneficiary) and, on the other, the posts<\/a> on Amazon Web Services’ developer site from users who will suffer.<\/p>\n The big picture is simple: Amazon’s success in utility computing is forcing it to become more sophisticated as a utility operator and that inevitably means drawing distinctions between users and reflecting those distinctions in variable pricing. S3 may only be a year old, but it’s already growing up.<\/p>\n","protected":false},"excerpt":{"rendered":" For any utility, profitability hinges on using your capital assets – your installed capacity – as efficiently as possible, and the way you do that is through sophisticated pricing schedules. In essence, you want to reward those customers whose usage patterns allow you to use your installed capacity efficiently (by cutting their prices) while penalizing […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[1],"tags":[],"class_list":["post-788","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/posts\/788","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=788"}],"version-history":[{"count":0,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/posts\/788\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.roughtype.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=788"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=788"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=788"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n