Blogs

Redmonk

Amazon: Perfect is the Enemy of Good

Amazon's Announcements

Incremental progress to declare victory is a phrase often heard in the technology industry, but far more rarely practiced. Too often we see vendors polishing their swords to slivers, having failed to learn the basic lesson that perfect is the enemy of good.

Not so the folks from Amazon Web Services. Besides their early identification of and commitment to the market for cloud based services, their building block approach to their web services business is one I believe many vendors could learn from.

Consider that when EC2 and S3 were launched, they were almost elemental building blocks which – while offering the elastic and pay-as-you-go benefits that have since come to characterize the cloud – required considerable investment in time and skills before they could be properly leveraged. Many vendors would have been horrified at the prospect of launching a product that could be characterized as unfinished; Amazon just made it available and set to improving it incrementally.

In the days since, we’ve seen the introduction of new services like DevPay of Flexible Payment Service as well as tweaks of the economic model (reserved instances), the persistence (elastic block store), the tooling (the Eclipse toolkit), the management (the management console), the service level reporting (service health dashboard), the platform capabilities (monitoring, auto-scaling and elastic load balancing) and most recently the data portability (AWS Import/Export).

None of which is to say that Amazon Web Services are perfect. Folks I know complain of the performance with file volumes numbering in the millions, the tooling story still has a long way to go to match Azure and Visual Studio’s ability to localize cloud development, and so on.

The point is that rather than get hung up on the existing shortfalls, Amazon is releasing early and often while working in the background to improve the service. My guess is that they’ll tackle the tooling and performance issues as they do everything else: incrementally.

Either way, it seems like Jeff Bezos’ “risky bet” is looking better by the day.

Disclosure: Amazon is not a RedMonk customer, but RedMonk is an Amazon customer.

Popularity: 4% [?]

by-nc-sa

How Long Until the Battle of the Enterprise Marketplaces?

As a long term believer in application marketplaces, it has been rewarding to see the success that offerings like the Apple iTunes store are having. A billion apps makes a convincing argument, and all that.

But I admit to still being absolutely mystified by the absence of marketplaces that incorporate, you know, actual developers. Clearly I’m talking about something distinct from the mobile app stores: if I need a developer to help me configure an application for my iPhone, whoever built it has already failed miserably. For enterprise software, on the other hand, this is the expectation rather than the exception. What’s the last piece of software you rolled out for your business that didn’t require some setup?

Exactly.

And yet while we have perfectly good models for marketplace one-time or recurring payments, buyer and seller ratings, elastic pricing and so on, enterprise software vendors have yet to perceive the massive potential that exists in marketplaces. Instead, they leave the task of finding, vetting and engaging qualified resources to the customer. For some, this is no doubt a shortsighted attempt to protect their own services divisions: by introducing or participating in an efficient marketplace around the after-purchase product experience, vendor service offerings would potentially be at risk. Think what vendors could do, though, simply by facilitating connections between their customers and the developers and third parties that work around these products. eBay for the enterprise undersells the concept, in my view.

Most bizarre is how many of the pieces some of the would-be marketplace providers already have, which are simply waiting on someone who can see the potential.

Consider Microsoft’s Web Platform Installer and Web Application Gallery, for instance. According to a release we were sent this week, the WPI has been downloaded 1.5 million times while users have downloaded 100,000 applications. Setting aside the delta between those numbers, which is admittedly curious, it’s difficult to argue that this initiative has been anything but successful. In spite of the fact that it does little to tackle the last mile of development and implementation: the connection of application users to qualified human resources.

Of the pieces the marketplace I envision would need, an Application Repository, Hardware, Identity Management system, Jobs Marketplace, and a Payment System, Microsoft’s already got one of the hardest to construct: the repository. Azure could be leveraged for the hardware, Geneva for identity, and they have to have some payments infrastructure sitting around somewhere, as long as they’ve been talking about it. Leaving jobs, which they could either build or buy relatively simply, I should think.

Not that Microsoft’s alone in its ability to target this opportunity, of course: there are half a dozen large vendors that could. Even Amazon, not an application vendor, has most of the requisite pieces.

