Building a machine learning model one time can be done in an ad-hoc manner, but if you ever want to update it and serve it in production you need a way of repeating a complex sequence of operations. Dagster is an orchestration engine that understands the data that it is manipulating so that you can move beyond coarse task-based representations of your dependencies. In this episode Sandy Ryza explains how his background in machine learning has informed his work on the Dagster project and the foundational principles that it is built on to allow for collaboration across data engineering and machine learning concerns.
- How did you get involved in machine learning?
- Can you start by sharing a definition of "orchestration" in the context of machine learning projects?
- What is your assessment of the state of the orchestration ecosystem as it pertains to ML?
- modeling cycles and managing experiment iterations in the execution graph
- how to balance flexibility with repeatability
- What are the most interesting, innovative, or unexpected ways that you have seen orchestration implemented/applied for machine learning?
- What are the most interesting, unexpected, or challenging lessons that you have learned while working on orchestration of ML workflows?
- When is Dagster the wrong choice?
- What do you have planned for the future of ML support in Dagster?
- From your perspective, what is the biggest barrier to adoption of machine learning today?
- Thank you for listening! Don't forget to check out our other shows. The Data Engineering Podcast covers the latest on modern data management. Podcast.__init__ covers the Python language, its community, and the innovative ways it is being used.
- Visit the site to subscribe to the show, sign up for the mailing list, and read the show notes.
- If you've learned something or tried out a project from the show then tell us about it! Email firstname.lastname@example.org) with your story.
- To help other people find the show please leave a review on iTunes and tell your friends and co-workers
- Apache Spark
- Peter Norvig
- Josh Wills
- REPL == Read Eval Print Loop