Zalando's Machine Learning Platform: from experimentation notebooks to production pipelines at scale
Crossing the gap between notebook-based ML experimentation and production-grade pipelines was the core challenge: Jupyter notebooks do not scale to production requirements (security, reproducibility, observability, performance), and manually writing CloudFormation templates for pipelines was verbose and error-prone.
CloudFormation templates for Step Functions pipelines became too verbose and tedious to edit manually at scale, requiring an internal abstraction layer (zflow) to remain maintainable.
zflow has been used to create hundreds of ML pipelines at Zalando, and the tooling abstracts away infrastructure complexity so ML practitioners can focus on their domain rather than the infrastructure.
Frequently asked questions
What did this team achieve with this AI workflow?
zflow has been used to create hundreds of ML pipelines at Zalando, and the tooling abstracts away infrastructure complexity so ML practitioners can focus on their domain rather than the infrastructure.
What tools did this team use?
JupyterHub, Databricks, Apache Spark, Amazon SageMaker, AWS Step Functions, AWS CDK, CloudFormation, AWS Lambda, S3, BigQuery.
What results were reported?
ML pipelines created with zflow: hundreds of pipelines; time to start experimenting in Datalab: less than a minute (source-reported, not independently verified).
What failed first in this deployment?
CloudFormation templates for Step Functions pipelines became too verbose and tedious to edit manually at scale, requiring an internal abstraction layer (zflow) to remain maintainable.
How is this ecommerce ops AI workflow structured?
Explore data in Datalab → Scale up with Databricks/Spark → Define pipeline with zflow DSL → Generate CloudFormation template → Deploy via Zalando CDP → Execute Step Functions pipeline → Monitor via ML portal.