<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Industrial Practice on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/industrial-practice/</link><description>Recent content in Industrial Practice on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 15 Jan 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/industrial-practice/index.xml" rel="self" type="application/rss+xml"/><item><title>Recommendation Systems (16): Industrial Architecture and Best Practices</title><link>https://www.chenk.top/en/recommendation-systems/16-industrial-practice/</link><pubDate>Thu, 15 Jan 2026 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/recommendation-systems/16-industrial-practice/</guid><description>&lt;blockquote>
&lt;p>The hardest part of a production recommendation system isn&amp;rsquo;t the model. It&amp;rsquo;s the &lt;strong>system around the model&lt;/strong>: the feature store that prevents training/serving skew, the canary deployment that catches regressions before they hit 100M users, and the orchestration that meets a 100ms p95 latency budget while running four ML models in sequence. This final article describes the architecture that every major tech company has converged on — and the trade-offs within each layer.&lt;/p></description></item></channel></rss>