Bulk API

Question 1

What are the use-cases for Bulk API?

Answer 1

• Loading large volumes of data in a single transaction.
• Searching large volumes of data in a single transaction.

Question 2

BULK API 1.0 vs Bulk API 2.0

Question 3

What is an Idempotent design pattern?

Answer 3

In an enterprise application, it’s usually a good idea to use a message broker that guarantees at-least-once delivery. At-least once delivery guarantees that a message broker will deliver a message to a consumer even if errors occur. One side-effect, however, is that the consumer can be invoked repeatedly for the same message. Consequently, a consumer must be idempotent: the outcome of processing the same message repeatedly must be the same as processing the message once. If a consumer is not idempotent, multiple invocations can cause bugs.

Question 4

Bulk API Data Volume limits?

Answer 4

Bulk API is synchronous when submitting the batch request and associated data. The actual processing of the data occurs asynchronously.

• Up to 10,000 batches can be submitted per rolling 24–hour period.
• A batch can contain a maximum of 10,000 records.
• Event Message—The maximum event message size is 1 MB. Publishing an event using the Salesforce APIs counts against your standard API limits.