Apple’s iTunes store has demonstrated quite convincingly that when you lower the barriers to application discovery and acquisition, volume is the inevitable result. Which is why it’s surprising that vendors looking to increase their volume sales aren’t doing everything in their power to reduce the friction of the same process with their enterprise wares.

Sooner or later, of course, someone will be the Apple of the enterprise market, and if they get it even half right they’ll be successful. Which in turn will inspire competition, just as iTunes led to the Blackberry Application Marketplace.

We’ll have a battle of the marketplaces, in other words. The only question is when, and who’s going to be first and who’s going to be second.

Who knows? Maybe it’ll be Sun.

Disclosure: Microsoft and Sun are RedMonk customers, while Amazon and Apple are not.

Popularity: 4% [?]

by-nc-sa

In the Cloud, No One Fights House to House

In their efforts to establish context, many of the journalists and vendors we speak with begin by comparing the cloud to ancestral technologies like grid or utility compute offerings. Many, if not most, believe that is representative of the possible upside for the cloud and cloud based offerings.

Certainly those of this mind set may yet be proven correct, irrational exuberance being a historically common failing in this industry. But for my money, such analogies undersell – dramatically – the cloud’s horizontal appeal.

Shortly after Network.com launched in 2006, I had the opportunity to speak with a few of the folks from Sun about the offering. Their first question to me was both expected and straightforward: “Have you signed up for Network.com yet?” My answer was just as simple: “No. Why would I?”

And indeed, why would I? With all due respect to Sun’s ability get to market early, Network.com had little to offer an individual technologist. Because it was focused on batch operations that could be easily outsourced rather than general workloads, its applicability to my needs was questionable. This belief was further validated in the specialized nature of the customers of the service I spoke with: oil and gas exploration, fluid hydrodynamics research, digital animation rendering and so on. The typical customer case study from Network.com was as impressive as it was exceptional. Sun’s Grid was an early, impressive achievement, but one targeted to as narrow an audience, in my view, as its E10K machines – but without the similar margins.

Sun was hardly alone in its lack of delivery here, of course. If anything, the soon-to-be-Oracle-acquisition was ahead of the curve: when a major platform services market is pioneered by an online retailer, it’s safe to say that the vendors missed a trick. Microsoft’s Ray Ozzie admitted as much to Om Malik, saying in March of last year that the market “really isn’t being taken seriously right now by anybody except Amazon. They’ve done the world a service by putting out there some fairly provocative, interesting services.”

Why are their services interesting? Their appeal. Unlike the grid and utility efforts that preceded them, the cloud was more horizontally applicable, and – if anything – is becoming more so every day. Grid computing is demonstrably useful to the Exxons and Pixars of the world while cloud services like storage are potentially relevant to everyone from a Fortune 50 to your neighbor backing up his music collection. That alone differentiates cloud from other important technical trends such as SOA. Like operating systems, the cloud can play in consumer and enterprise with near equal facility, making it a rare beast indeed.

The implications for provider and vendors are, of course, varied, but if you combine the appeal with the low barriers to entry, what you have is what I’ve been telling customers: an opportunity not to fight house to house. Most enterprise markets are supersaturated, with customer acquisition and retention a costly chore thanks to the overhead of the requisite sales, marketing and support staffs. The cloud alone is no panacea for that condition, of course, for at certain purchasing levels it will be forced to jump through the same hoops as every other enterprise technology offering.

Like open source, however, the cloud can – by virtue of its applicability and accessibility – flow into the enterprise basement like flood waters. Rather than fight it out house to house, sales call by sales call, the opportunity exists to have an offering that sells itself. And better, from a vendor perspective, may be difficult to decommit from, if only because of the pains of migrating significant volumes of data.

But to get there, you have to do what Amazon did: take the market seriously.

Disclosure: Microsoft and Sun are RedMonk customers, while Amazon is not.

Popularity: 3% [?]

by-nc-sa

The Open Database Alliance and the Future of MySQL

Stated more simply: as long as MySQL remains committed to the dual licensing model, it will be unable to accept the same patch set that open source only versions of the code can, because they do not share the same licensing concerns. Which is why we’ve seen these spring up.” – MySQL: Now and Then

Given that I wrote the above back in December, I obviously could not have known that the Open Database Alliance would launch this week. But if by some miracle you’d had a vision of the future and relayed it to me, I confess that I would not have been terribly surprised.

