A trigger in Salesforce can invoke what type of method to perform HTTP callouts?

In Salesforce, when it comes to performing HTTP callouts, the platform places certain restrictions on where and how these operations can be executed. Specifically, HTTP callouts cannot be made from synchronous triggers. The correct choice, which is the @future method, is designed to allow operations to run asynchronously, enabling HTTP callouts to occur without hindering the execution of the trigger.

The @future annotation tells Salesforce that the method should be run in the future, allowing the trigger to complete its operation without having to wait for the callout to finish. This approach is particularly significant in maintaining performance and user experience because it decouples the callout from the record save context.

In contrast, synchronous methods are executed in the context where they are invoked, which does not allow for server-side callouts. Although batch methods can execute operations asynchronously, they are intended for bulk processing of records and not specifically tailored for the immediate invocation of HTTP callouts like the @future method. An immediately invoked function in this context is not a standard practice in Salesforce and does not apply to the operation of callouts.