{"id":136,"date":"2004-10-19T17:27:44","date_gmt":"2004-10-20T00:27:44","guid":{"rendered":"http:\/\/redmonk.com\/sogrady\/wp\/?p=136"},"modified":"2004-10-19T17:27:44","modified_gmt":"2004-10-20T00:27:44","slug":"enterprise-licensing-madness","status":"publish","type":"post","link":"https:\/\/redmonk.com\/sogrady\/2004\/10\/19\/enterprise-licensing-madness\/","title":{"rendered":"Enterprise Licensing Madness"},"content":{"rendered":"<p>So Microsoft today became one of the first vendors I&#8217;m aware of to openly and unambiguously state that its per processor licensing will stay that way, regardless of the number of cores the chip will run. Here&#8217;s what I told <a href=\"http:\/\/www.internetnews.com\">internetnews.com<\/a> on the topic (<a href=\"http:\/\/www.internetnews.com\/ent-news\/article.php\/3423971\">link<\/a>): <\/p>\n<blockquote><p>&#8220;From a software industry perspective this is an intelligent and aggressive move by Microsoft to try and seize the low ground in TCO conversations,&#8221; Stephen O&#8217;Grady, senior analyst at research firm RedMonk, told internetnews.com. &#8220;Many enterprise application vendors are struggling with the implications of multi-core architectures and its pricing implications. Microsoft&#8217;s unambiguous position here stands to benefit them at buy time and will pressure competing vendors to follow suit. Between this decision and Sun&#8217;s per-employee licensing options, customers stand to benefit from more predictable and manageable pricing.&#8221;<\/p><\/blockquote>\n<p>Now I haven&#8217;t talked to the folks from Redmond about this yet, but to me this is a great move for Microsoft. Pricing for enterprise applications over time developed into a quasi-actuarial science &#8211; and I should know, because in my former life as a systems integrator I had to try and build the potential pricing models on the front end of several engagements, and my math skills are marginal at best. <\/p>\n<p>The advent of multi-core architectures is poised to make the often absurdly complex pricing schemes even worse for some enterprises, and is the cause of some hand-wringing from CIOs and IT managers that I&#8217;ve spoken with recently. But Microsoft just closed the door on what some would perceive as an additional revenue opportunity in favor of simplicity and (likely) a happier customer. For the firm that gave us Licensing 6.0, that&#8217;s a step in the right direction. More importantly, this is likely to pressure some of its competitors to follow suit, or face substantial pushback from CIOs on the topic. <\/p>\n<p>So when it comes to today&#8217;s news, I&#8217;m in wholehearted agreement <a href=\"http:\/\/www.tbray.org\/ongoing\/When\/200x\/2004\/10\/19\/SWPricing\">with Tim Bray<\/a> that licensing today is far more complicated than it needs to be, and I&#8217;d go further and say that per processor licensing schemes are likely to be increasingly pressured by more intrinsic pricing models (i.e. Sun&#8217;s per employee model), open source competition, and the growing abilities of the processors themselves. About time, too.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>So Microsoft today became one of the first vendors I&#8217;m aware of to openly and unambiguously state that its per processor licensing will stay that way, regardless of the number of cores the chip will run. Here&#8217;s what I told internetnews.com on the topic (link): &#8220;From a software industry perspective this is an intelligent and<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","footnotes":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false},"categories":[42],"tags":[],"class_list":["post-136","post","type-post","status-publish","format-standard","hentry","category-in-the-headlines"],"jetpack_featured_media_url":"","jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/redmonk.com\/sogrady\/wp-json\/wp\/v2\/posts\/136","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/redmonk.com\/sogrady\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/redmonk.com\/sogrady\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/redmonk.com\/sogrady\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/redmonk.com\/sogrady\/wp-json\/wp\/v2\/comments?post=136"}],"version-history":[{"count":0,"href":"https:\/\/redmonk.com\/sogrady\/wp-json\/wp\/v2\/posts\/136\/revisions"}],"wp:attachment":[{"href":"https:\/\/redmonk.com\/sogrady\/wp-json\/wp\/v2\/media?parent=136"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/redmonk.com\/sogrady\/wp-json\/wp\/v2\/categories?post=136"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/redmonk.com\/sogrady\/wp-json\/wp\/v2\/tags?post=136"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}