When your Kedro projects scale, have you faced challenges such as:
⢠𪢠High dependency between development and production?
⢠š§ Difficulty in making changes without impacting the entire pipeline?
⢠ⳠLarge dependency footprints, with long installation times?
⢠𧶠Monolithic testing, requiring full pipeline tests in CI/CD?
⢠āļø Multiple teams using the same pipeline code but with different configurations?
We've developed a tool called Alloy that helps data science teams scale their applications by building consumable Kedro pipelines from reusable Python packages, enforcing best development practices. We are currently seeking users interested in trialing Alloy to support our research on potentially open-sourcing it as a sister product to Kedro. Please react with š if you'd be interested in learning more
š§¶ 4
𧬠3
𤩠4
š 4
š 3
šš¼ 1