|Available in: Enterprise, Performance, Unlimited, and Developer Editions|
With the advent of BigObjects, it’s possible to keep billions of records on the platform. Salesforce has made new platform services available to help you work at this new scale, by combining BigObject data with your core business data.
Async SOQL is implemented in the form of a RESTful API that enables you to run queries in the familiar syntax of the SOQL language. You can run multiple queries in parallel, and monitor their completion status.
Each query runs in the background, and the results are deposited into an object you specify, which can be an sObject or BigObject. As a result, you can subset, join, and create more complex queries that are not subject to timeout limits. This is ideal when you have millions or billions of records, and need more performant processing than is possible with synchronous SOQL.
For more information, see the Async SOQL Guide.
Async SOQL Versus Data Pipelines
Async SOQL is related to Data Pipelines, but is focused on object-level segmentation, aggregation, and filtering, and does not allow you to interact with Salesforce files. The figure below compares the two methods.
To use Async SOQL effectively, it’s helpful to understand its key components and other related concepts. Why would you use an asynchronous SOQL query instead of standard SOQL? The following table lists the key decision criteria across the broadest array of use cases.
|Reasons For||Reasons Against|
|Reliability||Immediacy of Result|
|Scale||< 50M Scale|