[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-mlops-is-not-optional-for-production-ml-en":3,"article-related-mlops-is-not-optional-for-production-ml-en":30,"series-industry-300b42e9-6fea-45f4-bc4a-664cb7244ade":83},{"id":4,"slug":5,"title":6,"content":7,"summary":8,"source":9,"source_url":10,"author":11,"image_url":12,"cover_image":12,"category":13,"language":14,"translated_content":11,"related_article_id":15,"keywords":16,"key_takeaways":22,"views":26,"created_at":27,"published_at":28,"topic_cluster_id":29},"300b42e9-6fea-45f4-bc4a-664cb7244ade","mlops-is-not-optional-for-production-ml-en","MLOps is not optional if you want ML in production","\u003Cp data-speakable=\"summary\">\u003Ca href=\"\u002Ftag\u002Fmlops\">MLOps\u003C\u002Fa> is the operational layer that turns \u003Ca href=\"\u002Ftag\u002Fmachine-learning\">machine learning\u003C\u002Fa> models into reliable production systems.\u003C\u002Fp>\u003Cp>MLOps is not a nice-to-have add-on to machine learning; it is the difference between a demo and a system that survives contact with production.\u003C\u002Fp>\u003Cp>Thomas Nys puts the failure mode plainly: most ML projects never make it into production, and the blocker is usually not model quality. It is the inability to reproduce training environments, serve predictions at the right latency, monitor degradation, update safely, and govern the whole lifecycle. That is why a notebook success does not count as business value.\u003C\u002Fp>\u003Ch2>Production is where ML stops behaving like software\u003C\u002Fh2>\u003Cp>Traditional software is deterministic. If the code is the same, the behavior is the same. ML systems are not like that. The model, the data, and the features all shape the output, which means a passing test in development does not guarantee a stable result in production. That is the core reason DevOps alone fails here.\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781543872489-ll37.png\" alt=\"MLOps is not optional if you want ML in production\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>One concrete example is training-serving skew. A feature calculated one way during training and another way in production produces a model that looks correct on paper and fails in the real world. This is not a theoretical edge case. It is a common cause of drift, bad predictions, and hard-to-debug incidents. MLOps exists to prevent that gap from opening in the first place.\u003C\u002Fp>\u003Ch2>Reliability matters more than model accuracy\u003C\u002Fh2>\u003Cp>The article’s strongest claim is also the most operationally important: building the model is only a slice of the work. Nys argues that model creation is about 20% of the effort while operating it is the other 80%. That ratio matches how production systems behave. The expensive part is not the first successful run; it is keeping the system healthy after data changes, traffic grows, or business rules shift.\u003C\u002Fp>\u003Cp>Monitoring makes that reality visible. A model can maintain good offline metrics and still fail because the input distribution changed after a product launch, a market shift, or a new user cohort. Without data drift, concept drift, and infrastructure monitoring, the team notices only after revenue, risk, or customer experience has already taken the hit. MLOps makes degradation observable before it becomes a business incident.\u003C\u002Fp>\u003Ch2>Reproducibility and governance are not bureaucracy\u003C\u002Fh2>\u003Cp>Another reason MLOps matters is that production ML needs traceability. If a model underperforms, teams must know which version is deployed, what data trained it, what parameters were used, and what performance it had in validation. That is not paperwork for its own sake. It is the only way to rollback safely, compare versions, and satisfy compliance requirements in regulated environments.\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781543874450-u005.png\" alt=\"MLOps is not optional if you want ML in production\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>The same applies to retraining. Manual notebook reruns do not create dependable systems. Automated pipelines, pinned dependencies, experiment tracking, and model registries do. A scheduled or drift-triggered retraining process is only useful when it is tested, approved, and reversible. In other words, governance is what makes ML change safe enough to ship repeatedly.\u003C\u002Fp>\u003Ch2>The counter-argument\u003C\u002Fh2>\u003Cp>The best objection is practical: many organizations do not need a full MLOps stack. If the model is experimental, low stakes, or rarely updated, heavy infrastructure can slow teams down and waste money. For a small team, managed services and minimal automation are often the right first step. The article itself acknowledges this by recommending incremental adoption and warning against trying to build everything at once.\u003C\u002Fp>\u003Cp>There is also a real cost to overengineering. Feature stores, orchestration platforms, model registries, and custom monitoring can become a pile of tools that no one owns. If the use case is not business critical, that complexity is unjustified.\u003C\u002Fp>\u003Cp>That objection is correct about scope, not about principle. The answer is not to skip MLOps; it is to right-size it. Even a modest setup needs experiment tracking, versioning, and basic monitoring. Once a model affects revenue, risk, or customer experience, operational discipline stops being overhead and becomes the minimum cost of using ML responsibly.\u003C\u002Fp>\u003Ch2>What to do with this\u003C\u002Fh2>\u003Cp>If you are an engineer, start with experiment tracking, model versioning, and a simple deployment path before chasing advanced tooling. If you are a PM, treat monitoring and rollback as product requirements, not implementation details. If you are a founder, budget for the unglamorous work: data quality, ownership, governance, and maintenance. ML that cannot be operated is not a product; it is a prototype with a dashboard.\u003C\u002Fp>","MLOps is the operational layer that turns machine learning models into reliable production systems.","thomasnys.com","https:\u002F\u002Fthomasnys.com\u002Fwhat-is-mlops\u002F",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781543872489-ll37.png","industry","en","63358330-a783-4029-a837-53fa4b33fd47",[17,18,19,20,21],"MLOps","machine learning production","model monitoring","feature store","model versioning",[23,24,25],"MLOps is the operational layer that makes ML reliable in production.","Monitoring, versioning, and retraining are core production requirements, not extras.","Right-sized MLOps beats ad hoc notebooks for any model with real business impact.",0,"2026-06-15T17:17:22.508357+00:00","2026-06-15T17:17:22.505+00:00","6843714e-4c75-4428-9401-280186600b53",{"tags":31,"relatedLang":42,"relatedPosts":46},[32,34,36,38,40],{"name":20,"slug":33},"feature-store",{"name":19,"slug":35},"model-monitoring",{"name":17,"slug":37},"mlops",{"name":18,"slug":39},"machine-learning-production",{"name":21,"slug":41},"model-versioning",{"id":15,"slug":43,"title":44,"language":45},"mlops-is-not-optional-for-production-ml-zh","想把 ML 用到生產環境，MLOps 不是選配","zh",[47,53,59,65,71,77],{"id":48,"slug":49,"title":50,"cover_image":51,"image_url":51,"created_at":52,"category":13},"4f5b9071-650c-4376-80f2-1c33484d83cb","kalshi-adds-solana-perpetual-futures-after-xrp-en","Kalshi adds Solana perpetual futures after XRP","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781553769118-d4w7.png","2026-06-15T20:02:30.737686+00:00",{"id":54,"slug":55,"title":56,"cover_image":57,"image_url":57,"created_at":58,"category":13},"8c10e73a-b4e7-444b-9a70-421823b16755","mlops-zoomcamp-path-to-production-ml-en","MLOps Zoomcamp maps the path to production ML","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781542983207-pzyb.png","2026-06-15T17:02:28.963068+00:00",{"id":60,"slug":61,"title":62,"cover_image":63,"image_url":63,"created_at":64,"category":13},"75ec77eb-424e-474f-813f-bb387da904e9","cloudflare-too-expensive-after-share-price-surge-en","Cloudflare Is Too Expensive to Buy After the Surge","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781539368511-x1fq.png","2026-06-15T16:02:19.031847+00:00",{"id":66,"slug":67,"title":68,"cover_image":69,"image_url":69,"created_at":70,"category":13},"f49d58f8-0bd5-4442-9bdb-b0ca12e97986","turbovec-cuts-10m-vector-ram-to-4gb-en","TurboVec cuts 10M-vector RAM to 4GB","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781528566106-frfj.png","2026-06-15T13:02:23.344662+00:00",{"id":72,"slug":73,"title":74,"cover_image":75,"image_url":75,"created_at":76,"category":13},"0423587b-197e-41cc-99d3-6197263e6874","midjourney-v8-1-default-model-update-en","Midjourney V8.1 now ships as default model","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781515062253-2i5e.png","2026-06-15T09:17:19.17797+00:00",{"id":78,"slug":79,"title":80,"cover_image":81,"image_url":81,"created_at":82,"category":13},"f862c145-269f-4ef4-aa12-44207a7475aa","midjourney-free-methods-vs-paid-access-en","Midjourney Free Methods vs Paid Access","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781514188185-dk6r.png","2026-06-15T09:02:35.461188+00:00",[84,89,94,99,104,109,114,119,124,129],{"id":85,"slug":86,"title":87,"created_at":88},"d35a1bd9-e709-412e-a2df-392df1dc572a","ai-impact-2026-developments-market-en","AI's Impact in 2026: Key Developments and Market Shifts","2026-03-25T16:20:33.205823+00:00",{"id":90,"slug":91,"title":92,"created_at":93},"5ed27921-5fd6-492e-8c59-78393bf37710","trumps-ai-legislative-framework-en","Trump's AI Legislative Framework: What's Inside?","2026-03-25T16:22:20.005325+00:00",{"id":95,"slug":96,"title":97,"created_at":98},"e454a642-f03c-4794-b185-5f651aebbaca","nvidia-gtc-2026-key-highlights-innovations-en","NVIDIA GTC 2026: Key Highlights and Innovations","2026-03-25T16:22:47.882615+00:00",{"id":100,"slug":101,"title":102,"created_at":103},"0ebb5b16-774a-4922-945d-5f2ce1df5a6d","claude-usage-diversifies-learning-curves-en","Claude Usage Diversifies, Learning Curves Emerge","2026-03-25T16:25:50.770376+00:00",{"id":105,"slug":106,"title":107,"created_at":108},"69934e86-2fc5-4280-8223-7b917a48ace8","openclaw-ai-commoditization-concerns-en","OpenClaw's Rise Raises Concerns of AI Model Commoditization","2026-03-25T16:26:30.582047+00:00",{"id":110,"slug":111,"title":112,"created_at":113},"b4b2575b-2ac8-46b2-b90e-ab1d7c060797","google-gemini-ai-rollout-2026-en","Google's Gemini AI Rollout Extended to 2026","2026-03-25T16:28:14.808842+00:00",{"id":115,"slug":116,"title":117,"created_at":118},"6e18bc65-42ae-4ad0-b564-67d7f66b979e","meta-llama4-fabricated-results-scandal-en","Meta's Llama 4 Scandal: Fabricated AI Test Results Unveiled","2026-03-25T16:29:15.482836+00:00",{"id":120,"slug":121,"title":122,"created_at":123},"bf888e9d-08be-4f47-996c-7b24b5ab3500","accenture-mistral-ai-deployment-en","Accenture and Mistral AI Team Up for AI Deployment","2026-03-25T16:31:01.894655+00:00",{"id":125,"slug":126,"title":127,"created_at":128},"5382b536-fad2-49c6-ac85-9eb2bae49f35","mistral-ai-high-stakes-2026-en","Mistral AI: Facing High Stakes in 2026","2026-03-25T16:31:39.941974+00:00",{"id":130,"slug":131,"title":132,"created_at":133},"9da3d2d6-b669-4971-ba1d-17fdb3548ed5","cursors-meteoric-rise-pressures-en","Cursor's Meteoric Rise Faces Industry Pressures","2026-03-25T16:32:21.899217+00:00"]