文中指出五大迷思:
- microservices 引導更簡潔的程式碼
but: “You don’t need to introduce a network boundary as an excuse to write better code.”
- microservices 架構下更好實作
but: “Distributed transactions are never easy.”
- microservices 更快
but: “You could gain a lot of performance in a monolith by simply applying a little extra discipline.”
- microservices 對工程師簡單
but: “A bunch of engineers working in isolated codebases leads to ‘Not my problem’ syndrome.”
- microservices scale 更好
but: “You can scale a microservice outward just as easily as you can scale a monolith.”
----
microservice 的 boundary 應該是沿用原本組織的部門去區分才是 (大方向…),而不是上述的一些錯誤理由。
IngramChen
積分 2
cloudflare 的免費用戶走 hinet 不會經過 taipei 的 edge 了
這表示台灣的用戶經過 cloudflare 大多會走 hk 或 singapore. 之前 taipei 的 edge 開了還挺高興的, 但就這麼沒了
分散式系統最難的佈署是 stateful 的 service (例如資料庫),誰來解決這個問題?container 有解決嗎?container 現在解決的問題都是 stateless。但 stateless 本來就很簡單了,多包一層 docker 皮幹嘛?