Difference between the Event Receivers , Workflows and Timer Job in SharePoint 2013?

Event Recievers	Workflow	Timer Job
Can execute either before or after the operation	Always executes after the operation	We ll Add
Can cancel the operation	Cannot cancel the operation as the item will have already been created	We ll Add
Cannot be launched manually by the user	Can be started manually by the user	We ll Add
Not designed for user interaction	Specifically designed for user interaction	We ll Add
Can execute in response to many different actions, including deletes	Can only execute in response to one of four events – Manual, an item being created, an item being edited, and an item being submitted for approval	We ll Add
Must be created in Visual Studio	Can be created with Visual Studio, Visio or SharePoint Designe	We ll Add
Syncronous Events and Asyncronous Events	Workflows are always async
Event handlers execute from a Particular WFE, So when some thing goes wrong in that WFE, It may end-up	But Workflow Jobs are robust and can resume even after Reboots.
Usually Event handlers runs for short period	Workflows can be longer even for years!
Event handlers execute from a Particular WFE, So when some thing goes wrong in that WFE, It may end-up	But Workflow Jobs are robust and can resume even after Reboots.
There is no User Interface/user Interaction in Event Receivers	Workflows can have user interactions such as getting user input in Initiation forms.
SharePoint Event receivers are triggered by events like New Item Adding-Added, Updating-Updated, Deleting-Deleted, etc	Workflows triggered only on Creation/Change/deletion.
Event handler doesn't do such.	Workflows leaves "Workflow History" logs which we can refer for debugging
Event receivers are better for large volume	Workflows are better for small amount of data.