Overview

Databricks’ second edition (2023) of the MLOps reference guide covers the full ML lifecycle — from development through staging to production — with updated content on Unity Catalog, Model Serving, and Lakehouse Monitoring. The guide provides a reference architecture and design decision framework for operationalizing ML at scale.

Key Frameworks

MLOps = ModelOps + DataOps + DevOps: The unified discipline treating model lifecycle, data pipelines, and deployment infrastructure as interconnected concerns.

Guiding Principles:

  • Models are code — version, test, and deploy them like software
  • Reproducibility requires deterministic environments and data versioning
  • Monitoring is not optional — model performance degrades over time

ML Deployment Patterns:

  • Batch inference for offline scoring
  • Real-time serving for latency-sensitive applications
  • Streaming inference for continuous data pipelines

Reference Architecture: Multi-environment (dev/staging/prod) design with Unity Catalog for data governance, Model Serving for deployment, and Lakehouse Monitoring for observability.

Chapter Themes

ChapterFocus
V1 RecapCore MLOps principles and deployment patterns
What’s NewUnity Catalog, Model Serving, Lakehouse Monitoring
Design DecisionsAsset organization, pre-deployment testing, real-time deployment
Reference ArchitectureMulti-environment view, development through production

Actionable Takeaways

  • Treat ML artifacts (models, features, data) as first-class versioned assets in a unified catalog
  • Implement pre-deployment testing gates — not just accuracy, but latency, throughput, and data drift
  • Design for the full lifecycle from day one — monitoring and retraining pipelines are not afterthoughts
  • Use the lakehouse pattern to unify data engineering and ML engineering on a single platform