View profile

ARCHITECHT Daily: Cloudera's IPO will be an eye-opener on open source

Cloudera officially filed its S-1 report on Friday, in preparation for an IPO later this year. You ca
ARCHITECHT Daily: Cloudera's IPO will be an eye-opener on open source
By ARCHITECHT • Issue #51 • View online
Cloudera officially filed its S-1 report on Friday, in preparation for an IPO later this year. You can get a high-level overview of its filing and the IPO market in various places. Here are the financial highlights, from a CNBC story
  • What they’re hoping to raise: up to $200 million
  • Revenue: $261.0 million in the year ending Jan. 31, up from $166.0 million a year ago
  • Net loss: $187.32 million, narrower than the $203.14 million from a year ago
Of course, if you’re really interested in the economics of big data, and Cloudera specifically, you should just read (or skim) the whole thing.
Cloudera’s S-1 lists a goldmine of open-source-related issues—some more worrisome than others—including the pace/continuation of open source development, licensing issues, and potential problems with the Apache Software Foundation. But I think the biggest thing to watch over the next couple of years will be broader than just Cloudera. Namely, it will be the effect of more publicly available financial data—especially from a high-profile company like Cloudera—on open source business models, whether or not companies are selling Hadoop. 
Red Hat aside, many open source companies still struggle with questions like finding the right balance between open and proprietary, balancing licensing revenue against support revenue, and balancing internal R&D investment with community investment. More evidence of what’s working and what’s not could be very useful for open source companies and investors alike.
And although this will ultimately matter across software sectors (and although Cloudera lately cites IBM as its primary competitor), the biggest immediate impact will likely be on Cloudera’s legacy Hadoop-based peers MapR and Hortonworks. I’ll ignore MapR for the time being because it’s still a private company with private financials, and I really don’t know what they look like. Hortonworks, however, has always taken a more traditional support-and-services approach to open source than either Cloudera or MapR. 
And it has experienced, shall we say, a roller-coaster ride since going public a couple years ago—in part because of that pure open-source product strategy. To its credit, Hortonworks isn’t oblivious, and has been doing some interesting things around IoT (with its DataFlow offering) and cloud computing (with its Data Cloud for AWS offering) that could help out. The company briefed me on them last week, and perhaps I’ll write up a little more on this shortly. 
I made a little chart (below) that’s simple in terms of metrics, but that highlights a very important distinction: While revenue is growing nicely at both companies, Cloudera’s net loss was smaller and shrunk during its last fiscal year. Hortonworks’ net loss was larger and grew during its last fiscal year. If I’m a Hortonworks executive or shareholder, I’m looking at that and thinking of ways to narrow the gap.
Basically, though, we’re in a period where open source is the norm for enterprise software (especially at the infrastructure level) and where SaaS and cloud services are catching on very quickly. Sunlight might be the best disinfectant, but it’s also good for illumination. As more open source and cloud-based companies go public (hello, Dropbox, in a bit!), we’re all going to learn a lot about the economics of modern enterprise software companies—the good, the bad and the ugly.

If you enjoy the newsletter, please help spread the word via Twitter, or however else you see fit.
If you’re interested in sponsoring, please drop me a line.
Use Feedly? Get ARCHITECHT via RSS here:
What's new on ARCHITECHT
Pivotal CEO Rob Mee on the success of Cloud Foundry and learning to sell enterprise software
Artificial intelligence
Cloud and infrastructure
Despite all the innovation in data centers over the past several years—from server designs to building designs to where they’re located—there’s still a lot of work to do. And while websites and cloud services have a global reach, the effects of the data centers that power them are often felt locally. Here are three recent stories that highlight why web/cloud infrastructure is still an unsolved problem:
All things data
These are two good posts on the relative importance of data visualization, which is simultaneously useful, hard to do right, and of indeterminate importance to companies. I would suggest it’s most important for companies (e.g., news outlets) serving consumers with, essentially, one-shot charts. For many BI use cases, a dashboard and a few good standard charts probably can do the trick.
Listen to the Architecht Show podcast
Did you enjoy this issue?

ARCHITECHT delivers the most interesting news and information about the business impacts of cloud computing, artificial intelligence, and other trends reshaping enterprise IT. Curated by Derrick Harris.

Check out the Architecht site at

If you don't want these updates anymore, please unsubscribe here
If you were forwarded this newsletter and you like it, you can subscribe here
Powered by Revue