知识卡片
微服务羡慕症
微服务羡慕症是因追逐流行架构而迁移,却未弄清现有单体的问题与微服务自身代价。迁移后若保留共享数据库、内部库和协调发布,可能只得到分布式单体。先诊断瓶颈和团队能力,再决定边界。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
原书出处
参考来源
- 位置:《Principles of Software Architecture Modernization》第1章《What’s Wrong with Monoliths?》(源文件:`_epub-src/OPS/ch01.xhtml`,归一化正文 [45923:50093))
- 结论依据:原文明确给出反模式名称、原因与迁移后可能并存单体和多个服务的后果。
- 原始内容:Many teams pursue microservices without understanding the real issues they are solving with their monolith and the inherent drawbacks of the Microservice Architecture Style. ThoughtWorks calls this anti-pattern “Microservices Envy” ( https://www.thoughtworks.com/en-us/radar/techniques/microservice-envy ). Microservices have a lot of benefits, but they are not a silver bullet, and certainly not for all companies. Beginning in the mid-2010s, many organizations worldwide have tried to embrace a microservices architecture, with some companies like Amazon, Netflix, SoundCloud, and Spotify succeeding greatly.