An architect recommended using Apex code to make callouts to an external system to process insurance quotes.
What should the integration architect consider to make sure this is the right option for the integration?
An architect recommended using Apex code to make callouts to an external system to process insurance quotes.
What should the integration architect consider to make sure this is the right option for the integration?
When considering making callouts to an external system using Apex code, it is crucial to understand the limits associated with such callouts. Among these, the maximum callouts in a single Apex transaction is essential because it directly impacts how many external calls can be successfully made without hitting Salesforce's governor limits. This is fundamental to ensuring that the integration can handle the required volume of calls efficiently and without errors, making this the most pertinent consideration in this scenario.
I think the concern here is about the time to process the call. C is about DML or operation being performed in the same transaction ? Which is not mentioned. D is about >5 sec calls and concurrency
A, B and D also are limits bit here main problem is C: You can’t make a callout when there are pending operations in the same transaction. https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_callouts_timeouts.htm
DML, Asynchronous(Batch etc,.) are not mentioned to consider pending operations. Hence the limit of long running requests apply here.
A is about quote bulkification. Likely not a problem. B is specific to continuation job, but parallel callout is for bulkification