Skip the navigation

Q&A: New Red Hat CEO on JBoss, open source and the future

At the fifth annual JBoss user conference, James Whitehurst shares some of his vision and explains what it's like to switch from an airline to the open-source industry

By Todd R. Weiss
February 13, 2008 12:00 PM ET

Computerworld - ORLANDO -- Since being acquired by Linux vendor Red Hat Inc. in mid-2006, open-source middleware vendor JBoss Inc. has been a company in transition. It was well-known for its open-source middleware line that could be used by large businesses to better tie together their divergent applications.

Today, JBoss has come further by adopting some of its parent company's strategies, particularly by creating and marketing fee-based enterprise versions of its popular middleware in addition to still offering its free, community-based open-source software.

Red Hat CEO James Whitehurst
In an interview at the JBoss World Orlando 2008 conference, James Whitehurst, Red Hat's newly appointed CEO and president, talked with Computerworld about where the JBoss division has been and where it is going as part of Red Hat's overall strategy for customers. Whitehurst, 40, joined Red Hat last December after serving as chief operating officer and in other positions at Delta Air Lines Inc. since 2002. He also was a vice president and director of The Boston Consulting Group Inc.

How are things different for JBoss customers since the 2006 Red Hat acquisition? It's hard for me to know what external people expected from JBoss back then because I wasn't here at the time of the acquisition.

But as a company, we went back and fundamentally retooled the business model. JBoss up to the acquisition was the .org bits that they then sold to customers with support contracts. Now, as with our separate community-based Fedora and Red Hat Enterprise Linux editions of Linux, having JBoss offer both community-based open-source JBoss versions as well as JBoss Enterprise versions is a better model for our customers. If you're going to run something in production, you want to be sure it's going to run reliably.

Open source is innovative, but the bad news is that the code keeps changing quickly. Customers want to make sure it is going to work for a few years without major changes. It's a very different model than JBoss had before, but it's very robust.

My first thought was that having two versions was an artificial way to make money in open source. But it's not artificial at all. It's a controlled way of integrating open source for enterprises. JBoss went from selling technical services and support to selling a hardened business product.

And how has that worked so far for the parent company, Red Hat? The JBoss business is growing rapidly, and we believe it will continue to grow at twice the pace of our Red Hat Enterprise Linux business.

We have a huge opportunity to convert JBoss business users from the free community-based version to the paid version. I bet you'd be hard-pressed to find a Fortune 500 company that's not using JBoss today. The question is, are they paying for it? The enterprise version is much easier for them to use because it uses stable code that doesn't constantly change compared to the community-based version. It's about a flip of the switch today to change to the enterprise version. If you go with the enterprise version, it means what you add will still work effortlessly five years from now. Unless it's battle-hardened, it won't get used, and the communities won't get as big.



Our Commenting Policies