liveBook · Manning

Machine learning infrastructure

As explained in Designing Deep Learning Systems: A guide for software engineers

The software, hardware, and services that support machine learning data processing, training, deployment, and operation.

Machine learning infrastructure is the software, hardware, and services that make data processing, model training, deployment, serving, monitoring, and maintenance repeatable and reliable. It supports data scientists, data engineers, MLOps engineers, platform engineers, and AI applications across the development cycle. section 1.1.2

A reference infrastructure stack commonly includes:

  • Data warehouses and ingestion pipelines for collecting, transforming, enriching, labeling, and processing data. section 1.1.2
  • Compute platforms, workflow orchestration services, and training services for executing development workloads. section 1.1.2
  • Model metadata and artifact stores, serving services, and monitoring systems for deployment and production operation. section 1.1.2

Its central production requirement is a smooth path from data and experimentation to scalable deployment and monitoring. Automation reduces operational work, communication, and coordination costs, allowing data scientists to complete more of the cycle independently without becoming DevOps or data-engineering specialists. section 1.1.4

Productionizing a model

A data scientist uses shared infrastructure to set up a data pipeline, train a model, deploy it for production use, and monitor model performance, while the platform supports the surrounding automation and operations. section 1.1.2 section 1.1.4

How Designing Deep Learning Systems: A guide for software engineers covers it

How deep it goes
Defines component responsibilities and organizational value, but stops short of implementation commands, configurations, or detailed system internals.
Examples
Names data warehouses, compute platforms, orchestration services, artifact stores, training services, serving services, and monitoring systems.
What it assumes
Assumes participation in machine learning development but reduces the need for data scientists to master DevOps and data engineering.
What you can do after
Operate a repeatable path for building, deploying, monitoring, and maintaining models with less cross-team coordination.
How it connects
Connects data engineering, DevOps, MLOps, data pipelines, workflow orchestration, model training, model serving, and monitoring.

Also explained in

Compare how 2 books explain machine learning infrastructure →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Designing Deep Learning Systems: A guide for software engineers. The section links point to the parts of the book it draws on.