Reasons to Kedro

collaboration - Sharable catalog - small nodes over monolithic notebooks - catalog - easily load anything without needing to run - No need to write...

Reasons to Kedro #

  • collaboration
    • Sharable catalog
    • small nodes over monolithic notebooks
  • catalog
    • easily load anything without needing to run
    • No need to write read/write code
  • pipeline
    • No need to keep execution order in your head
    • easily run a slice of a pipeline
  • plugins
    • pip install
    • make your own
  • hooks
  • flexible expandable cli

Reasons Not to Kedro #

  • Already utilizing another DAG framework
  • Data is not in a widely supported format
  • Micro short-lived project
  • Large Project / Deadline
    • Use a lower profile project to learn first
  • Team not willing to change
  • Need minimal dependencies
  • God Project - kedro owns everything??

Connections

Related tags and posts connected to this entry.