In any instance where you might use a batch job or scheduled task, or in situations that involve complex ever-changing business requirements, the saga pattern is generally a good fit. However there are some things you should keep in mind.
While it may be tempting to throw a whole bunch of logic, data access, and the whole kitchen sink into a saga, this is not a good idea.
Although saga data storage is abstracted to be very easy to work with, remember at some point that data needs to be persisted somehow. In production, the default is to use RavenDB, but you can also use a relational database via NHibernate, or roll your own saga storage by creating an implementation of
ISagaPersister and registering it with the ...