知识卡片
单体架构的适用范围
单体把主要功能作为一个应用统一开发和部署。范围清晰、规模适中的产品因此获得较低的集成与运行成本;当代码与团队持续增长,共享状态和依赖才可能使变化更难隔离。不能仅因单体这个名称就推断它设计混乱或无法扩展。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Monoliths and Microservices · 查看原书依据
Consider an e-commerce platform like an online bookstore. In its early days, this bookstore operates as a single application. Everything from managing inventory, processing orders, handling customer reviews, and updating the website's front end is part of a single, cohesive codebase.
参考来源
- 位置:《Building Distributed Systems Designing scalable architectures with microservices, event-driven patterns, and robust deployment…》第02章《Monoliths and Microservices》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Distributed Systems Designing scalable architectures with microservices, event-driven patterns, and robust deployment…/_epub-src/OPS/ch02.xhtml)
- 结论依据:原文以服务职责、依赖或运行情境展开本卡主题;本卡保留其作用条件与代价,不把局部优势推广为无条件保证。
- 原始内容:Consider an e-commerce platform like an online bookstore. In its early days, this bookstore operates as a single application. Everything from managing inventory, processing orders, handling customer reviews, and updating the website's front end is part of a single, cohesive codebase.