Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Practical Devops for the busy data scientist: Alice in DataOps land

Practical Devops for the busy data scientist: Alice in DataOps land

Everyone uses the buzzword DevOps. Pretty much every company has hired or is about to hire a DevOps engineer or specialist. But how does this translates to Machine learning? What is more, how does this relate to your models' development, training, and deployment?

In this talk, we will debunk some of the DevOps terms and myths. The talk will include Machine learning examples and terms will be explained in a suitable way for data scientists/machine learners/ anyone willing to understand from scratch what is DevOps and how to use it.

Tania Allard

July 16, 2019
Tweet

More Decks by Tania Allard

Other Decks in Technology

Transcript

  1. Tania Allard, PhD @ixek Developer Advocate @Microsoft Google Developer expert

    ML -Tensorflow Practical DevOps for the busy Data Scientist OSCON 2019 http://bit.ly/OSCON-MLOps
  2. 4 A common story... @ixek Model / application to be

    productised R&D - develop, iterate fast, usually local or cloud Magic Is it live??
  3. 6 Replacing the magic @ixek Model/app ready to productise R&D

    - develop, iterate fast, usually local or cloud MLOPs, automation, controlled deployment Worry free deployment! Wait and relax
  4. 10 DevOps is the union of people, process, and products

    to enable continuous delivery of value into production What is DevOps anyway? @ixek
  5. 11 Sort of DevOps applied to data-intensive applications. Requires close

    collaboration between engineers, data scientists, architects, data engineers and Ops. How does it fit for DS? @ixek
  6. 13 @ixek MlOps Aims to reduce the end-to-end cycle time

    of data analytics/science from the origin of ideas to the creation of data artifacts.
  7. 14 @ixek What to automate? Establish checkpoints Find the low

    hanging fruits How stable and robust are my processes? Devise a long term strategy What can I readily improve? Where am I? Can I count? Getting started
  8. 23 Use canonical data sources - always know what data

    you are using (where it comes and goes) @ixek
  9. 26 What and when to automate? @ixek • What should

    we automate? • Define success and failure metrics • Go from simple to complex tasks • Evaluate and monitor
  10. 36 Summary @ixek 1. DataOps help create value and improve

    end-to-end ML 2. Start by identifying the low-hanging fruits and defining automation success 3. Choose the right tooling and processes 4. Leverage people and processes 5. Implement wisely