The simplistic analysis is that the Open Database Alliance is strictly a reaction to the Oracle acquisition of Sun, and by extension, MySQL, which has introduced uncertainty into that ecosystem. The truth, however, is that the consortium, or something very much like it, was inevitable given the increasing delta between the versions of MySQL being shipped by MySQL and those being distributed by third parties with no dual license interests to protect.

To recap, for those of you unfamiliar with the intricasies of the dual licensing practice, here’s a quick description. In dual licensing,

…a single entity such as MySQL is responsible for the overwhelming majority of all development on a given codebase. Anything they don’t produce themselves, they license. Very often this is practiced in conjunction with the dual-license model; because MySQL is responsible for virtually all of the development of the core code, they own or have licensed appropriately all of the involved IP. As such, they’re free to issue commercial licenses to those who would cannot or choose not to comply with the terms of the open source license – the GPL, in this case.

Sounds too good to be true, open source alongside proprietary licenses (and revenues)? Looking for the catch?

In part, it’s that the burden of development is born almost entirely by the MySQL staff, but the more relevant concern here is the inability to consume external contributions – even if they’re excellent – without licensing them.

Unlike, notably, Monty Program AB and Percona, which can consume whatever patches they deem acceptable because without the need to adhere to a dual licensing model, they are free from its restrictions.

What’s happening here, then, is this: the MySQL forks that have been propagating through the community for sometime – not to mention competing with the parent distribution – are beginning to coalesce and become a more centralized alternative.

The near term market impacts should be minimal: just as the MySQL organization spent years building its enterprise credibility, so too must those that would compete with it, technical superiority or no. The longer term implications, however, are far less clear. Already we’re seeing substantial community interest in the innovations to the codebase occurring externally, and this week’s news could potentially accelerate enterprise interest in the forked codebases by coordinating development to a greater degree.

If nothing else, then, we live in interesting times.

Thanks to Lisa Sheeran of Sheeran/Jager Communication, I was able to put a few questions to Monty Widenius via email, so herewith the rare Q&A that’s with someone other than myself.

SOG: While it will have an obvious technical advantage in its ability to consume patches and fixes that MySQL itself cannot, how does the Open Database Alliance anticipate competing with the enterprise heft of Sun in the short term and Oracle in the long term? Or does the Alliance anticipate pursuing a different customer segment?
Monty: Our aim is to make MariaDB the main and most used open source database. If we succeed, then the user and customers will come to us, the Open Database Alliance, for their MariaDB and MySQL business.

We plan to grow the same way that MySQL initially grew — by working closely with the community and the MariaDB users. This means that Monty Program Ab’s first customers are heavy database users who need changes done in the server code to be able to satisfy their business needs.

Sun/Oracle will be better equipped to handle big companies that are used to deal with companies of the same size. The Alliance is targeting customers that need more personalized services than Sun/Oracle provides.

SOG: What storage engines, besides Maria, will be supported, if any?
Monty: We aim to support by default all open source storage engines. In our current tree we already have PBXT. Within a couple of weeks we will also have XtraDB and FederatedX. We are talking with some other storage engine vendors to include their engines too.

SOG: What restrictions are imposed on the business by the ownership of the MySQL trademark by Sun, and potentially Oracle?
Monty: The main restriction is that we can’t call our branch of MySQL “MySQL”. Instead we have chosen to call it MariaDB, after my youngest daughter.

SOG: How many full-time development resources are available to the Alliance, both for development and support?
Monty: The Alliance is growing by the day, so this is an increasing number.

Percona is about 20 people.
Monty Program Ab will be around 15 by end of May.
Openquery is about 3 persons.

From how things looks now, I would not be surprised if we have more than 10 companies in the alliance by the end of the month.

SOG: Are there any Open Database Alliance customers available for comment?
Monty: Each of the current Alliance members have a lot of customers. I can of course only speak for Monty Program AB; We are talking with several
really big, well known companies regarding server work so things looks good!

Disclosure: MySQL and Sun are RedMonk customers, while Oracle and the Open Database Alliance are not.

Popularity: 4% [?]

by-nc-sa

