Use Salesforce? REST APIs and Apigee Connectors for Better Enterprise Connectivity
Chances are you’re a Salesforce customer. Chances are that you are not only using Salesforce for sales and service, but also use their platform (Salesforce1) to build applications. Chances are that you have had to deal with questions like:
how do I securely access Salesforce APIs through different apps?
how do I simplify my access to other backend systems / cloud providers through Salesforce?
how can I get visibility into how the Salesforce APIs are being used, or what is Salesforce calling into?
how can I ensure that I don’t run over my Salesforce platform limits?
Apigee Edge provides answers to these questions. You can use Edge as a facade: a proxy layer which can sit between Salesforce and other apps and cloud providers.
Edge enables the exposure of normalized, consumable APIs (based on your design philosophies) that provide access to Salesforce APIs for use by other apps in your enterprise.
You can take a few different approaches to integrate with Salesforce. With a Salesforce REST API you can use service callout policies in Edge to authenticate against Salesforce and invoke methods on various standard objects, such as account and opportunity.
Volos connectors are a set of Node.js modules that enable you to connect to enterprise systems (cloud SaaS providers, databases, and cloud storage, for example) in a RESTful manner. The Volos Salesforce connector is a Node.js module that lets you fetch data from Salesforce using a RESTful API. It leverages the SOQL (Salesforce object query language) framework to provide seamless access to Salesforce data to the rest of your enterprise.
So big deal, why do I still need to use Apigee? Turns out there are several benefits.
Analytics is a core component of Apigee Edge that provides real-time and role-specific visibility into Salesforce API usage across your enterprise. You can use the out-of-the-box and custom reports to very quickly determine the overall performance of the APIs, where the bottlenecks are, what Salesforce objects are being accessed more frequently than others, what channels (mobile, web, desktop) are driving API usage, and a whole lot more.
Effective control and management over platform limits
The Salesforce platform has several limits that you can run into, including platform apex limits, static apex limits, API request limits, and Chatter REST API limits. Edge provides several traffic management policies, including concurrent rate limits, quota, spike arrest, and caching, which enable you to minimize latency for Salesforce data while providing effective control and management over platform limits.
Data shaping and flexible security
Apigee provides a rich set of transformation and security policies. You can use the transformation policies to convert the response from Salesforce and present it in formats that can be readily consumed from different apps.
You can also use the rich set of security policies to provide a consistent and flexible security facade while accessing Salesforce data from other apps in your enterprise. Apigee provides support for OAuth, SAML and other security standards. You can also use traffic management and threat protection policies as a buffer to safeguard your Salesforce data from malicious requests, limit how many times (quota) the data is accessed, and protect from sudden traffic spikes.
Several of our customers have already taken this road and are reaping the benefits of this approach. For a more detailed discussion on Edge and Salesforce integration, check out this demo: