I'm a little confused by the article. Everything mentioned seem to be real problems you'll fairly quickly run into that need real solutions (passing data over the network, handling transient errors).
Celery + Redis is already mature, easy, and can be setup quickly. Not my favorite framework by any means but it seems to work, more or less
Sure, my argument is that those concerns should be composable with the distribution layer, not defined by it. There are plenty of different ways to pass data across a network or between machines, I'm not going to reinvent them all. There are also plenty of ways to manage non-transient errors (and very app-specific), I'm not going to implement them all. I'm also not assuming you need or want object persistence and replayability of your workflows. If you do, then use the right tool for the job.
Celery + Redis is already mature, easy, and can be setup quickly. Not my favorite framework by any means but it seems to work, more or less