WSO2 launches platform built on OSGi spec
February 9, 2009 —
(Page 1 of 2)
Related Search Term(s): OSGi, SOA, WSO2
WSO2, an open-source SOA infrastructure software maker, released today a platform of integrated middleware components called Carbon. Each component in Carbon is built on the OSGi (Open Services Gateway Initiative) specification.
OSGi implements a component model for the Java Virtual Machine to make Java more modular, explained WSO2 CTO Paul Fremantle. WSO2 uses OSGi to integrate its middleware platform.
Carbon consists of the WSO2 Enterprise Service Bus (ESB) 2.0, WSO2 Registry 2.0 and WSO2 Web Services Application Server 3.0. The stack also includes the new WSO2 Business Process Server, which is based on Apache ODE (Orchestration Director Engine).
WSO2 is making "extremely rapid progress" in building out its SOA stack, said RedMonk principal analyst James Governor. He observed that WSO2's tooling in the information as a service space is a standout, and that the company is now trying to drive into process composition management.
With OSGi underpinning it, it's easier for developers to "grow with Carbon," Fremantle said. Developers can incrementally add components on top of services without having to reinstall the entire stack, similar to how the Eclipse foundation integrates plug-ins into its tooling, he explained.
Consistency and integration among components enables service composability in SOA, Fremantle said. Composability is the concept that collections of services can be assembled into composite services, and it is one of the guiding design principles of the SOA methodology.
WSO2 will be releasing several different component packs so that its customers can decide what component pattern they want to use for creating services, Fremantle said. Every Carbon component is managed through a single console.
In contrast, most SOA infrastructure software has a tendency to enforce architecture on the customer, Fremantle said. "Many developers moved to SOA to get away from central IT, but they are knocking on its door to get ESB help," he said. "That is the issue we are addressing with Carbon."
That lack of flexibility that Fremantle alleges stems from the nature of how many software makers assembled their respective SOA stacks.