Real Time Integration vs Near Real Time Integration?
A typical Salesforce integration can be designed as Real Time Sync or Near Real Time Sync (Batch). One of the preferred way is to use a third party integration tool that provides benefits like direct connectors to various applications, ease of use, ease of maintenance, enterprise ready, etc.
The below mentioned comparative analysis and parameters will help an organization choose the right type of sync for their business requirements.
During the Salesforce (or any other system) Integration discussions, business users are always keen to see the data instantly and prefer a real time integration. Many times, the integration tool and its edition is selected under the assumption that the real time integration will be available, but, it is realized later that a separate option/license is required (that comes with additional cost) to use real time option and that makes business users to settle with near real time integration option.
In summary, if the inherent requirement is to integrate the data instantly in real time, then real time integration will be the preferred choice even if it comes at an extra cost and added complexity. For all other cases where data integration is delayed by few minutes and adequate API is available, near real time option works the best.
Senior IT Manager- Salesforce Platform at BMC Software
8 年Nice article Sumit. A small comment on maintenance. If we are talking about an enterprise integration, a near real time integration might need the additional retry, try/catch logic. Probably one more thing to consider when looking for a tool.
Country Leader | Consulting | Technology | Strategy | Product
8 年Thanks Robert for your comments. Please see my response below: - Why would the API Consumption be any higher for a batch? The Select statement would still only select the number of records that are eligible. Sumit - Since this is near real time integration (batch), it is running every minute or so and thus, every time it is firing the select statement and that consumes an API call. And thus, in a day, you are consuming around 1500 API calls and there may be very few updates here. - Why is there a license cost? If you can do a callout on one type of integration, you can do so on another. Are you assuming a certain type of license? (Enterprise vs Unlimited, etc?) Sumit - The license type is applicable on the ETL tool or middleware. If you use Boomi, Informatica or other, they need a separate license to listen to the callouts or outbound messages (act as listener). - Why do you see the Maintenance as being higher for a real-time vs a batch? They both would still require a WSDL (or HTTP package) and would both need to make the call and handle the response. Sumit - While using an ETL tool or middleware, you simply select the object for question and you do not require WSDL (or HTTP package). To implement real time integration using an ETL tool or a middleware, you need additional components like Outbound message or apex callouts and hence additional components will require additional maintenance. I hope it answers your questions.
Group Salesforce.com Application Architect at Citrix - 18 Salesforce Certifications - Presented at Dreamforce three times - Trailhead All-Star Ranger
8 年I actually have a few questions on your comparison. - Why would the API Consumption be any higher for a batch? The Select statement would still only select the number of records that are eligible. - Why is there a license cost? If you can do a callout on one type of integration, you can do so on another. Are you assuming a certain type of license? (Enterprise vs Unlimited, etc?) - Why do you see the Maintenance as being higher for a real-time vs a batch? They both would still require a WSDL (or HTTP package) and would both need to make the call and handle the response. Thanx!