没有可用于确定服务粒度的简单启发式方法。
There can be no simple heuristic for determining service granularity. Rather, we offer two examples of factors that you should consider when designing services
仅包含单个操作或少量操作的大部分服务都表明服务粒度不恰当。
A large number of services, each containing a single operation or small number of operations, indicates inappropriate service granularity.
恰当服务粒度水平将帮助尽可能减少过分细粒度服务的增加。
The right level of service granularity would help minimize the proliferation of services that are too fine-grained.
服务粒度问题已经在业界被广泛地讨论（请参阅参考资料）。
The issue of service granularity has been discussed widely in the industry (see Resources).
这份服务粒度表格仅仅是一位高效的企业架构师腰带上挂着的又一把工具。
Indeed, the Service granularity matrix serves as just another tool in the belt of the effective enterprise architect.
反过来，采用很少的服务(或者单个服务)来包含大量操作也同样表明服务粒度不恰当。
Conversely, a very small number of services (or a single service) containing a large number of operations likewise indicates inappropriate service granularity.
这表明，在选择服务粒度时，我们可能需要在多个因素间进行折衷，如可维护性、可操作性和易用性。
This indicates that in selecting service granularities we are likely to be trading off factors such as maintainability, operability and consumability.
既然认识到了在确定服务粒度时需要考虑周全，那么在确定哪些操作应组成服务时有什么注意事项呢？
Having established that we need to be thoughtful when determining service granularity, what considerations apply in deciding which operations should constitute a service?
实现 SOA的方法有两个方面应该在早期确定：对服务的内部或外部访问的提供，和一个解决服务粒度的方法。
There are two other aspects of an approach to SOA that should be established early on: the provision of internal or external access to services, and an approach to service granularity.
在任何特定情况下都可以处理该问题的一个实用方法就是，确认、特征化以及对可用的不同服务粒度级别进行命名。
A practical way to deal with this issue in any specific situation is to identify, characterize, and name the levels of service granularity which are applicable.
我们认为，服务粒度的两个极端——提供仅有几个方法的很多服务，或数十或数百个操作均集中在几个服务中——都将对易用性造成影响。
We suggest that extremes in service granularity — either many services with few methods, or few services with many tens or hundreds of operations — will tend to impede consumability.
实验表明，该架构模式很好的解决了GIS服务粒度选择的问题，同时提高了网络GIS展现层功能，增强了客户端的用户体验感。
As is shown, the model solves choice of Service granularity well and heightens function of Web GIS representation, strengthening experienced of the users.
为了尽可能进行重用和支持进行快速变更来适应市场变化，我的服务的粒度应该如何？
What granularity should my services be at so that I maximize reuse and enable quick changes to react to market forces?
让我们通过一个例子来更好地了解应该如何做出关于服务接口粒度的决策。
Let's use an example to better understand how decisions about service interface granularity should be made.
这些业务服务的粒度和分配将在设计新SOA时成为两个重要的方面。
The granularity and distribution of these business services emerge as two important factors when designing a new SOA.
自顶向下方法旨在分解业务元素（主要是业务流程和用例），然后将它们细化为适合服务的粒度。
The top-down approach is about decomposing business elements (mainly business processes and use cases) and refining them into a granularity that makes sense for services.
不同于其他IT架构，SOA要求不同的服务水平管理，原因在于服务的粒度比应用的粒度更细。
SOA requires different service level management than other it architectures, because of the finer granularity of services, compared to applications.
在本文的服务设计讨论中，我们考虑的是服务本身的粒度，即服务应该包含的操作数量。
In this discussion of service design we consider the granularity of the services themselves, that is, the number of operations a service should have.
另一种选择就是将一些相关的服务捆绑成粗粒度的服务定义，这是门面模式的变种。
Another option is the bundling of several related services into coarser-grained service definitions, which is a variation of the facade pattern.
每个粒度级别的服务都由更低粒度级别的服务或其他功能组成。
Services at each level of granularity will be composed from services, or other functions of lower levels of granularity.
这种方法还更好地遵从了面向服务架构的易组合性原则，因而可以利用现有的细粒度服务组成新的粗粒度服务。
This approach also better serves the principle of composability for service-oriented architectures, whereby new, coarser grained services can readily be composed from existing finer grained services.
这个方法导致服务方法粒度的下降，抹杀了服务方法的业务意义。
This approach leads to decreasing of the service methods granularity and diminish business meaning of the service methods.
粗粒度：服务的粒度是指服务公开给出的功能范围。
Coarse granularity: granularity with services refers to the extent of functionality that a service presents publicly.
SOA的精髓在于能够解决实际问题的松散耦合粗粒度服务。
The spirit of SOA lies in loosely coupling course-grained services that solve real business problems.
对于面向服务的设计，您可以对粒度进行考虑，如服务提供者级或服务规范级的粒度(对于前者而言，要考虑应提供多少服务)。
For service-oriented design, you can think of granularity at the service provider level (how many services are provided) or at the service specification level, for example.
必须确定SOA中服务的恰当粒度。
You must determine the appropriate granularity of what becomes a service in your SOA.
服务的粒度级别：WS响应模板模式将降低Web服务的粒度级别。
Level of granularity for services: the WS response templates patterns will reduce the granularity of Web services.
通过Internet公开许多细粒度服务将会增加攻击范围。
Exposing many fine grained services over the Internet will increase attack surface.
假如BPEL被作为一种从细粒度服务中创建粗粒度服务的集成技术来使用的话，它拥有你需要的一切特性。
If BPEL is used as an integration technology to build coarse-grained services out of smaller grained services, it has all the features you might need.
本地服务是细粒度紧密耦合服务，允许您方便地将业务功能划分为离散的组件。
Local services are fine-grained, tightly-coupled services that enable you to easily segment business function into discrete components.
应用推荐