RedHat's new FuseSource acquisition dovetails existing JBoss efforts

Home

News: RedHat's new FuseSource acquisition dovetails existing JBoss efforts

  1. Yesterday, amidst the hoopla at the combined Red Hat Summit and JBoss World event in Boston, RedHat quietly announced that they have sealed the deal on the acquisition of FuseSource. The negotiations have been moving along quietly for some time, possibly since late April when Progress Software, the parent company that's selling FuseSource, announced that they would be divesting ten non-core product lines, or maybe even earlier. Still, in the wake of that announcement, FuseSource was able to carry on and held a highly successful CamelOne conference in mid-May. But that must not have been enough to keep the company off the selling block.

    Sources close to FuseSource show initial excitement about the transition. FuseSource evangelists Rob Davies and James Strachan, contacted at the JBoss World event in Boston on June 27, expressed initial excitement about the move. Both reserved serious comment for a later time, but Strachan was willing to say that the deal was, in a word, "Awesome." He feels that the ideology of both organizations "dovetail nicely." While Davies started a blog yesterday by explaining that "it is really fantastic that Red Hat [has] announced they are acquiring FuseSource!"

    Robin Howlett, a senior architect at Silver Chalice, one of the many fine speakers at the aforementioned CamelOne event, said that RedHat and FuseSource should make "a great match" and that "joining the first billion-dollar open source company, and one with such a strong and trusted brand, can only mean a promising future for [FuseSource's] comprehensive, open source integration solutions. I'm interested in seeing what they produce."

    RedHat's vice president and general manager of middleware, Craig Muzilla, was unable to confirm the possibility of the acquisition when interviewed yesterday, moments before the acquisition was made public. But he did say that RedHat is always looking to expand their middleware capabilities and he stressed RedHat's existing involvement with Apache projects like Camel and Active MQ.

    Reporters for SearchSOA.com were able to catch up with Muzilla after the announcement was made public, at which time he said:

    “We are accelerating our integration platform side of the business … [w]hat FuseSource has is some very complementary technology.”

    […]

     “They have the leaders, the originators in Camel... [we]  were doing Camel already. They also bring expertise in messaging with ActiveMQ. This helps us. The architecture fits well. The team fits well.”

    For more from that article, check out this link on RedHat acquiring FuseSource.

    As always, we here at TheServerSide are very interested to hear what you, the Camel and Apache users, think about this news. Is this going to push FuseSource middleware products further faster? Is there worry that RedHat's larger corporate identity will interfere with the FuseSource team's ability to contribute to Apache projects as they're used to? What are the factors that matter to you?

     

  2. Congratulations to the Camel team. I'm using it in my current project and I can say it saved me much headache and time.

    Hopefully this means cleaner architecture, more integration with JavaEE spec, more lightweight and standard based component implementation, less Spring dependency and more tooling.