We just don’t talk enough about the intersection of APIs and mobile middleware, but they really are a match made in heaven. APIs are the prevailing interface model, mobile middleware provides the Enterprise grade security and scalability, and HTML5 keeps mobile fragmentation costs at bay. It all came together last week at IDF 2013. Here is a picture of the demo pod rocking a full end-to-end demo with Expressway API Manager.
The use case was a conference room booking demo which helps large Enterprises (like Intel) optimize the use of physical space for meetings and collaboration. Expressway provided the governance, mediation and security layer by taking XML and JSON room sensor data and optimizing it for mobile devices through caching and compression. Further, rather than worry too much about sensitive information leaking to the phone from back-end systems.
Expressway redacts potentially sensitive personally identifiable information (PII) and checks API response data against a data loss protection policy at the egress (API) point. On top of this it scales to thousands of half-duplex (HTTP) or full-duplex (Websocket) clients, all with a simple drag and drop policy and an API discoverable from a developer sharing platform.
How is it all better than MBaaS or a botique mobile development shop? You have lower development costs and lower TCO, lower operational costs for developer collaboration, fewer mobile fragmentation nightmares and Expressway policies that can be maintained by an architect, not a dev team.
Kudos to the Expressway and HTML5 teams. If you have an interesting mobile use case that can benefit from APIs and mobile middleware, let us know in the comments!