paradigm VS Kedro

I built Paradigm from scratch to deploy any model at scale. It deploys the model on Kubernetes with load balancers. If you run into any issues, I'm happy to guide you on how to use it.

I started with paradigm. I got a deeper understanding about argo workflows through it as well. Helps to get a proper grab of industry standards from the beginning.

For scalability, it should be on Kubernetes. This is the best solution I have come across. You can deploy the model as a service with a LoadBalancer. You can refer to Kubernetes services or use a tool such as this one that handles building the service for you.

I came across this tool today and checked it out, I feel this can get the job done very quickly without so many complex features. It is also very small in size, so does not take up a lot of space in the cluster as well.

Link - https://github.com/ParadigmAI/paradigm It seems to be a pretty new project. But this has high usability.

Prefect is a good choice, But I wanted a much simpler tool. Hence, I built a barebone workflow controller here.

Interesting, thanks for sharing. I'll definitely take a look, although at this point I am so comfortable with Snakemake, it is a bit hard to imagine what would convince me to move to another tool. But I like the idea of composable pipelines: I am building a tool (too early to share) that would allow to lay Snakemake pipelines on top of each other using semi-automatic data annotations similar to how it is done in kedro (https://github.com/kedro-org/kedro).

# pyproject.toml [project] dependencies = [ "kedro @ git+https://github.com/kedro-org/kedro@3ea7231", "kedro-datasets[pandas.CSVDataSet,polars.CSVDataSet] @ git+https://github.com/kedro-org/kedro-plugins@3b42fae#subdirectory=kedro-datasets", ]

So there's 2 sides to pipeline management: the actual definition of the pipelines (in code) and how/when/where you run them. Some tools like prefect or airflow do both of them at once, but for the actual pipeline definition I'm a fan of https://kedro.org. You can then use most available orchestrators to run those pipelines on whatever schedule and architecture you want.

We have set up a milestone on GitHub so you can check in on our progress and contribute if you want to. To suggest features to us, report bugs, or just see what we're working on right now, visit the Kedro projects on GitHub.

you could use a project framework like kedro to force you to be more disciplined about how you structure your projects. I'd also recommend checking out this book: Edna Ridge - Guerrilla Analytics: A Practical Approach to Working with Data

Recently I started a position as Developer Advocate for Kedro, an opinionated data science framework, and one of the things we're doing is exploring what are the best open source tools we can use to create our documentation.

You can also check out Kedro, it’s like the Flask for data science projects and helps apply clean code principles to data science code.

An often overlooked framework used by NASA among others is Kedro https://github.com/kedro-org/kedro. Kedro is probably the simplest set of abstractions for building pipelines but it doesn't attempt to kill Airflow. It even has an Airflow plugin that allows it to be used as a DSL for building Airflow pipelines or plug into whichever production orchestration system is needed.