Your browser is not supported. Please update it.

27 September 2012

In the aftermath of WAC, the race is on for common API management

The high profile Wholesale Applications Community (WAC) may have failed to deliver its grand promises of a common developer platform spanning the world’s main cellcos, and leveraging the advantages inherent in their networks, but the vision lives on. Grand plans rarely work out for carriers with their multitude of agendas and competitive conflicts, but WAC did succeed in sharpening focus on the move for operators to open their network APIs (application programming interfaces) to partners. Now there is a new battle, to fill the WAC vacuum and create a harmonized platform for managing these APIs.

The WAC effort itself has been folded into the GSM Association’s own effort in this area, OneAPI, although the actual technology has been acquired by Apigee, a specialist in systems to publish and manage APIs. Apigee will deliver a unified network API service for operators, which will be provided by the GSMA to its membership. It also promises to continue to evolve a cross-platform mobile development platform, as envisaged by WAC when it was established in February 2010, as an extension of the Joint Innovation Lab project of Vodafone, Verizon Wireless, China Mobile and Softbank.

As well as the WAC move, Apigee recently announced a self-service API management system free of charge, enabling any application developer to make 3.5m API calls per month (about one a second). An app completes an API call whenever it performs a function or pings the network. Apigee also offers a premium service starting at $9,000 per month.

According to the company, which raised $20m in funding last month, almost 20 one-fifth of the top 100 Fortune companies, including Walgreens and Netflix, use Apigee, making more than 100bn API calls per month. It acts as the gateway between them and the operators’ networks.

Given the GSMA support, Apigee might seem to be a done deal in terms of delivering a de facto standard for API management. But despite its broad membership, the GSMA has not always succeeded in outdoing commercial bighitters, and there are plenty of firms eager to provide that bridge between apps provider and cellco. The addressable space is growing as operators get more confident about opening up their networks, and as more large software partners turn to a third party rather than an inhouse solution.

But that will see competition rising too, and with it, the danger of fragmentation, always the ironic demon which haunts initiatives to create harmony among different mobile and software platforms ‘ though the situation cannot be much worse than it is now, with many carriers having three or four API management systems in use. And eventually, the goal is an overall framework in which individual systems can all work.

That will take years and many political compromises to achieve though, and in the meantime, the vendors are jostling for position. Alcatel-Lucent, already highly active in the API space, recently upped its game by open sourcing its API management platform under the brand apiGrove. There are plenty of other contenders too ‘ Ericsson and Huawei, like ALU, have seen the opportunities of providing unified software platforms to enhance their role in their cellco customers’ value chains, as those operators shift their focus to ‘telco 2.0’ and web applications. Enterprise software suppliers like IBM, Oracle and Aepona play too, aiming to push their offerings into the carrier space, and there are specialists like Apigee itself, APISpark and at least a dozen others. Most focus on API management functions such as metering and security, but many are adding in business analytics.

ALU will hope to raise its profile as well as tapping into a broad base of innovation with its open source move. Like Apigee, apiGrove aims to help cellcos and enterprises to expose their network and cloud infrastructure APIs more easily to developers, with the aim of creating a critical mass of support, making its offering a de facto platform for API exposure management. Any firm can download the apiGrove software and start exposing their APIs to developers. Users can then contribute code back to the project, and companies like Citrix are already doing this, forming the basis of an API community. That can be a two-way process ‘ ALU hopes it can then get apiGrove embedded into Citrix’s open source cloud platform, CloudStack (as an example), so that any carrier using that system for cloud infrastructure will automatically have access to apiGrove.

As well as the open efforts, which aim to give ALU significant industry influence and customer profile, it is also launching API efforts which generate revenue more directly ‘ in particular, a set of professional consulting offerings in this area. It recently opened a new division to add sharper API focus to the application enablement strategy it first described in 2009, providing professional services as well as a methodology for opening APIs faster and more easily.

Laura Merling, SVP of application enablement at the vendor, told LightReading that many operator API initiatives have failed because existing platforms are too complex, and the carriers have lacked a clear go-to-market strategy, or a process to streamline the creation, deployment and management of their network-based services. Her group aims to help customers create a platform-as-a-service for internal development as well as for third party partners. “Ultimately revenue is one way they’ll measure success, but it’s like number six on a list of seven. It’s not the top thing. The top thing is delivering services more quickly,’ she said.