 Let's understand Qable Apex. So Qable Apex is basically a super set of future methods, which provides some extra benefits, extra features as well. So you might have gone through future methods and Apex batch Apex examples. So if we talk about Qable Apex, so it can be known as combination of future methods and batch Apex. So this you will feel in the syntax as well. So in future method basically limitation is we can work on primitive arguments only, but here that limit is not available you can go beyond primitive arguments as well. And in batch Apex like we use three methods start, execute and finish. So similarly like here in Qable Apex you need to define one method. So that's why it is known as combination of future methods and batch Apex. Then if you want to execute your Qable Apex so you need you can call the class by a simple system.nqjob method. So similarly like in batch Apex as well we use execute batch method to execute the batch Apex. So when you call nqjobs method so it returns a job ID that can be monitored. So that ID basically you can use to monitor like different parameters related to Qable Apex. Now let's talk about the additional benefits those are available with Qable Apex. So first is non-primitive types. In case of future methods you are restricted with primitive data types or primitive arguments. And maybe like you can have collection of primitives but that to primitives only. In Qable Apex you can go beyond primitive data types and you can use non-primitive types as arguments. So it means you can work on S objects as well in Qable Apex. Now if you talk about monitoring so Qable Apex can be monitored in two ways like you can monitor it with the help of UI. By searching Apex jobs and quick find and setup and you can see the status of your Qable Apex job. Also when you run nqjob method so it basically returns the ID, job ID and with the help of that job ID you can also monitor your Qable Apex. The third benefit is chaining jobs. So if you want to call one process through another so that you can do with the help of Qable Apex. So chaining of jobs is available in Qable Apex which is not available with future method. So these are some benefits those are additional to a future method that's why we prefer Qable Apex. This is the syntax of future method. So in case of future method you need to use adverite annotation map. Sorry, you need to use adverite future annotation for particular method. So if you use this annotation adverite future so that method will work as a future method that will be executed or synchronously. So here method name is my future method it is receiving a list of string as parameters and you can see string is a primitive type but we are using collection of primitive so that is permissible. And here you can write the code and through this future method we are calling my sync method and we are passing parameters. Basically what we are doing we are defining this my sync method individually. So we can call it directly without making it future method and we can call it through future method as well. So this way like a future method can be useful. Now talking about Qable Apex syntax so here you need to implement a class named as some class so it name can be anything. Now we need to implement one interface that is Qable. So it is kind of similar to batch Apex so in batch Apex also we need to implement an interface and then we need to define start execute and finish methods. So similarly in Qable Apex as well. You need to implement Qable interface and you will be defining only one method that is execute. You don't need to define start and finish methods in Qable Apex. Now if I talk about future method again so in future method you can see we don't need to implement any interface. We just need to use at the rate future annotation to convert any method in future method. Whereas in Qable Apex syntax is totally different. And here in execute method you need to use Qable context instance that is context name can be anything but Qable context this class should be same. And inside this execute method you will be implementing actual code that will be executed while you will be executing your Qable Apex. So this is brief about Qable Apex.