知识卡片
独立运行按需扩容
不同业务服务的流量、CPU和内存需求不相同。将商品浏览与用户注册分开后,可以分别分配实例与资源,避免为一个热点把整个应用一起扩容。服务边界应结合实际负载和业务责任,而非预设所有功能等比例增长。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Monoliths and Microservices · 查看原书依据
Not all parts of an application receive the same amount of traffic. In the e-commerce application, the UserService will handle user registration and other aspects of the customer signup flow, while the ProductCatalogService will serve displaying those customers the catalog of goods the website sells. The number of users registering themselves will often be less than the number of users browsing the catalog of goods.
参考来源
- 位置:《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)
- 结论依据:原文以服务职责、依赖或运行情境展开本卡主题;本卡保留其作用条件与代价,不把局部优势推广为无条件保证。
- 原始内容:Not all parts of an application receive the same amount of traffic. In the e-commerce application, the UserService will handle user registration and other aspects of the customer signup flow, while the ProductCatalogService will serve displaying those customers the catalog of goods the website sells. The number of users registering themselves will often be less than the number of users browsing the catalog of goods.