In this video we take a look at a simple use case demonstrating how easily Apigee enables a transformation that can typically be a complex example in a Telco environment - A Telco XML/SOAP style backend (ParlayX) converted to the GSMA OneAPI. This enables carriers to create their own location or messaging APIs on top of an existing backend without having to go into the middleware layer meaning faster time to market for new services and avoids introducing instability in an operational network.
Daniel Jacobson of NPR posted a fascinating piece about how NPR tackles a common problem – what’s the best way to render content on a variety of devices, from modern web browsers with top-notch CSS implementations that look almost like typesetting (like Safari) to mobile phones using WAP to low-end devices like HD Radio receivers that don’t understand anything but plain ASCII text.
NPR’s clever solution is to strip markup out of the text and store it in a database table, indexed by position in the text document. To re-generate the content for a particular device, their software queries...
Last week, Scott Metzger of Truecredit.com gave a great case study presentation on how they opened their internal SOA as APIs for partners at the Burton Group Catalyst conference. Specifically, the different policy and governance patterns.
Scott talks about the factors driving them to identify and implement a separate application agnostic layer for 5 major policy patterns including service access, routing, caching, transformations, and operations. (And more details of their implementation in this video.)
(continuing our series on API roadmap considerations)
TrueCredit.com tells a story of calculating they would need thousands of IP addresses for all the different versions and flavors of their open API - to account for different variations and versions needed by partners.
Even if you have a ‘one sized fits all’ API - you might need to be able to transform data, mediate terms or customize SLAs without coding each change or a creating a new version of the API. Reasons could include:
• Protocol needs - A SaaS customer with a...