Choosing an iPaaS for Mobile-enabling Applications with secure APIs
I attended a great session on strategies to mobile-enable your applications at the Gartner AADI Summit this morning. Gartner Analysts Gordon Van Huizen and Massimo Pezzini discussed several challenges and strategies to tackle the hot topic of mobile-enablement of applications and API management. Massimo presented two styles of mobile application integrations – point-to-point and mediated.
Given the heterogenous nature of today’s IT application architecture, the latter is the more common scenario. This means most customers would need to insert a mediation layer that can provide a level of indirection, a level of control, and the ability to aggregate data across multiple applications to deliver pertinent information in a single API call. This is a great time to consider an iPaaS (integration platform as a service) as the tool to handle this use case. This is particularly important when part of your application portfolio is in the cloud. The traditional ESBs are just not designed to handle the brave new world of SaaS. Choose your new integration platform wisely.
It is also critical that the iPaaS has been purpose-built for the web and mobile architectures of this new world. The last thing you need is a platform that needs kludgy fixes to adapt to mobile-friendly protocols such as REST, HTML5, etc. Customers feel a sense of comfort that their investments in SnapLogic for four main reasons:
- REST-based: Every SnapLogic pipeline (data flow) can be exposed as a REST service with a flip of a switch (click of a mouse in a check box, really). These services can be secured for appropriate authorization and authentication to make sure they are fully secure.
- JSON Format: The internal data representation of SnapLogic pipelines is in JSON format, which is the preferred format for all mobile APIs. This means there is ZERO additional effort to convert an existing pipeline into an API. Other iPaaS offerings that are using non-JSON (records, proprietary structures, etc.) as internal representation need to add a layer of overhead where the internal representation needs to be converted into JSON before the API call is responded to.
- Orchestration and Aggregation: As demonstrated in the architecture diagram in the above picture, orchestration or aggregation is a key requirement in mobile-enabling of applications. Mobile application developers expect all the relevant information in a single API call and not have to go to multiple applications individually and then piece that information together on the mobile client app. SnapLogic delivers multi-point hybrid integration capabilities that effortlessly orchestrates or aggregates across the firewall boundaries, whether the data is residing in the cloud or on-premise. The 160+ prebuilt connectors, called Snaps, also greatly simplify the integration design and development.
- Elasticity: And lastly, future-proofing the iPaaS layer to handle exploding mobile API loads is totally non-negotiable. SnapLogic’s elasticity allows customers to scale out dynamically to handle variable workloads.
A Fortune 50 customer mobile-enabled its salesforce by using SnapLogic as the mediating iPaaS. They exposed SnapLogic pipeline that aggregated data across Salesforce and Oracle E-Business Suite. The sales reps were able to access all relevant information (customer contact information and products owned from Salesforce, and payment status from Oracle E-Business Suite). They secured the API by integrating SnapLogic with CA’s Siteminder for authentication and SSO.
For the above reasons, SnapLogic becomes the iPaaS of choice for mobile-enabling your application infrastructure. Please feel free to reach out to me with your comments and questions on my twitter handle (@mpjoshi) or by leaving comments on the blog.