A customer hopes to build connections to multiple legacy on-prem apps that aren’t natively connected to Salesforce

Connectors for Data Integration -Unlock External Data to Build Connected Experiences

Use Case: Multi-Org and External Data Consolidation

Robert, from GetCloudy Consulting, is answerable for keeping up the organization’s multi-organization foundation. Now, the organization is considering how they can make a client 360 by consolidating data that is spread across the entirety of the organs inside their foundation, while additionally remembering the various premises frameworks. They need to unite the entirety of this data into one single wellspring of truth.

Arrangement design interfacing numerous Salesforce organization’s data and external data.

Robert initially considered utilizing just the APIs from each organization to concentrate data. In any case, he felt that arrangement would make long improvement cycles. All things considered, Robert prescribes working with the MuleSoft group to use Heroku Connect for the 40+ organizations that were burned-through from past acquisitions. To interface numerous organs and make that solitary wellspring of truth the business was searching for, he likewise suggests utilizing Heroku Connect with a Postgres database. To incorporate the data that should be associated with the on-premises frameworks and those inside the cloud, he suggests utilizing MuleSoft connectors. More than 200 connectors are accessible to use with the goal that any Salesforce occurrence or future procured framework is covered. It reliably carries all the data from Siebel to SAP to any future framework to a similar single wellspring of truth.

Separate Between Integration Connectors

With so numerous alternatives, it very well may be hard to pick what the best coordination is for your use case. We should swim through your alternatives.

From MulSoft connectors to utilizing Heroku Connect, incorporation connectors use Salesforce APIs by means of SOAP, Bulk, and Streaming. There are contrasts between every choice with regards to three key zones:

DevOps and additionally Administrative and Ongoing Integration Maintenance



Remembering these key territories, apply the information you’ve acquired to these situations.

Use Case 1: A client needs to incorporate at scale single or various Salesforce organizations in a turnkey computerized way. The client is keen on utilizing a Heroku Postgres Database in the cloud with insignificant progressing organization exertion.

Arrangement: Heroku Connect is the joining connector proposal. As you learned in the past units, Heroku Connect offers a turnkey completely computerized mix between Salesforce organizations and their Heroku Postgres Database. Since it’s a completely overseen mix connector, the client doesn’t need to stress over keeping up and overseeing association uptime or upkeep.

Use Case 2: A client needs to coordinate single or different examples of Salesforce organizations to an Oracle or SQL database that can be on-prem or in the cloud. The client has DevOps assets to set up and keep up the association on a continuous premise. The client is additionally keen on building change and accumulation procedures on data before it’s put away in the database.

Arrangement: MuleSoft Salesforce Connector is the suggested choice. Why? It supports Oracle and SQL databases, and the Postgres Database. Likewise, the MuleSoft Salesforce Connector can be set up to interface with a database that probably won’t be in the cloud. With MuleSoft Anypoint Platform, clients can perform tasks like total data or change data before it’s put away in the database.


MuleSoft Salesforce Connector is anything but a completely overseen joining connector and requirements DevOps support to oversee and keep up the association.

Use Case 3: A client needs to incorporate data from numerous Salesforce organizations to social databases, like Postgres, Oracle, or MySQL. The data volume is relied upon to develop throughout some stretch of time—for example, an underlying volume of 10,000 records with an expansion of 1 million records inside a year. The client is economical and might want to monitor the permitting cost.

Arrangement: For this situation, choosing a MuleSoft Anypoint connector is the most ideal decision because of the permitting model. Heroku Connect puts together its estimates with respect to the number of records matched up between Salesforce and its Postgres database. This implies as the volume of records increments, so does the authorizing cost. The MuleSoft Anypoint connector permitting did not depend on the number of records matched up, which makes it a superior expense control choice. It’s critical to remember that the client is liable for overseeing and keeping up the association as the volume of data scales.

Wrap Up

At the point when you consider your answer design, recollect that utilizing combination connectors is an approach to broaden Salesforce. In spite of the fact that you needn’t bother with these devices to use Salesforce, making reconciliations that incorporate at least one of these instruments helps eliminate the plans that cause troubles in your everyday work.

A) Which MuleSoft API-led connectivity layer exposes part of a database without business logic?

check answers

B) A customer hopes to build connections to multiple legacy on-prem apps that aren’t natively connected to Salesforce. Before data is sent to Salesforce, the customer must add logic to modify the data. Which integration is best suited for this scenario?

  • I) Heroku Connect
  • II) MuleSoft Salesforce Connector
  • III) MuleSoft Database Connector
  • IV) MuleSoft HTTP Connector

Leave a Comment

Your email address will not be published. Required fields are marked *