If you're even remotely familiar with the force.com development practices, you know what apex batches are what they are used for. Running resource-intensive processes on a large volume of data is non-negotiable for a businesses and Salesforce understands this to it's core, which is why it has deployed this powerful asynchronous framework that gets the job done with state-of-the art efficiency. In this article, i'll try to skip the boring theoretical definitions (there's a ton of them, a google search away!). The goal is to be able to visualise what runs behind the scenes and how the batch framework works. The chase You already know, an apex batch class needs to implement the Database.Batchable interface. If you also don't already know what an interface is, they are like a haunted house which contains body-less souls (interface methods). These souls (methods) do not have a body, are lifeless (empty) by definition, and any one who implements the interface (buys th...