3 ms·
It really depends on the SaaS products. Often we have to pull the data out of the REST API, like you suggested. I have no experience with salesforce, but a quic
by Avalaxy 7y ago
It really depends on the SaaS products. Often we have to pull the data out of the REST API, like you suggested. I have no experience with salesforce, but a quick Google taught me that you can access their database. This is done using SOQL, as illustrated here https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql.htm https://developer.salesforce.com/docs/atlas.en-us.soql_sosl..... In this case you just pull the data out of salesforce when you need it, without caching it in your own database.
I hope this helps you, let me know if it gets you any further.
- charlesnodier 7y agoThanks Avalaxy. That's exactly what we're doing now (pulling data out of Salesforce using SOQL). The issue is that we're starting to do it so frequently that we're bumping up against Salesforce's API call limits.
- Avalaxy 7y agoGotcha. With a high velocity of data changes this is usually done with streaming data. Just did another quick google and I saw that SalesForce has a Streaming API that lets you capture events: https://developer.salesforce.com/docs/atlas.en-us.api_streaming.meta/api_streaming/intro_stream.htm https://developer.salesforce.com/docs/atlas.en-us.api_stream... Their description sounds like your use case: > Applications That Poll Frequently Applications that have constant polling action against the Salesforce infrastructure, consuming unnecessary API calls and processing time, would benefit from Streaming API because it reduces the number of requests that return no data. I hope this will help you.