The reviewed record of science sign in
Pith

arxiv: 2107.00079 · v1 · pith:GDXUDG4I · submitted 2021-06-30 · cs.LG

Using AntiPatterns to avoid MLOps Mistakes

Reviewed by Pith T0 review T1 audit T2 compute T3 formal T4 kernel pith:GDXUDG4Irecord.jsonopen to challenge →

classification cs.LG
keywords antipatternsdescribemlopspracticesbestfinanciallessonsvocabulary
0
0 comments X
read the original abstract

We describe lessons learned from developing and deploying machine learning models at scale across the enterprise in a range of financial analytics applications. These lessons are presented in the form of antipatterns. Just as design patterns codify best software engineering practices, antipatterns provide a vocabulary to describe defective practices and methodologies. Here we catalog and document numerous antipatterns in financial ML operations (MLOps). Some antipatterns are due to technical errors, while others are due to not having sufficient knowledge of the surrounding context in which ML results are used. By providing a common vocabulary to discuss these situations, our intent is that antipatterns will support better documentation of issues, rapid communication between stakeholders, and faster resolution of problems. In addition to cataloging antipatterns, we describe solutions, best practices, and future directions toward MLOps maturity.

This paper has not been read by Pith yet.

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.