An Agent is much more flexible than any SharePoint feature, so questions like these can be hard to define. Sure, workflows are a functional match for some agents. Event Receivers are a match for other agents. timer jobs are yet another match, SSIS packages could be yet another match.
Agents have such broad application that you need to combine a number of different pieces from the Microsoft stack to achieve the same functions. And not all of those pieces even reside within SharePoint.
I've found it more applicable to compare Agents to Visual Studio work - that is the environment in which you can truly write code. It is much too flexible and broad to pigeonhole into a concise chart.
An Agent is much more flexible than any SharePoint feature, so questions like these can be hard to define. Sure, workflows are a functional match for some agents. Event Receivers are a match for other agents. timer jobs are yet another match, SSIS packages could be yet another match.
Agents have such broad application that you need to combine a number of different pieces from the Microsoft stack to achieve the same functions. And not all of those pieces even reside within SharePoint.
I've found it more applicable to compare Agents to Visual Studio work - that is the environment in which you can truly write code. It is much too flexible and broad to pigeonhole into a concise chart.