Future Method Vs Queueable Apex Vs Batch Apex | A Detailed Comparison

[@anshulausome]

Really awesome, great comparison of all the asynchronous apis of Salesforce

[@zordial]

Thanks Anshul

[@aswinbalaji2608]

Thanks for detailed info.

[@imtiyazansari9713]

Sir I think in each bach we can do 100 callouts but by mistake you typed 10 in last slide

[@SuperHayat89]

Awesome

[@sumanbhujabal3611]

Helpful

[@sasikumar-kg1ps]

Why we need to use Future method, because all thing we can do in queueable right?

[@sudan9735]

Great question, will wait for someone to answer through !!

[@SachinM1985]

we can not monitor the jobs by using future, also we cannot use non-primitive data type in future and changing not possible in Future method, all these overcome by queueable.

[@sudan9735]

@@SachinM1985 thanks for the explanation Sachin, the question was if queueable can do all of these right why do we even need future method ?

[@SachinM1985]

@@sudan9735 jobs which are not important, we can run them in separate thread for this we use future method

[@maheshbabu-te8sk]

@@sudan9735 one reason we can avoid mixed dml exception we need to use future annotation for particular method

[@vipulukey828]

Why did u skip schedulable apex?

[@mksays2255]

please correct batch apex cannot be called from another batch apex

[@saddaaddajourney]

kripya hindi mein bhi vedio banaye