My Backup: Dropbox, JungleDisk, S3, and a Desperate Need for Deduping

When it comes to backing up my music, I have four problems. Apart from the backup, I mean.

  1. My music acquisition is done on a Linux laptop (both Amazon and the eMusic store provide Linux clients)
  2. My Linux laptop’s harddrive is only 128 GB, much of which is devoted to virtual images, ergo space for music is tight
  3. My primary music library is housed on a Mac (so as to be portable to my iPhone)
  4. My music library (~80 GB) is too large to be entirely synced with Dropbox (50 GB max)

In other words, I currently download to one machine – an Ubuntu equipped X301 – which has only enough space to contain a subset of the master library. As for the master library, it’s attached to a Mac Mini running OS X, which in turn needs to be regularly updated with the newly acquired tracks from the Ubuntu machine.

Got all that?

Besides migrating newly acquired content to the master library, one of the requirements of my backup process is to push the content to the cloud. As I noted in 2007, my music may just be my most valuable material possession, and it’s certainly the least replaceable, so having an offsite copy is critical to me. Just as it will be to a horde of consumers in the years ahead, but that’s a different matter entirely.

So here’s my solution, warts and all – and yes, I’ll get to those.

Tools

  • Paid Dropbox account: $99/year
  • Paid Amazon S3 account: $0.150/GB storage | $0.100/GB transfer
  • JungleDisk client: have a lifetime account, which appears to be no longer available
  • Dropbox client
  • Rsync

Process

  • [Ubuntu laptop] Download music from Amazon/eMusic/etc into ~/Music

  • [Ubuntu laptop] ~/Music is symlinked to my Dropbox directory (instructions here), meaning everything downloaded is pushed to the cloud and to my other Dropbox equipped machines, including the Mac Mini
  • [Mac Mini] Dropbox directory is synced to the master music library on an external drive using the following process. All credit for the process – scripts included – goes to to Chris Tirpak. Anything wrong, particularly with the rsync options, is purely my stupidity:
    1. Create a backup rsync script. Mine is as follows:

      #!/bin/bash
      #
      # backup the home directory to copper
      #
      SUBJECT="Daily Backup Log"
      EMAIL="sogrady@gmail.com"
      BACKUPLOGFILE="/Users/sog/bin/backupMac.log"

      #remove the old log file in case it is still there
      rm $BACKUPLOGFILE

      echo "Begin backup at: " > $BACKUPLOGFILE
      date >> $BACKUPLOGFILE

      rsync -rltvz /Users/sog/Dropbox/Music/ --exclude "Amazon MP3" /Volumes/"NO NAME"/"MUSICDIR"/ \
      >> $BACKUPLOGFILE 2>&1

      rsync -rltvz /Users/sog/Dropbox/Music/"Amazon MP3"/ /Volumes/"NO NAME"/"MUSICDIR"/ \
      >> $BACKUPLOGFILE 2>&1

      echo "End backup at: " >> $BACKUPLOGFILE
      date >> $BACKUPLOGFILE

      # send the log in an email using /bin/mail
      /usr/bin/mail -s "$SUBJECT" "$EMAIL" < $BACKUPLOGFILE

      rm $BACKUPLOGFILE

    2. Copy this file to ~/bin
    3. Tell the script to run every night to sync the directories by inserting getting launchd to execute a plist entry. Here's my plist script:
    4. Put the plist file in ~/Library/LaunchAgents
    5. In a terminal: launchctl unload net.ogrady.backupMacSilent.plist
    6. In a terminal: launchctl load net.ogrady.backupMacSilent.plist
    7. In a terminal: launchctl list | grep -i net.ogrady
  • With the master directory thus updated with any newly downloaded tracks, JungleDisk then reflects the master directory up to S3 for permanent backup nightly.

The good news about the above: it will dutifully run rsync nightly to grab the target Dropbox directories and copy them over to the master directory. The bad news? It creates duplicate files. Lots of duplicates. My master music directory - both from this process and from previous backup efforts - has a massive duplication problem, probably on the order of several thousand duplicate files.

Which brings me to the question: anyone got an outstanding de-duplication procedure that will let me preview the files to be removed? Because I need some serious help.

Otherwise, what would you improve, and where? What's your backup routine look like?

