Slack Community and become part of the ZenML family
GitHub star to show your love
Vote on the next ZenML features
What is ZenML?
ZenML is an extensible, open-source MLOps framework to create production-ready machine learning pipelines. It has a simple, flexible syntax, is cloud and tool agnostic, and has interfaces/abstractions that are catered towards ML workflows.
At its core, ZenML pipelines execute ML-specific workflows from sourcing data to splitting, preprocessing, training, all the way to the evaluation of results and even serving. There are many built-in batteries as things progress in ML development. ZenML is not here to replace the great tools that solve these individual problems. Rather, it integrates natively with many popular ML tooling, and gives standard abstraction to write your workflows.
Why do I need it?
Ichi Wa Zen, Zen Wa Ichi.
We built ZenML because we could not find an easy framework that translates the patterns observed in the research phase with Jupyter notebooks into a production-ready ML environment. ZenML follows the paradigm of Pipelines As Experiments (PaE), meaning ZenML pipelines are designed to be written early on the development lifecycle, where the users can explore their pipelines as they develop towards production.
By using ZenML at the early stages of development, you get the following features:
- Reproducibility of training and inference workflows.
- Managing ML metadata, including versioning data, code, and models.
- Getting an overview of your ML development, with a reliable link between training and deployment.
- Maintaining comparability between ML models.
- Scaling ML training/inference to large datasets.
- Retaining code quality alongside development velocity.
- Reusing code/data and reducing waste.
- Keeping up with the ML tooling landscape with standard abstractions and interfaces.
Who is it for?
ZenML is built for ML practitioners who are ramping up their ML workflows towards production. It is created for data science / machine learning teams that are engaged in not only training models, but also putting them out in production. Production can mean many things, but examples would be:
-
If you are using a model to generate analysis periodically for any business process.
-
If you are using models as a software service to serve predictions and are consistently improving the model over time.
-
If you are trying to understand patterns using machine learning for any business process.
-
In all of the above, there will be team that is engaged with creating, deploying, managing and improving the entire process. You always want the best results, the best models, and the most robust and reliable results. This is where ZenML can help. In terms of user persona, ZenML is created for producers of the models. This role is classically known as 'data scientist' in the industry and can range from research-minded individuals to more engineering-driven people. The goal of ZenML is to enable these practitioners to own their models until deployment and beyond.
Release 0.5.0 and what lies ahead
The current release is bare bones (as it is a complete rewrite). We are missing some basic features which used to be part of ZenML 0.3.8 (the previous release):
- Standard interfaces for
TrainingPipeline. - Individual step interfaces like
PreprocessorStep,TrainerStep,DeployerStepetc. need to be rewritten from within the new paradigm. They should be included in the non-RC version of this release. - A proper production setup with an orchestrator like Airflow.
- A post-execution workflow to analyze and inspect pipeline runs.
- The concept of
Backendswill evolve into a simple mechanism of transitioning individual steps into different runners. - Support for
KubernetesOrchestrator,KubeflowOrchestrator,GCPOrchestratorandAWSOrchestratorare also planned. - Dependency management including Docker support is planned.
However, bare with us: Adding those features back in should be relatively faster as we now have a solid foundation to build on. Look out for the next email!
Roadmap and Community
ZenML is being built in public. The roadmap is a regularly updated source of truth for the ZenML community to understand where the product is going in the short, medium, and long term.
ZenML is managed by a core team of developers that are responsible for making key decisions and incorporating feedback from the community. The team oversee's feedback via various channels, but you can directly influence the roadmap as follows:
- Vote on your most wanted feature on the Discussion board.
- Create a Feature Request in the GitHub board.
- Start a thread in the Slack channel.
Contributing
We would love to receive your contributions! Check our Contributing Guide for more details on how best to contribute.
Copyright
ZenML is distributed under the terms of the Apache License Version 2.0. A complete version of the license is available in the LICENSE.md in this repository.
Any contribution made to this project will be licensed under the Apache License Version 2.0.
Credit
ZenML is built on the shoulders of giants: we leverage, and would like to give credit to, existing open-source libraries like TFX. The goal of our framework is neither to replace these libraries, nor to diminish their usage. ZenML is simply an opinionated, higher-level interface with the focus being purely on easy-of-use and coherent intuitive design. You can read more about why we actually started building ZenML at our blog.
Legacy [Updated Soon Q4 2021]
From this point onwards, the README is intended to give a glimpse as to what lies ahead. We have redesigned our public roadmap to showcase better the timeline in which these features will be complete.
Quickstart
The quickest way to get started is to create a simple pipeline.
Step 0: Installation
ZenML is available for easy installation into your environment via PyPI:
pip install zenml
Alternatively, if you’re feeling brave, feel free to install the bleeding edge: NOTE: Do so on your own risk, no guarantees given!
pip install git+https://github.com/zenml-io/zenml.git@main --upgrade
Step 1: Initialize a ZenML repo from within a git repo
git init
zenml init
Step 2: Assemble, run, and evaluate your pipeline locally
import numpy as np
import tensorflow as tf
from zenml.pipelines import pipeline
from zenml.steps import step
from zenml.steps.step_output import Output
@step
def importer() -> Output(
X_train=np.ndarray, y_train=np.ndarray, X_test=np.ndarray, y_test=np.ndarray
):
"""Download the MNIST data store it as numpy arrays."""
(X_train, y_train), (X_test, y_test) = tf.keras.datasets.mnist.load_data()
return X_train, y_train, X_test, y_test
@step
def trainer(
X_train: np.ndarray,
y_train: np.ndarray,
) -> tf.keras.Model:
"""A simple Keras Model to train on the data."""
model = tf.keras.Sequential()
model.add(tf.keras.layers.Flatten(input_shape=(28, 28)))
model.add(tf.keras.layers.Dense(10))
model.compile(
optimizer=tf.keras.optimizers.Adam(0.001),
loss=tf.keras.losses.SparseCategoricalCrossentropy(from_logits=True),
metrics=["accuracy"],
)
model.fit(X_train, y_train)
# write model
return model
@step
def evaluator(
X_test: np.ndarray,
y_test: np.ndarray,
model: tf.keras.Model,
) -> float:
"""Calculate the accuracy on the test set"""
test_acc = model.evaluate(X_test, y_test, verbose=2)
return test_acc
@pipeline
def mnist_pipeline(
importer,
trainer,
evaluator,
):
"""Links all the steps together in a pipeline"""
X_train, y_train, X_test, y_test = importer()
model = trainer(X_train=X_train, y_train=y_train)
evaluator(X_test=X_test, y_test=y_test, model=model)
pipeline = mnist_pipeline(
importer=importer(),
trainer=trainer(),
evaluator=evaluator(),
)
pipeline.run()
Leverage powerful integrations
Once code is organized into a ZenML pipeline, you can supercharge your ML development with powerful integrations and on multiple MLOps stacks.
Work locally but switch seamlessly to the cloud
Switching from local experiments to cloud-based pipelines doesn't need to be complex.
pipeline.run('airflow_gcp_stack')
Versioning galore: Use caching across experiments
ZenML makes sure for every pipeline you can trust that:
Use caching to help iterate quickly through ML experiments.
Automatically detect schema
# See the schema of your data [COMING SOON]
pipeline.view_schema()
View statistics
# See statistics of train and eval [COMING SOON]
pipeline.view_statistics()
Evaluate the model using built-in evaluators
# Creates a notebook for evaluation [COMING SOON]
training_pipeline.evaluate()
Compare training pipelines
# COMING SOON
Distribute preprocessing to the cloud
Leverage distributed compute powered by Apache Beam:
# COMING SOON
Deploy models automatically
Automatically deploy each model with powerful Deployment integrations like Ray.
# COMING SOON
The best part is that ZenML is extensible easily, and can be molded to your use-case. You can create your own custom logic or create a PR and contribute to the ZenML community, so that everyone can benefit.
![[BUG]: StepInterfaceError: Unable to find materializer for output 'output' of type `<class 'keras.engine.training.Model'>` in step 'trainer'.](https://avatars.githubusercontent.com/u/60731083?v=4)
![[BUG]: Cannot load service with unregistered service type](https://avatars.githubusercontent.com/u/34342460?v=4)
![[BUG]: ZenML GPU scheduling](https://avatars.githubusercontent.com/u/17685502?v=4)
25 Dec 28, 2022
8.9k Jan 9, 2023
175 Jan 8, 2023
3.1k Jan 7, 2023
10 Apr 4, 2022
16 Sep 2, 2022
1 Jun 3, 2022
36 Jun 20, 2021
421 Dec 31, 2022
6 Feb 6, 2022
4k Jan 9, 2023
233 Jan 1, 2023
1 Feb 10, 2022
33 Dec 3, 2022
1 Apr 26, 2022
5 Jun 18, 2022
84 Nov 25, 2022
8.1k Dec 30, 2022
19 Oct 3, 2022
