如何加速軟件部署？

{"type":"doc","content":[{"type":"blockquote","content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"敏捷及其相關的實現技術，是亙貫過去十數年乃至更長時間的一個聚焦話題。儘管 CI\/CD、DevOps 業已成爲敏捷的關鍵特性，但在實際部署中還是免不了磕磕絆絆之處。每次部署都獨具其神奇之處，影響團隊在每次軟件交付中的工作量。"}]}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"爲什麼要快速部署？"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"無論系統架構是多麼的漂亮，代碼是多麼的優雅，測試套件是多麼可靠，但唯有真正地將代碼部署到生產環境中，我們的工作才能對客戶產生實質影響。代碼在部署之前，只是一些與面試問答毫無二致的智力活動。部署才能將這些知識產權轉變爲經濟活動。毫無疑問，代碼應儘快得到部署。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"然而，工程團隊卻在爲此苦苦掙扎。大量有據可查的事實表明，絕大多數的宕機事故都是由部署新更改造成的。道理的確如此，如果什麼都不改變，那麼發生事故的可能性也就大大降低。因此，部署代碼明顯是存在風險的。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"絕大多數當下流行的工程實踐，目的都是在提高軟件部署速度的同時，降低因部署加速而引發的故障風險。這些實踐大多在小型企業暢通無阻，但是當軟件或團隊規模隨着企業發展壯大而持續增長時，具體場景的重要性就愈發顯現。從開發回溯到設計和實現的逆向工程，會暴露出大量的低效之處。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"軟件的高質量快速部署是現實的目標，基於這一認可，本文將針對軟件交付過程提出流程化的觀點，識別並疏通瓶頸，提高流程效率。約束理論（Theory of Constraints，TOC）在其中的應用，意味着可對軟件的交付流程做逆向建模，進而識別瓶頸，並逐一做優化。"}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"部署會導致服務宕機"}]}]}