There is a nice article about this (including workflow tutorial).
I agree with the conclusions but in reality I don’t prefer to go for workflows for business logic even if its simple. It’s not difficult to find developer to code plugins. Yes its more complex, developer depended but more efective.
https://www.tutorialspoint.com/microsoft_crm/microsoft_crm_workflow_processes.htm
The following list tries to explain the same −
- Although plugins and workflows both can be used to run synchronous as well as asynchronous logic, plugins are generally preferred for synchronous logic, while workflows for asynchronous logic.
- Generally, to implement complex business logic, plugins are preferred over workflows. Workflows are preferred when you want to achieve relatively easier functionalities (such as sending emails, assigning users, etc.)
- Plugins need to be developed with coding, while workflows can be configured directly by business users without any knowledge of workflows.
- Workflows can run on-demand. Hence, if there are requirements where the user wants to run some logic manually, workflows would be a better choice.
- From performance impact, synchronous plugins provide a better performance (and throughput) as compared to real-time workflows in scenarios where the request frequency is higher.