IngramChen 積分 2 編輯於

文中指出五大迷思:

  • 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 應該是沿用原本組織的部門去區分才是 (大方向…),而不是上述的一些錯誤理由。

這是文章的子討論串,你可以回到上層查看所有討論和文章