Software development in the new age: IONA's aggressive embrace of open source
Before service oriented architecture (SOA), distributed computing battles were often waged between Microsoft's DCOM (Distributed Component Object Model) supporters and vendor-neutral CORBA (Common Object Request Broker Architecture) proponents. While these technologies don't generate much press these days, they continue to run many critical systems, particularly in large enterprises.
IONA's strategy is based on two initiatives. First, back in June 2005, IONA announced it was sponsoring the development of Celtix, an open source ESB written in the Java programming language. The first functional release of Celtix code is expected at the end of this year. Second, IONA announced this week it was working within the Eclipse Foundation, an open source community that is best know for creating an extensible framework for software development tools, on a new project dedicated to service creation in SOAs. This proposal, called the SOA Tools Platform (STP), is Eclipse's ninth top-level project. It is designed to create an extensible framework for SOA-related activities like service and service policy creation and configuration. The goal is to have a functional framework available by mid-2006.
What is the risk for IONA? With Celtix, the risk is cannibalization of the company's Artix product line. Both are positioned as ESBs, and some users may find that Celtix is all they need and forego the licensing cost involved with Artix deployments. On the tooling front, IONA plans to use the Eclipse STP tools as its primary software for Artix development, replacing its own tools. If the Eclipse project falters, IONA will be forced to continue to invest in two tool efforts.
What about the rewards? With Celtix, IONA realizes that an open source ESB solution will undoubtedly emerge at some point, so its proactive Celtix efforts will enable the company to be closely aligned with the potential open source ESB leader. In addition, no-cost (for software licenses) Celtix implementations may jump-start the SOA/ESB market, eventually leading Celtix and other entry-level ESB users to invest in the more robust Artix line. There is also an opportunity to generate service revenue off Celtix implementations.
As for the STP, IONA's goal is to leverage Eclipse and its developer resources to improve the tools that will be fundamental for the success of Celtix and Artix. The vendor also believes that the STP software will entice some portion of tool users to invest in either Celtix or Artix solutions.
Finally, taken together, these efforts offer IONA the potentially large payback of refurbishing the company's image and mindshare from being the leading CORBA provider to being a leader in SOA solutions.
IONA's success will depend on whether its Celtix and STP projects are successful and its relationship with the open source community. For example, will Celtix deliver a useable ESB, and will that free offering gain traction? As for STP, while Eclipse strategic members have pledged their support and other vendors have endorsed it at launch, will the project be as successful over the long haul as other Eclipse efforts have been?
As for its relationship with the open source community, the key is how much code and resources IONA contributes and how much it allows its offspring like Celtix to blossom despite the threat of cannibalizing its own products. And successful interaction is not about pleasing individual coders, as open source contributors are often now working for large companies like IBM. To generate buzz, inspire contributions, and drive adoption of Celtix and STP, IONA must not only be seen as an energetic and responsible member of the community but also one that can help other vendors and user companies drive profits or reduce costs.
IONA's situation is similar to Novell's. Once giants in their respective market segments, their actions rippled through the IT industry. Now both have hitched their futures to not just accepting but embracing open source. Other established software companies and startups will have to face the fact that most useful horizontal technology products will spur open source versions. Fear of open source, its licenses, and a new business model will only hold back software vendors.
IONA redefines its image
IONA Technologies, with headquarters in Waltham, Mass., and Dublin, made its name selling and supporting CORBA solutions with its Orbix offering. Now, the company is attempting to leverage its considerable distributing computing expertise and experience by selling SOA-tailored solutions, such as its Artix enterprise service bus (ESB). And as it embraces SOA, the company is also embracing the open source development model and community. But unlike some vendors that are hedging their bets or hoping to skim from global open source resources without committing too deeply, IONA is aggressively integrating standards and open source into its products and services, accepting the risks to reap the rewards.IONA's strategy is based on two initiatives. First, back in June 2005, IONA announced it was sponsoring the development of Celtix, an open source ESB written in the Java programming language. The first functional release of Celtix code is expected at the end of this year. Second, IONA announced this week it was working within the Eclipse Foundation, an open source community that is best know for creating an extensible framework for software development tools, on a new project dedicated to service creation in SOAs. This proposal, called the SOA Tools Platform (STP), is Eclipse's ninth top-level project. It is designed to create an extensible framework for SOA-related activities like service and service policy creation and configuration. The goal is to have a functional framework available by mid-2006.
What is the risk for IONA? With Celtix, the risk is cannibalization of the company's Artix product line. Both are positioned as ESBs, and some users may find that Celtix is all they need and forego the licensing cost involved with Artix deployments. On the tooling front, IONA plans to use the Eclipse STP tools as its primary software for Artix development, replacing its own tools. If the Eclipse project falters, IONA will be forced to continue to invest in two tool efforts.
What about the rewards? With Celtix, IONA realizes that an open source ESB solution will undoubtedly emerge at some point, so its proactive Celtix efforts will enable the company to be closely aligned with the potential open source ESB leader. In addition, no-cost (for software licenses) Celtix implementations may jump-start the SOA/ESB market, eventually leading Celtix and other entry-level ESB users to invest in the more robust Artix line. There is also an opportunity to generate service revenue off Celtix implementations.
As for the STP, IONA's goal is to leverage Eclipse and its developer resources to improve the tools that will be fundamental for the success of Celtix and Artix. The vendor also believes that the STP software will entice some portion of tool users to invest in either Celtix or Artix solutions.
Finally, taken together, these efforts offer IONA the potentially large payback of refurbishing the company's image and mindshare from being the leading CORBA provider to being a leader in SOA solutions.
Working correctly with open source can pay
Embracing open source will be key for many software vendors to thrive in the future. IBM is a massive supporter of Linux and other open source technologies (even while it continues to pitch proprietary solutions), and this is helping its service organization stay relevant and busy. Apple Computer has also experienced success working with and giving back to the open source community. Others like Computer Associates, which have only dipped their toes in the waters, have yet to see much of a return. On the other end of the spectrum, Microsoft remains the most influential software supplier with an antagonistic relationship with open source, and its constant struggles with open source have weakened its long-term position.IONA's success will depend on whether its Celtix and STP projects are successful and its relationship with the open source community. For example, will Celtix deliver a useable ESB, and will that free offering gain traction? As for STP, while Eclipse strategic members have pledged their support and other vendors have endorsed it at launch, will the project be as successful over the long haul as other Eclipse efforts have been?
As for its relationship with the open source community, the key is how much code and resources IONA contributes and how much it allows its offspring like Celtix to blossom despite the threat of cannibalizing its own products. And successful interaction is not about pleasing individual coders, as open source contributors are often now working for large companies like IBM. To generate buzz, inspire contributions, and drive adoption of Celtix and STP, IONA must not only be seen as an energetic and responsible member of the community but also one that can help other vendors and user companies drive profits or reduce costs.
IONA's situation is similar to Novell's. Once giants in their respective market segments, their actions rippled through the IT industry. Now both have hitched their futures to not just accepting but embracing open source. Other established software companies and startups will have to face the fact that most useful horizontal technology products will spur open source versions. Fear of open source, its licenses, and a new business model will only hold back software vendors.