Popularity: 4% [?]

by-nc-sa

Blogging is Dead! Long Live Blogging!

I am not proud of the fact that some of my e-mail goes unanswered as a result. It is never my intention to be rude or to give well-meaning readers the cold shoulder. If I were a commercial best-seller, I would have enough money to hire a staff to look after my correspondence. As it is, my books are bought by enough people to provide me with a sort of middle-class lifestyle, but not enough to hire employees, and so I am faced with a stark choice between being a bad correspondent and being a good novelist. I am trying to be a good novelist, and hoping that people will forgive me for being a bad correspondent.” – Neal Stephenson, Bad Correspondent

If only I could get away with that.

The fundamental problem Stephenson is referring to, as Linda Stone would presumably confirm, is time. Whatever the productivity system employed – from FIFO to Getting Things Done – the single, immutable fact is that replying to correspondence takes time. And time, as Emerson in turn would almost certainly confirm, is that most precious of commodities: unlike money, once spent, it can never be recaptured.

Time is on my mind for a number of reasons these days, not least because of the whispers I keep hearing that “blogging” is “dead.” The world’s moved on, it’s said, and blogging and the protocol(s) that enable it are the dinosaurs to Twitter et al’s mammals. Implied in such statements, of course, is that blogs are being done in by time, or more accurately, the lack thereof. Blogging aggregators/readers have not been spared, and are being taken out to the woodshed by the very people that write the software.

So is it true? Are Twitter and its 140 character counterparts making the previously vibrant blogging ecosystem anoxic by consuming its oxygen equivalent more efficiently?

Sorry, I’m not buying it. Maybe I should: I consume fewer blogs than I once did, due in part to the siren call of Twitter. And I suppose it could be something of a conflict of interest to protest claims of a particular mediums death…on that medium.

Still, like a bad B movie villain, the long form, as Tim refers to it, just refuses to die. And why should it? The simple, inescapable truth is that certain conversations require more space – more time – than others. I can tell you where I’m having lunch in 140 characters. I might even be able to give you a decent review of the venue. But I cannot break down the intricasies of a large Oracle/Sun merger/acquisition in a Twitter-sized chunk; for that I need a few several thousand words.

What we’re moving towards, I think, is a more balanced vision of information consumption, in which a full spectrum of content from War and Peace to SMS will be recognized as valid forms of expression, each with respective strengths and weaknesses. Just as blogging was a reaction, in many respects, to the publishing trends that preceded it, so too was Twitter an evolution of blogging; hence the “microblogging” description. Twitter has pushed the boundaries of the short form, and in so doing, proven a market.

What it has not done is obviated the need for the forms that preceded it.

Each of us must establish our own balance with respect to our information consumption; the Stephenson’s of the world will ignore email in service of a larger goal, while us mortals will assemble our own systems for managing our input driven in part by how we’d like to consume but mostly by how we have to. None of these systems will be perfect, of course, because there is simply too much information. Efficiencies and coping strategies can only do so much; as some of us move to newer mediums in search of lower volume – say from email to Facebook – in time the newer medium will come to resemble the old, and then we’ll be off for greener pastures.

None of this, however, is likely to be zero sum. Twitter might impact the time I spent reading and writing blogs, but it certainly doesn’t absorb all of it. Because at the end of the day, it’s just a different tool for a different job, and quite often, that job is pointing to someone’s blog.

Tim said this last week:

Here’s one thing I’m sure of: there is no danger of all human discourse converging on the short, medium, or long form.

I agree. In a world in which disruption is the rule and the clock is always ticking, short, medium and long forms will persist, if only because they must. The market sizes for each will vary, depending on the time we’re collectively able and willing to invest, but I’m certain there will be markets for each.

Even blogging.

Popularity: 4% [?]

by-nc-sa

links for 2009-05-06

Popularity: 4% [?]

by-nc-sa

The Tuesday Grab Bag: RedMonk HQ, Google Voice and More

RedMonk HQ

