When you implement Salesforce, you must integrate it with other applications for higher organization wide productivity. Although, each integration scenario is unique, there are common requirements and issues that must be resolved. Architects and developers understand integrations needed in-detail and apply best practices during the design and implementation phase of a Salesforce integration project. Once implemented, you to get to production as fast as possible and have the most stable, scalable, and maintenance-free set of applications possible.

Based on the best practices, the Integrations are classified broadly into 3 categeories:
  1. Data Integration - The requirement to synchronize data that resides in two or more systems so that both systems always contain timely and meaningful data. Data integration is often the simplest type of integration to implement, but requires proper information management techniques to make the solution sustainable and cost effective. Such techniques often include aspects of master data management (MDM), data governance, mastering, de-duplication, data flow design, and others.
  2. Process Integration - This category addresses the need for a business process to leverage two or more applications to complete its task. When you implement a solution for this type of integration, the triggering application has to call across process boundaries to other applications. Usually, these patterns also include both orchestration, where one application is the central "controller" and other, where applications are multi-participants and there is no central "controller". These types of integrations can often require complex design, testing, and exception handling requirements. Also, such composite applications are typically more demanding on the underlying systems because they often support long-running transactions, and the ability to report on and, or manage process state.
  3. Virtual Integration - This category addresses the need for a user to view, search, and modify data that's stored in an external system. When you implement a solution for this type of integration, the triggering application has to call out to other applications and interact with their data in real time. This type of integration removes the need for data replication across systems, and means that users always interact with the most current data.

Choosing the best integration strategy for your system is in the hands of a expert team which consists of Architects, Project Managers, Developers, Testers etc., but the most important differentiator is a team that's certified and understands the dynamic changes Salesforce platform has undergone and upcoming, current roll outs.

See what HBR is saying about the #1 platform for integrations

Get the Essence

Learn How Dextara can help you?

Learn about our Integration Patterns