Prerender 從 AWS 搬回傳統機房的成本節省
source link: https://blog.gslin.org/archives/2022/10/03/10895/prerender-%e5%be%9e-aws-%e6%90%ac%e5%9b%9e%e5%82%b3%e7%b5%b1%e6%a9%9f%e6%88%bf%e7%9a%84%e6%88%90%e6%9c%ac%e7%af%80%e7%9c%81/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Prerender 從 AWS 搬回傳統機房的成本節省
在 Hacker News 上看到「We reduced our server costs by moving away from AWS (gitconnected.com)」這篇，原文在「How we reduced our annual server costs by 80% — from $1M to $200k — by moving away from AWS」這邊。
偶而會看到這類的報導，這次是 Prerender 這家的服務，從本來在 AWS 上的 $1m/y 降到 $200k/y (這邊都是用美金在計算)。
但好像沒提到第一次投資購買硬體花了多少錢，不過就以前的經驗上來說，把每個月非人力的 OPEX 加上 CAPEX 的各種攤提，大概會是雲端的 1/3 到 1/2 的費用。
近年來 k8s 以及各種架構愈來愈完整，很多技術也都收斂，慢慢變成業界標準了，不需要自己土砲搞一堆東西而導致產生可觀的維護成本。
從 crt.sh 上面搜尋 prerender.io 可以看到 Prerender 選擇的工具，像是在地端上面應該是用 k8s，然後有用 Sentry 以及 Redash。
這個跟當年算過的經驗類似，startup 可以先上雲端把服務做起來，雲端的擴充性對於初期的幫助會很大 (先 scale up 撐住，再改寫成可以 scale out 的版本)，而當量又大到一定程度時就反過來先問 discount，如果不滿意的話就可以規劃搬回地端。
Prerender 的量看起來超過臨界值不少，搬到地端省成本應該是蠻理所當然的...
Related
Leave a Reply
Your email address will not be published. Required fields are marked *
Comment *
Name *
Email *
Website
Notify me of follow-up comments by email.
Notify me of new posts by email.
To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Learn More)
Post navigation
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK