The issue of service granularity has been discussed widely in the industry (see Resources).
服务粒度问题已经在业界被广泛地讨论（请参阅参考资料）。
The right level of service granularity would help minimize the proliferation of services that are too fine-grained.
恰当服务粒度水平将帮助尽可能减少过分细粒度服务的增加。
Indeed, the Service granularity matrix serves as just another tool in the belt of the effective enterprise architect.
这份服务粒度表格仅仅是一位高效的企业架构师腰带上挂着的又一把工具。
A large number of services, each containing a single operation or small number of operations, indicates inappropriate service granularity.
仅包含单个操作或少量操作的大部分服务都表明服务粒度不恰当。
Conversely, a very small number of services (or a single service) containing a large number of operations likewise indicates inappropriate service granularity.
反过来，采用很少的服务(或者单个服务)来包含大量操作也同样表明服务粒度不恰当。
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 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.
在任何特定情况下都可以处理该问题的一个实用方法就是，确认、特征化以及对可用的不同服务粒度级别进行命名。
Having established that we need to be thoughtful when determining service granularity, what considerations apply in deciding which operations should constitute a service?
既然认识到了在确定服务粒度时需要考虑周全，那么在确定哪些操作应组成服务时有什么注意事项呢？
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.
我们认为，服务粒度的两个极端——提供仅有几个方法的很多服务，或数十或数百个操作均集中在几个服务中——都将对易用性造成影响。
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.
实现 SOA的方法有两个方面应该在早期确定：对服务的内部或外部访问的提供，和一个解决服务粒度的方法。
This requirement usually manifests itself in low granularity of data service interfaces.
这些需求通常反映在数据服务接口的低粒度上。
In this discussion of service design we consider the granularity of the services themselves, that is, the number of operations a service should have.
在本文的服务设计讨论中，我们考虑的是服务本身的粒度，即服务应该包含的操作数量。
Let's use an example to better understand how decisions about service interface granularity should be made.
让我们通过一个例子来更好地了解应该如何做出关于服务接口粒度的决策。
A fundamental difference between service operations and object methods is that service operations have a much larger granularity.
服务操作与对象的方法之间的根本不同在于服务操作具有相当大的粒度。
A service designer must decide on the granularity of service contracts in terms of operation signatures for request and response message parameters.
服务设计者必须根据操作签名中的请求和响应消息参数来决定服务契约的粒度。
The granularity of the project is important: smaller projects should use service adaptors and service proxies to connect to legacy functionality, or functionality not SOA-enabled.
项目的粒度非常重要：较小的项目应该使用服务适配器和服务代理来连接遗留的功能或者不支持 SOA 的功能。
As long as service interfaces are explicitly defined and of appropriate granularity, EAI middleware can ensure that the interoperability and location independence principles of SOA are met.
只要服务接口已经明确定义并有合适的粒度，EAI中间件就能确保满足soa的互操作性和位置无关性原则。
Second, AIX breaks down its versioning into four levels of granularity: version, release, technology level (formerly maintenance level), and service pack.
第二，AIX 把版本分为四个粒度级：版本、发布版、技术级别（以前称为维护级别）和服务包。
This approach leads to decreasing of the service methods granularity and diminish business meaning of the service methods.
这个方法导致服务方法粒度的下降，抹杀了服务方法的业务意义。
Thus, determining the level of granularity in what to expose as a service and how to expose it is a key job function of this role.
因此，确定作为服务公开的粒度级别以及如何进行公开是此角色的主要工作职能。
If business users are the ones using the services, they can provide useful feedback on the granularity of the information provided by the service.
如果业务用户是使用服务的用户，则可以提供关于服务所提供的信息的粒度的有用反馈。
The list below covers aspects of latency, distributability, scalability, footprint, and qualities of service to the extent that these attributes can be used to distinguish granularity.
下面的列表讨论了服务的延迟、可分布性、可伸缩性、占用空间和质量的内容，以便使用这些属性来区分粒度。
Additionally, the service design needs to ensure the business applicability of the exposed services, and needs to be defined at the correct level of granularity.
此外，服务设计需要确保所提供服务的业务适用性，并且需要在正确的粒度级别进行定义。
At each level of granularity, it is important that a service definition encapsulates its function in such a way that it is reusable.
在每个粒度级别上，服务定义以可复用的方式封装其功能是很重要的。
A set of services at a certain granularity level can be choreographed, and the result would be another more coarse-grained service.
某一粒度级别的一组服务可以通过编排，形成另一个具有较粗粒度的服务。
Then make the first history service request for daily granularity with a duration of yearly.
然后确保第一个历史记录服务请求持续时间为一年的期间内粒度为每天的数据。
Coarse granularity: granularity with services refers to the extent of functionality that a service presents publicly.
粗粒度：服务的粒度是指服务公开给出的功能范围。
You must determine the appropriate granularity of what becomes a service in your SOA.
必须确定SOA中服务的恰当粒度。
Probably the most difficult portion in developing a Services Oriented Architecture lies in determining what the right level of granularity of a Web Service should be.
在开发面向服务的体系结构的过程中可能最困难的部分在于，决定Web服务的粒度的正确级别应该是什么。
Increase flexibility, granularity, and maintainability of Web service interfaces.
提高Web服务接口的灵活性、粒度和易维护性。
应用推荐