如何掌控複雜的雲端成本

{"type":"doc","content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"本文要點："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"雲提供商的複雜定價策略讓用戶在選擇服務時很容易陷入困惑，並且缺乏準確透明的賬單常常會導致用戶預算偏離預期。"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"雲端預算管理的責任不清是造成資源超支和利用率不足的一大原因所在。預算管理需要與交付一樣成爲項目生命週期的一部分，並且團隊需要以全新的方式協作，以瞭解需求並確定成本管理的優先級。"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"團隊可以通過兩種實用的方法來管理雲端成本並節省資金：實施一致、全面的標記流程，或使用某種可提供成本可見性和精確拆解的第三方產品。"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"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":"當團隊在雲中啓動一個新項目時，開發人員和交付團隊往往不會優先考慮預算管理的事宜。項目流程通常是這樣展開的：CFO確定並監督總體預算。產品負責人確定了項目的上線日期，然後努力確保所有人都跟上節奏。在爲這個新項目配置資源之前，人們並不會按每月預算或總體雲託管成本預期來體現成本，能見到的只有交付時間表。開發人員需要資源，運營人員則忙於嘗試迭代並滿足前者的需求，同時還要保證安全性。最緊迫的優先事項是在截止日期之前交付安全的應用程序，而不是試圖瞭解令人困惑又複雜的雲服務定價和利用率。"}]},{"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":"到2020年底，"},{"type":"link","attrs":{"href":"https:\/\/hostingtribunal.com\/blog\/cloud-computing-trends\/#gref","title":"","type":null},"content":[{"type":"text","text":"雲端項目預計將佔企業所有技術支出的70％"}]},{"type":"text","text":"。因此，隨着公司支出的增長，組織越來越需要妥善處理混亂的雲端開支，並奪回預算的控制權以優化成本。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"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":"這是一個同雲計算一樣古老的故事：頭部雲服務提供商（AWS、Microsoft Azure和GCP）的定價模型並不像本地部署那麼簡單。結果，很多組織試圖在迷霧中尋找方向時會浪費時間、預算，並錯過潛在的成本節約機會。今年《"},{"type":"link","attrs":{"href":"https:\/\/www.flexera.com\/blog\/industry-trends\/trend-of-cloud-computing-2020\/","title":"","type":null},"content":[{"type":"text","text":"雲狀況報告"}]},{"type":"text","text":"》的受訪者估計，企業在雲計算上將超支23％，同時還會浪費雲端總支出的30％。"}]},{"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":"雲提供商並沒有爲你提供原有基礎設施計費方案的簡單1：1映射。他們的重點是簡化將IT遷移到他們的環境中的過程，並提供這一過程所需的所有服務。"}]},{"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":"以AWS Lambda爲例。假設你有一個使用Cloudfront CDN的Web應用程序。當用戶與應用程序交互時，它會通過一個API網關觸發一個HTTP請求，而這個API網關會調用一個Lambda函數，該函數會獲取數據並將其存儲在DynamoDB中。"}]},{"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":"這裏的需求看起來很簡單，但你現在其實在使用四個AWS雲服務：用於緩存的CloudFront CDN，用於路由HTTP請求的API Gateway，用於執行和處理請求的Lambda以及用於根據用戶請求存儲數據的DynamoDB。每一種服務都有自己的定價結構，並混有一些免費套餐。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"numberedlist","attrs":{"start":1,"normalizeStart":1},"content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":1,"align":null,"origin":null},"content":[{"type":"text","text":"CloudFront每月免費提供50GB數據傳輸和2,000,000個HTTP請求，免費期一年，但隨後收取的數據費用會因數據層所在的各個區域，以及各個區域的HTTP請求的定價而異，無效請求的定價爲每個無效路徑請求0.005USD，此外還有每10,000個請求每字段級別加密的定價、每1,000,000個實時日誌請求的定價，等等。"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"blockquote","content":[{"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":"numberedlist","attrs":{"start":2,"normalizeStart":2},"content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":2,"align":null,"origin":null},"content":[{"type":"text","text":"API網關的定價也有免費套餐，包含1M RESTful API請求、1M HTTP API調用、1M消息和750k連接分鐘數。此外，每百萬次API調用有一些根據調用次數區分的區間定價；如果你決定按每個緩存內存分配的大小開始緩存，那麼還會有按緩存次數計算的定價；十億次以內的消息傳輸是一個價格，按照每百萬次傳輸計算，還有一個每百萬連接分數的0.25倍費用。"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"blockquote","content":[{"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":"numberedlist","attrs":{"start":3,"normalizeStart":3},"content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":3,"align":null,"origin":null},"content":[{"type":"text","text":"Lambda定價因地區而異，但每百萬請求有一個價格，還有一個每GB秒鐘的持續時間成本。持續時間成本取決於你爲函數分配的內存量，每100ms的每個內存段的持續時間成本各不相同。然後還有額外的，用來提高速度的併發能力收費，在配置期間的併發數量方面也存在成本。除此之外，你可能會在你所在地區以外進行數據傳輸，這屬於EC2數據的標準數據傳輸費率範圍（這又是一套完全獨立的定價結構）。"}]}]}]},{"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":"我可以繼續講一講DynamoDB，但我覺得上面這些已經足夠說明問題了！"}]},{"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":"heading","attrs":{"align":null,"level":3},"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":"在多個雲服務之間貨比三家是很難的，因爲每家提供商都使用了不一樣的術語。Azure的“虛擬機”在GCP上稱爲“虛擬機實例”，在AWS上僅稱爲“實例”。一組實例在Amazon和GCP上均稱爲“自動縮放組”，但在Azure上稱爲“縮放集”。由於命名約定不同，甚至搞清楚你要購買的究竟是什麼產品，以及是否還有可替代的競品服務都是很難的事情。"}]},{"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":"就像上面那個只使用了Lambda的簡單Web應用程序的例子那樣，人們需要花費大量時間才能對比一個Web應用程序託管在一個雲中與另一個雲中的花費。我們需要掌握每個雲提供商的技術知識，才能搞清楚這個服務商的服務和另一家提供商的服務如何對應，要對比定價就更困難了。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"heading","attrs":{"align":null,"level":3},"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":"雲端計價使用的是按需模型，這與本地的情況相去甚遠。在本地部署中，你可以部署很多事物並讓它們24\/7工作，卻不會增加成本（除了電費）。在雲中，一切費用都取決於你使用服務的時間，以每小時、每分鐘、每個請求、每個數量或每秒爲基準。日誌的存儲方式、你使用的數據庫，甚至是託管的國家\/地區最終都會影響你支付的費用。"}]},{"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":"link","attrs":{"href":"https:\/\/www.computerweekly.com\/ehandbook\/Hyper-Converged-Infrastructure-Key-Choices","title":"","type":null},"content":[{"type":"text","text":"Quocirca的一項研究"}]},{"type":"text","text":"，組織平均只使用了他們雲端服務器的37%能力。但從另一方面來看，雲資源是“計量”的，這意味着你只需要配置（並支付）所需的資源即可。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"heading","attrs":{"align":null,"level":3},"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":"前面提到，雲端並沒有單一的有形定價單位。你需要爲託管所需的計算和內存資源付費，但存儲、數據庫和其他組件也有收費項目。雲服務還有幾種類型：基礎架構即服務（IaaS）、平臺即服務（PaaS）、函數即服務（FaaS）、存儲即服務（STaaS）和安全即服務（SECaaS），所有這些類型的計費標準都不一樣。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"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":"根據Flexera的"},{"type":"link","attrs":{"href":"https:\/\/www.flexera.com\/blog\/industry-trends\/trend-of-cloud-computing-2020\/","title":"","type":null},"content":[{"type":"text","text":"2020年雲狀態報告"}]},{"type":"text","text":"，受訪者預計2020年企業雲支出將增加近50％，但精確預算仍然非常困難。於是，節省成本連續第四年成爲了企業雲計劃中的最優先事項。"}]},{"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":"numberedlist","attrs":{"start":1,"normalizeStart":1},"content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":1,"align":null,"origin":null},"content":[{"type":"text","text":"實施一種在設計生命週期中增加成本指標的方法，或者"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":2,"align":null,"origin":null},"content":[{"type":"text","text":"使用一種可以簡化成本數據並提高可見性的產品。"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":3,"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":"預先思考如何提高成本的透明度是很重要的。如果你要讓幾個團隊混用雲端賬戶，就不能將雲帳戶\/項目ID用作分隔點了。這意味着你將需要一種嚴格的標記方法，和一種圍繞雲服務供應的良好有形業務分類法，才能讓人們瞭解哪些成本主要來自哪些團隊。"}]},{"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":"heading","attrs":{"align":null,"level":3},"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":"開發時隨時考慮成本指標意味着效率提升措施可以融入應用程序的設計中，並且開發人員會知道在不使用某些事物時應將其關閉，或者正確地調整事物的大小。預算編制應該可以更好地塑造團隊行爲，並且每個職能部門都應發揮自己的作用，包括具備雲和運維技能的DevOps、具備應用工程技能的開發人員，以及具有遠見並瞭解預算的產品負責人\/經理。"}]},{"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":"那麼，團隊可以使用哪些技術來簡化成本節約工作呢？Github上已經針對各大雲提供商提供了一些有用的工具，這些工具使用雲提供商的函數即服務在特定時間內關閉雲資源。但諷刺的是，你得花錢運行一項服務來關閉另一項服務，才能節約雲服務支出。"}]},{"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":"如果你有了Kubernetes之類的東西，就可以在集羣中運行一些工具（例如Kube Downscaler），並允許Dev\/DevOps團隊縮減他們的應用程序，接着觸發自動縮放器以縮減實例，就可以開始節約開支了。在各大雲服務中還爲每種服務提供了針對性解決方案，例如Appvia編寫的一種使用Kubernetes關閉AWS中RDS的工具，稱爲rds-scheduler。它很像Kube Downscaler，接收Cron風格的時間參數，來指定要關閉事物的時間。"}]},{"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":"numberedlist","attrs":{"start":2,"normalizeStart":2},"content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":2,"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":"傳統上，開發人員在處理項目財務時會陷入困境，但他們具備構建技能和理解能力，能夠評估哪些地方可以節省成本。可以使用一種產品來爲你的團隊提供更高的可見性，使他們無需花費時間研究成本和標記服務。你可以使用每個項目的支出見解來代替常見的彙總視圖，以幫助優化預算並防止支出失控。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"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","marks":[{"type":"strong"}],"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","marks":[{"type":"strong"}],"text":"Jonathan Shanks"},{"type":"text","text":"是Kubernetes交付平臺"},{"type":"link","attrs":{"href":"https:\/\/www.appvia.io\/","title":"","type":null},"content":[{"type":"text","text":"Appvia"}]},{"type":"text","text":"的首席執行官和聯合創始人。他是一名DevOps專家和企業家，在研發領先的開發人員和工程師擴展和交付解決方案方面擁有近二十年的經驗。他領導着一支極富才華的工程師和開發人員團隊，致力於構建一個突破性的工具平臺，使大型組織能夠快速安全地創建創新產品和服務，並利用Kubernetes的強大功能簡化基礎架構、加快交付並降低成​​本。在加入Appvia之前，Jonathan是內政部主管兼技術主管。他的角色涉及與工程師團隊合作，爲多個數字項目提供解決方案。Jonathan率先採取了旨在振興內政部技術基礎設施方面的舉措，從而節省了大量時間和金錢。Jonathan曾在紐約泛歐證券交易所擔任Linux架構師，在Betfair擔任高級Linux工程師，從中獲得了豐富的經驗。"}]},{"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","marks":[{"type":"strong"}],"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":"link","attrs":{"href":"https:\/\/www.infoq.com\/articles\/taking-control-of-cloud-costs\/","title":"","type":null},"content":[{"type":"text","text":"Taking Control of Confusing Cloud Costs"}]}]}]}