liveBook · Manning

Deployment

As explained in Machine Learning System Design

Deployment is the process of making a software system or model available to operate in a target production environment.

Deployment makes a software system or model available to operate in a target production environment. For ML systems, it connects predictions to real requests, scheduled jobs, monitoring, fallback behavior, and business workflows rather than stopping at model training. section 13.5.1 section 15.0

A practical deployment plan separates several responsibilities:

  • Expose predictions through a structured HTTP API with defined request and response formats. section 13.5.1
  • Monitor data drift, data quality, system health, uptime, response times, and errors. section 13.5.1
  • Switch automatically to appropriate fallbacks when prediction inputs or quality signals become unreliable. section 13.5.1
  • Treat infrastructure-wrapper releases separately from model releases, because their frequencies, dependencies, testing, rollout, and monitoring needs differ. section 13.5.1
  • Match serving effort to the business deadline: a weekly sales report may tolerate a long batch job when delivery remains on schedule. section 15.0

Supermegaretail sales predictions

A retail deployment serves predictions through an API while monitoring drift and quality. If those signals deteriorate, it activates a fallback, ultimately using recent sales patterns adjusted for expected events and holidays. The wrapper can follow standard software rollout practices, while the model is released more frequently as new data or improved modeling becomes available. section 13.5.1

GET /predictions?query=<query_string>&parameters=<parameters>&version=
<version>
&limit=<limit>&request_id=<request_id>&sku=<sku>&entity_id=<entity_id>
&group=<group_type>

Use the endpoint listing to inspect how deployment exposes prediction requests, including versioning, limits, request IDs, SKUs, entities, and groups. section 13.5.1

{
    "predictions": [
        {
            "sku": <sku_id>,
            "demand": <demand>,
            "entity": <entity_id>,
            "period": <time_period_for_demand>,
        },
        ...
    ]
}

Use the response listing to inspect the prediction payload returned to downstream systems, including demand, SKU, entity, and period fields. section 13.5.1

How Machine Learning System Design covers it

How deep it goes
Explains APIs, monitoring, fallbacks, and separate wrapper-model release cycles, but does not detail model-release procedures beyond their governing factors.
Examples
Uses retail demand prediction, weekly sales reports, HTTP prediction requests, JSON responses, drift alarms, and fallback forecasts.
What it assumes
Assumes feature infrastructure and basic software deployment practices, while distinguishing heavier deep-learning systems from lightweight models.
What you can do after
Operate/configure production prediction services with APIs, monitoring, fallbacks, release distinctions, and deadline-aware serving choices.
How it connects
Ties deployment to model serving, API design, data drift, fallback strategies, batch processing, monitoring, and release management.

Also explained in

Compare how 23 books explain deployment →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Machine Learning System Design. The section links point to the parts of the book it draws on.