Ha! Kedro maintainer just joined on the hamilton slack, and we were talking it over :) here’s what I was thinking:
TL;DR hamilton is lighter weight and less opinionated about non-pipeline stuff, it also has a different way of specifying pipelines (that we prefer).
I think there are a few key differences in the approach:
- currently, hamilton is lighter weight and less opinionated about directory structure/style guide. It’s just a library!
- Kedro pipelining (from what I understand) has you define the nodes separately to specifying their inputs, whereas in hamilton it’s function-first, and the functions specify everything. It’s funny — Kedro is actually very similar to the framework I first designed to solve the problem and compared with @Stefan Krawczyk’s idea (that became hamilton), I called it “burr”
- Kedro has a whole bunch of additional features that allow it to integrate with the outside world and hamilton is pretty lighter weight here (although we’ll likely be adding more)
TL;DR hamilton is lighter weight and less opinionated about non-pipeline stuff, it also has a different way of specifying pipelines (that we prefer).
I think there are a few key differences in the approach: - currently, hamilton is lighter weight and less opinionated about directory structure/style guide. It’s just a library! - Kedro pipelining (from what I understand) has you define the nodes separately to specifying their inputs, whereas in hamilton it’s function-first, and the functions specify everything. It’s funny — Kedro is actually very similar to the framework I first designed to solve the problem and compared with @Stefan Krawczyk’s idea (that became hamilton), I called it “burr” - Kedro has a whole bunch of additional features that allow it to integrate with the outside world and hamilton is pretty lighter weight here (although we’ll likely be adding more)