Remember when I told you that in spite of some pending lease work, “barring any unforeseen issues, RedMonk is once more a Maine based organization?” Well, we had some unforeseen issues; in this case, a hideous and truly unsignable lease. So, we exited, and there was no more Old Port for RedMonk. That’s the bad news. The good news is that a couple of weeks later, I’ve resettled in what is going to be an even better home for the firm eight or nine blocks from the former office. As you might be able to tell from the picture, the building is a former temple, converted some years back into office space. Just across the street from the Old Port neighborhood I occupied briefly, we’re just as conveniently situated as we were before. More, if you’re visiting and need to park.

So there’s your miscellaneous RedMonk update for the day. And now, your grab bag of items that may deserve their own entries but aren’t getting them.

FriendFeed

I’ve had a FriendFeed account for a long time now, but to be honest, I haven’t really done much with it besides the initial configuration. When I need the kind of aggregation FriendFeed provides, I tend to hit Blizzard’s whoisi instead. It’s not that I don’t see the appeal, it’s just that FriendFeed hasn’t yet clicked for me. That said, I do find it interesting that subscriptions to my FriendFeed – which can be found here – have upticked dramatically in the past few weeks. I’ve gone from the odd few requests every other week to a constant stream of connections per day.

Is anyone else seeing something similar?

Gmail Interface

Much has been made in some quarters of the new, revamped mobile interface for Gmail offered to Android and iPhone users, and not without cause. Leveraging HTML5 and Gears, it includes some basic offline support, the ability to deal with flaky mobile connections and a cleaner interface.

Unfortunately, like all new software releases, it has some issues. In my usage, they’ve ranged from inconvenient to legitimately troubling bugs. As an example of the former, my personal Gmail account will often insist that it cannot connect to the network while my work account – also Gmail – has no issues whatsoever. As for the latter, a few days after the release I attempted to reply to an email thread with a few of my friends about where we were going for lunch the next day. Henceforth, every time that I reconnected to Gmail, it would resend that same message; my friends got seven or eight emails saying “Sapporo +1″ before I went in, deleted the databases (Settings: Safari: Databases: delete GmailMobileWeb) and fixed the problem.

The point is not to lambaste Google for bugs: they happen. Instead, I think it’s worth pointing out that with volumes of new interfaces being pushed out to devices with radically different form factors, we’re likely to see a lot of such weirdness in the months ahead.

Google Voice

While I remain a bit perplexed that it took Google as much time as it did – a year and a half or so – to spin Grand Central into Google Voice, it’s true that the my experience with the telephony moving pieces is less than some other areas we could talk about. Meaning that I’ll cut them some slack on the timing, if only because they’ve delivered on the features front. The SMS notification is great, as it allows me to use my Grand Central number as a real replacement for the mobile, which in turn allows me to limit the number of people that have my cell. This is good. The call transcripts, while occasionally a bit jagged, are enormously beneficial as they pick off calls from agencies and spammers alike: it’s much quicker to read a transcript than it is to listen to a voicemail. At least for me.

The sole missing feature for me that would make the service transformative would be the ability to point our toll-free number at it. I’m currently trying to do that with a For Pay third party service, but with little luck thus far. PhoneFusion insists on picking off calls before they get to Google Voice, while Toktumi won’t let me complete the sign up process (though their support has been helpful thus far).

If they added that ability, Google would effectively be our telephony provider going forward, with Skype playing an important supporting role.

Popularity: 4% [?]

by-sa

Clouds over the Ivory Tower

It being McKinsey, you can assume the math is correct. For once, though, I think the numbers fail to tell the story. Though whether that’s their fault or McKinsey’s is open to question. But I’m getting ahead of myself.

For those that missed it, the folks over the Uptime Institute engaged the celebrated management consultancy in a project to look at cloud computing. After examining the technology and the economics, McKinsey produced a presentation entitled “Clearing the air on cloud computing” that concluded that while cloud computing has undeniable benefits, “many of the claims being made about cloud computing have lead some to the point of ‘irrational exuberance’ and unrealistic expectations.” In Uptime’s words, anyway. The New York Times was a bit more blunt, saying “But while cloud computing is a marketing triumph, new research from McKinsey & Company asserts that trying to adopt the cloud model would be a money-losing mistake for most large corporations.” Further, they quote the study’s author, Will Forrest, as follows: “The industry has assumed the financial benefits of cloud computing and, in our view, that’s a faulty assumption.”

