A new service from SOA Software aims to help developers ‘close the gap’ for enterprises using APIs to manage workflow processes in business. Speaking with ProgrammableWeb at the recent API World, key business leaders of SOA Software shared details of their new API Gateway and explained what it will mean for in-house enterprise developers responsible for creating mobile applications.
“We have added API orchestration to our mobile application gateway which allows large enterprises to expose mobile applications as APIs”, said Sachin Agarwal, VP of Product Marketing with SOA Software.
SOA Software’s press release published to coincide with their API World presence explains:
“The new API Orchestration capability accelerates time to market to digital channels by helping businesses publish simple and elegant APIs to their business partners and developers. APIs are products, and need to be packaged in a simple yet a productive offering. This calls for delegating some of the aggregation and business process orchestration logic that has to be executed based on the context of the digital channel, to what SOA Software calls API Orchestration. API Orchestration relieves API developers from calling multiple APIs or even multiple operations on the same API. Having a simple API is key to drive API adoption and extend presence across digital channels.”
SOA Software’s CTO, Alistair Farquharson, explained to ProgrammableWeb why there is a need for this specific service:
“A lot of our customers were looking at API Management as a proxy for basic routing, but then when they were needing to link to the backend they needed a lot of specific code. One of the trends we are seeing is that enterprises are using APIs and on the client-side, this is becoming very complex. What orchestration does is that it takes the complexity out of the client-side as a mobile device doesn’t necessarily have the processing power to manage all of these processes built on the specific, complex code, and we are pushing these processes to the gateway.”
Farquharson gives the example of a blurring between processes and policies. On-the-fly developers within an enterprise may be using authentication as a process that is handled whenever an enterprise API is called. This creates additional complexity and slows down the API request call each time.
“Policies need to be taken out of an orchestration”, Farquharson asserts. “Authentication is a declarative, non-functional policy, our platform separates out process and policy.”
“We have lowered the bar for API development”, Farquharson said, referring to the new service’s offer of code resources to reduce the amount of technical coding developers will need to do. As a result, the new API orchestration tools allow developers to move from writing code to structuring processes. “We are seeing the developer role changing to be more of a technical business person,” Farquharson said.