Cited by 766Software Engineering Techniques and PracticesSoftware System Performance and ReliabilityScientific Computing and Data Management

The DOI matches its Crossref record; 63 of the 65 references it cites were found in a registry or an index; 8 of the 37 sources its claims cite were checked for support.

Machine Learning Operations (MLOps): Overview, Definition, and Architecture

Open access

Abstract

The final goal of all industrial machine learning (ML) projects is to develop ML products and rapidly bring them into production. However, it is highly challenging to automate and operationalize ML products and thus many ML endeavors fail to deliver on their expectations. The paradigm of Machine Learning Operations (MLOps) addresses this issue. MLOps includes several aspects, such as best practices, sets of concepts, and development culture. However, MLOps is still a vague term and its consequences for researchers and professionals are ambiguous. To address this gap, we conduct mixed-method research, including a literature review, a tool review, and expert interviews. As a result of these investigations, we contribute to the body of knowledge by providing an aggregated overview of the necessary principles, components, and roles, as well as the associated architecture and workflows. Furthermore, we provide a comprehensive definition of MLOps and highlight open challenges in the field.

Overview

Integrity signals

Registry

Crossref · 10.1109/access.2023.3262138

Cites

63 of 63 references verified0 citation errors · 0 not checkable

Statistics

Nothing to recompute.

Verification

Claims the paper makes

13 No basis given · 10 Own interpretation · 8 Sources not found · 7 No full text of the sources · 5 Partly supported · 3 Not checked yet · 2 Own method · 2 Own result · 1 Supported · accuracy not yet measured

Show all 18 claims

  • Probably not a substantial claim. 30
  • It may state two separate claims as one. 8
33 of 33
  • The paper relies on this without support.

    The final goal of all industrial ML projects is to develop ML products and rapidly bring them into production.

    “The final goal of all industrial machine learning (ML) projects is to develop ML products and rapidly bring them into production.”
  • The paper relies on this without support.

    MLOps is still a vague term and its consequences for researchers and professionals are ambiguous.

    “However, MLOps is still a vague term and its consequences for researchers and professionals are ambiguous.”
  • The paper relies on this without support.

    Most use cases have a read-heavy workload, combined with a batch or streaming-based ingestion pattern on very large data sets.

    “Most use cases have a read-heavy workload, combined with a batch or streaming-based ingestion pattern on (very) large data sets.”
  • The paper relies on this without support.

    Deep learning workloads (training and inference) are matrix-multiplication-heavy and therefore computation bound.

    “Typically, deep learning workloads (training and inference) are matrix-multiplication-heavy and therefore computation bound.”
  • The paper relies on this without support.

    GPUs are optimized towards matrix-multiplication-heavy workloads.

    “GPUs are optimized towards this type of workload and should be the primary focus for compute node specification.”
  • The paper relies on this without support.

    Only a small number of ML proofs of concept progress into deployment and production.

    “However, only a small number of these proofs of concept progress into deployment and production.”
  • The paper relies on this without support.

    The academic space has focused intensively on ML model building and benchmarking, but too little on operating complex ML systems in real-world scenarios.

    “Furthermore, the academic space has focused intensively on machine learning model building and benchmarking, but too little on operating complex machine learning systems in real-world scenarios.”
7 of 7

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

Citations

Cites

Show all 65 references

Research works printed but not linked: 7

  1. van der Meulen, 2018, Gartner Says Nearly Half of CIOs Are Planning to Deploy Artificial Intelligence
  2. Royce, Managing the development of large software systems, 1
  3. Beck, 2001, The agile manifesto
  4. Debois, 2009, Patrick Debois Devopsdays Ghent
  5. Mezak, 2018, The Origins of DevOps: What’s in a Name? DevOps. com
  6. Rütz, 2019, DEVOPS: A systematic literature review
  7. Baier, Challenges in the Deployment and, 1

Cited by

Sorted by citations

Metadata

Authors
Kreuzberger, D., Kühl, N., & Hirschl, S.
Affiliations
  • Karlsruhe Institute of Technology (DE)
  • IBM (Germany) (DE)
Venue
IEEE Access
Published
2023
Volume
11
Pages
31866-31879
ISSN
2169-3536 (ISSN-L)
OpenAlex
W4360995249
Cited by
766
References
65
Citations by year
2026: 245 · 2025: 239 · 2024: 168 · 2023: 106
FWCI
177.46
Type
journal article
Language
en
Open access
Locations
  • IEEE Access (publishedVersion, other-oa)
  • EPub Bayreuth (University of Bayreuth) (acceptedVersion, other-oa)
  • DOAJ (DOAJ: Directory of Open Access Journals) (submittedVersion, cc-by-sa)
Funders
  • Deutsche Forschungsgemeinschaft (491183248)
  • Open Access Publishing Fund of the University of Bayreuth
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Computer Networks and Communications › Software System Performance and Reliability
  • Social Sciences › Decision Sciences › Information Systems and Management › Scientific Computing and Data Management
Keywords
MLOps

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

A language model drew the claims from the paper on 2026-10-11, under version 3 of the claim definition (model deepseek-v4.1-flash, prompt extract-v3).

A second model labelled each claim on 2026-10-11 (model jev-1.13-20260917, definition revision gold-guideline-v0.2).

Cited sources are checked with a language model’s help (gpt-6-sol).

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review