Yeah! So I'm not an expert with domino, but looking at it, it serves a slightly different purpose.
DAGWorks is an opinionated way to write code that allows you to abstract it away from the infrastructure, whereas Domino is more about making it easy to deal with infrastructure, manage datasets, etc... Also has a large notebook/development focus. Nothing in is built to make it natural for the code to live for a while/keep it well-maintained, which is the problem DAGWorks is trying to solve.
The idea is that we can allow you to plug into whatever infrastructure you want and not have to think about it too much when you want to switch, although we're still building pieces of that out.
DAGWorks is an opinionated way to write code that allows you to abstract it away from the infrastructure, whereas Domino is more about making it easy to deal with infrastructure, manage datasets, etc... Also has a large notebook/development focus. Nothing in is built to make it natural for the code to live for a while/keep it well-maintained, which is the problem DAGWorks is trying to solve.
The idea is that we can allow you to plug into whatever infrastructure you want and not have to think about it too much when you want to switch, although we're still building pieces of that out.