Download to read offline
Uploaded byDaniel Peter
Callout architecture
The document discusses high-performance web service callouts on the Force.com platform, addressing issues like per-transaction limits and platform limits. It presents both native and proxy solutions for managing numerous callouts efficiently, highlighting a scalable but slower native solution versus a faster proxy implementation. Links to demos and code repositories are provided for further exploration.
More Related Content
Similar to Callout architecture
Callout architecture
- 1. High performance WebService Callouts on force.com
- 2.
- 3.
- 4. Native solution callout 1 callout2 callout 3 … callout 100 HTTP: callout 1 callout 2 … callout 10 BACKLOG: callout 11 … callout 100 HTTP: callout 11 callout 12 … callout 20 BACKLOG: callout 21 … callout 100 HTTP: callout 91 callout 92 … callout 100 BACKLOG: …
- 5. Native solution codedemo • https://na15.salesforce.com • http://some.webservice.com/viewer.php
- 6.
- 7.
- 8.
- 9.
- 10. Proxy solution 1 callout Infinite records callout proxy requestfull record data from IDs Some web service Receive full record data
- 11. Rolling curl • SmarterImplementation of php’s curl_multi_exec • https://code.google.com/p/rolling-curl
- 12.
- 14. Demo code ongithub https://github.com/danieljpeter/high_performance_force.com_callouts
- 15. Scalable, fast, butanother thing to maintain.
- 16.