atomate is essentially intended to be a better version of MPWorks, and will likely replace MPWorks soon. The number of changes is too much to detail but some examples:
- atomate does a much better job of MPWorks of not mixing in execution with the real content of the workflow. It has features like "env_chk" that help with this
- MPWorks requires 4 databases (SNL, submissions, FireWorks, output), whereas atomate only has 2 (FireWorks, output) - and even the latter is usually optional.
- atomate is much more modular in terms of building up workflows and really having reusable components
- the code is much clearer
- there are additional features like builders in there
- various improvements like more clear task documents vs MPWorks
- more workflows are implemented
I can't tell you how long it would take you to implement a workflow, especially given that I have no knowledge of what that workflow will be. I think it is best if you look at the code and try to make an estimate for yourself. Note that many people have now contributed what I would call moderately complex workflows and it usually doesn't take very long.
Best,
Anubhav