Now it’s true that saying that the technology industry is fickle is something of an understatement, obsessed as we all are with the shiny new thing. And with the task of marketing software a difficult task in the best of times, and these being very far from the best of times, it’s as unsurprising as it is predictable that the term cloud computing is being thrown around like it was, say, SOA. So the conclusion that cloud computing is just the latest marketing fad might seem logical. Inevitable, even.

But like Tim, I think that belies the real inevitability, which is the heavy adoption of cloud offerings.

The fact that the economics, apples to apples, are not a landslide win for the cloud would not be – or should not be, anyway – a surprise to many. For $69 a month, you can get a server from 1and1 that’s almost twice as fast (2.2 Ghz vs 1.2 Ghz) with twice as much physical memory (2×160 GB v 160 GB) as the default Amazon EC2 instance, which would run you approximately $74/mo. McKinsey’s delta between the loaded total cost of a CPU managed by a datacenter and EC2 are even more damning; the former beats the latter $150 to $366, for a 144% delta. Ugly.

Or it would be, if it were apples to apples. But it’s not.

Tim’s primary criticism of the McKinsey piece is that economics are not the sole predictor of success within the technology space.

I can remember like yesterday sometime in the Eighties, the CIO of my parent company, a telecom-equipment manufacturer, lecturing executives about how we simply could not realistically think about meeting information-worker demand for PCs, and I’m pretty sure one of her slides (a real slide, on a real projector—you had to allow a week’s lead-time to prepare them) had more or less exactly McKinsey’s points. She lost, because the information workers simply routed around her.

Getting Stuff Done · At the end of the day, that’s all that matters. When a new technology arrives, if it’s basically affordable and it lets you do your job faster and better, well, it just doesn’t matter if it’s a little more expensive or a little less secure or any of those other things. It’s going to happen.

Precisely. McKinsey’s numbers, in my opinion, are being handed down from an Ivory Tower. Similar to studies that “prove” how much more productive, maintainable or secure Java is to PHP, it ignores the most important feature of cloud computing: a low barrier to entry.

While having lunch in New York a few months back, I had the opportunity to talk about EC2 with some of the developers from a large media organization. They referred to it as “infrastructure that you can buy as books.” With budgetary limitations, their ability to procure more hardware had been severely curtailed. Working at a meda company, their ability to purchase books had not. And while such infrastructure-as-books anecdotes are flip, they are simultaneously anything but. The fact is that whatever the theoretical economics might be for any given environment, the practical market looks considerably different.

Having fought, as a systems integrator, through the procurement, hardening and deployment processes for new hardware for projects, I am highly skeptical that McKinsey’s math – while undoubtedly quite accurate – will trump the convenience of infrastructure on demand. As open source demonstrates quite convincingly, availability and convenience are powerful incentives indeed.

But more than glossing over ease of adoption as a fundamental driver of adoption, I’m perplexed by the implicit assumptions that cloud computing is a zero sum game. Slide 24, for example, assumes the “migration of total Windows and non-console Linux capacity for entire data center,” and slide 25 discusses the “total infrastructure labor base saving potential if moving whole data center to cloud” – they project it at 10-15%, in case you’re curious.

Who would contemplate the migration of their entire datacenter investments to the cloud? Forget the economics: unless the cloud offerings were effectively free – which McKinsey has convincingly proven they are not – the risks of migration would far outweigh the potential economic returns. In a world where US tax returns are being processed by COBOL programs written in the 60’s, I find the notion of wholesale migration – one of the assumptions for portions of the presentation – exceedingly problematic. It’s akin to questioning the economics of converting the entirety of one’s application portfolio to Visual Basic because that language is easy to learn.

Far more likely than an abrupt private datacenter to cloud shift is an adoption pattern similar to what we see today; James is exactly right, in my view, when he says that Amazon is the new VMware. In other words, we can expect pilot projects to be followed by discrete, tactical employment of the technology, bridging in time to strategic but complementary usage. And the economics of that complementary consumption – particularly in the speed of availability and time to market, and later, the impacts on pricing – would change considerably.

In 1980, McKinsey was asked by AT&T to predict the cellphone market in 2000 and was off by a factor of 120. I don’t know that they’re off at all in their numbers here (though their lack of attention to the economic advantages in deployment speed is troubling), but neither am I remotely convinced that they’ll be determinative.

