决定哪些内容是或者不是体系结构中的一部分，看上去有明确的界线，但是这种分离是很重要的，它允许我们管理软件模型的复杂性。
It may seem like a fine line to decide what is and what is not part of the architecture, but this separation is important in allowing us to manage the complexity of the software models.
例如，销售部门现在可以根据实际使用量添加新用户，而不会增加复杂性和采购新硬件、软件和管理资源的成本。
For example, the sales department is now able to add new users based on actual usage without increasing the complexity and cost of procuring new hardware, software, and administrative resources.
这是一个极大的变革，它让软件开发人员能够从管理应用程序伸缩性的固有复杂性中解脱出来，让他们能将精力集中于应用程序的编写。
This is a remarkable game changer that lets software developers ignore the inherent complexity of managing the scalability of an application, and lets them focus on writing applications.
应用推荐