Should enterprises embrace virtualization and “datacenter best practices” as McKinsey recommends? Absolutely. But those that would fight the rising tide of cloud adoption are likely to fare no better than Cnut.

Update: While I was willing to give McKinsey the benefit of the doubt on their numbers, Vinnie Mirchandani wasn’t. Interesting read.

Popularity: 4% [?]

by-sa

The Thursday Grab Bag: Backtype, MLB’s iPhone App and More

just as awesome as you think

For a variety of reasons, not least the best efforts of Oracle and Sun to sink my week, the planned commentary on McKinsey’s interesting Cloud Presentation isn’t quite ready yet. Look for that tomorrow, instead. But lest I leave you bereft of my prattle, let’s go back to the well and do the rare Thursday grab bag.

If you’re new around here, the grab bag is for items that may or may not deserve their own entries, but aren’t getting them. Without further delay…

BackType

First alerted to this Y Combinator backed effort by my colleague, I have to admit that I was skeptical that BackType could deliver on its promise: pulling the FriendFeed and Twitter discussions of your content back into the entry itself. But really, it couldn’t have been simpler. Unlike some of the other plugins I’ve used in this space, no template modifications were required: it Just Works. Drop it into WordPress, activate and enable it, and you’re done.

You can see it in action on the Oracle/Sun piece from this week, which as I write this had 17 Twitter comments and one FriendFeed mention.

Highly recommended piece of software.

Jaunty Jackalope

With the latest iteration of the Ubuntu hitting the streets this week, I made the jump last week, and I must say – Jeff’s accurate criticism of the login screen notwithstanding – Jaunty is excellent. Everything on my Thinkpad X301 works perfectly out of the box, with the exception of the AT&T WWAN which will power up but not connect to the network (my scripts still work, luckily). Suspend works flawlessly, power management works like a charm, the wifi card is supported natively, the compiz effects are applied with an eye towards usability, and the overall experience in general is just…easy. And the oft maligned notifications? I’m a fan.

Jaunty still does not come close, in my opinion, to matching the polish and eye candy of OS X, but it’s getting closer each iteration. I’ll contrast it with Windows 7 which I have installed on VirtualBox later, but for now, it’s a really nice distribution offering an excellent user experience.

MLB.com iPhone Application

Everyone I know who owns this is aware of this already, but for the iPhone owning baseball fans out there that remain unaware: MLB’s 2009 application is, quite possibly, the greatest piece of software ever written. Not that the UI is all that improved from last year’s version; apart from a few tweaks here and there, it’s pretty much the same. Nor is it more stable: if anything, it’s even more crash prone than it was before. No, the Holy Grail feature that this year’s version offers – which makes the ~$10 purchase price an absolute steal – is the gameday audio. Finally, after all these years, you can get streaming audio of both the home and away radio feeds for any game playing. And for those, like yours truly, that have been burned by MLB’s idiotic blackout rules in the past after purchasing offerings like MLB.tv, not to worry. The application’s gameday audio is blackout free, so that when I leave my car to go grocery shopping, I need not leave the game behind. You literally have the audio anywhere you have a signal, and not just 3G or wifi: it works just fine over EDGE.

This is easily the best iPhone application I’ve ever bought and the best $10 I’ve spent since I bought my lawyer our first round. Can’t recommend it highly enough for the baseball fans in the audience. I would buy an iPhone just for this application. Being able to listen to the ballgame whether I’m home in Maine or away in San Francisco? That really is priceless.

The Office Update

Remember when I told you a few weeks back that I secured an office in the Old Port, “pending” some “lease work?” Yeah, so that didn’t work out, as the lease I was provided was completely unacceptable for too many reasons to list. So no more office in the old port: that’s the bad news. The good news is that I’ve actually found an office just on the other side of the Franklin Arterial – a few blocks away, for unfortunates not intimately familiar with the geography of America’s Most Livable City – that’s actually superior in nearly every aspect. Thus RedMonk is still in Portland, just not quite where I’d originally expected us to be. Az and I should be settling in there next week, so if you happen to be in the neighborhood, do drop by.

Popularity: 4% [?]

by-sa
Close
E-mail It