esbs
美 
英
- 网络企业服务总线；扩展的电子稳定刹车系统；稳定系统
例句
If it turns out that 80% of their requirements are satisfied by one of these lighter-weight ESBs, they are using them.
如果结果表明某个轻便的ESB能满足他们80%的要求，他们就用。
InfoQ: In the last couple of years, ESBs have gained momentum -most of the Java vendors are marketing at least one ESB.
InfoQ：在过去的两三年中，ESB已经取得了很大的发展势头，Java厂商们至少在一种ESB上展开了营销。
Service consumers and providers access services throughout the network through one of these ESBs.
整个网络的服务使用者和提供者通过其中的一个ESB来访问服务。
Both of these ESBs are great open source integration solutions that will be a good match for a lot of integration problems.
这两个ESB都是不错的开源集成解决方案，对于大多数集成问题都能很好地解决。
Throttling and dispatching enables you to better control how service requests are addressed to target service providers by ESBs.
节流和分派使您能够通过ESB更好地控制如何将服务请求发送给目标服务提供商。
InfoQ: What are the painpoints of the current state of ESBs that motivated the need for looking for a replacement?
InfoQ：为什么要寻求替代方案，当前ESB的哪些痛点刺激了这一需求的产生？
Well-architected ESBs frequently use this pattern to map messages to a canonical message model and achieve semantic interoperability.
体系结构设计良好的ESB通常使用此模式将消息映射到规范消息模型，从而实现语义互操作性。
The Monitor pattern might be used at all of the ESBs involved in servicing a request.
处理请求所涉及的所有ESB都可能使用监视器模式。
ESBs, Service Directories and other "governance" components are often only required to manage the complexity that they themselves introduce.
ESB，服务目录以及其它的“治理”组件通常只在管理它们自身所引入的复杂性时才需要。
Regardless of the number of ESBs in the topology, each interaction involves two ESBs that are directly linked.
不管拓扑中ESB的数目有多少，每次交互都涉及两个直接连接的ESB。
InfoQ: Given the current state of open source ESBs, would you consider them to be on par with commercial alternatives?
InfoQ：鉴于开源ESB目前的状态，您认为能够把它们看作是商业产品相当的替代品么？
Business processes and transactions spanning multiple ESBs require aggregation of infrastructure services.
跨多个ESB的业务流程和事务需要聚合基础设施服务。
In the open source world, Enterprise Service Buses (ESBs), have emerged as the best infrastructure to support SOA.
在开源社区中，企业服务总线（ESB）已成为SOA的最佳基础设施。
So in short, you really should consider open source ESBs when selecting an ESB for your organization.
所以，简而言之，为你的组织选择ESB时，你真的应该考虑开源ESB。
In this article, you learned about ESBs and WS-BPEL process engines and how to decide which offers the best solution for your environment.
在本文中，您学习了ESB和WS-BPEL流程引擎，以及如何确定为您的环境提供最佳解决方案的流程引擎。
The concepts, architecture, and code explained in this article can be reused for other ESBs.
本文提供的概念、架构和代码可以在其他ESB中重用。
BPM and BPEL, which remain challenges for mainframe-centric integration solutions, are widely available on ESBs.
BPM和BPEL已经广泛运用于ESB，但以大型机为中心的集成解决方案却面临着很多挑战。
The following table compares some of the common use cases, suited to ESBs and the alternate, JEE-ish solution.
下表比较了适合于ESB、可使用JEE作为替代解决方案的常见用例。
While brokering has a clear advantage when several ESBs participate, the expected volume of service invocations is also relevant.
虽然在几个ESB共同参与时代理有着明显的优势，但预期的服务调用量也是很可观的。
However, the ESB integration patterns and concepts apply to ESBs implemented with any product.
然而，这些ESB集成模式和概念也适用于使用任何产品实现的ESB。
Currently, although it's improving, the integration between BPM engines, rules engines and the ESBs isn't perfect.
当前，尽管有所提升，但是BPM引擎，规则引擎和ESB之间的集成还不是很完美。
Additional standards are needed for asynchronous ESBs to reach their full potential.
异步ESB还需要其他标准，以便充分发挥他们的潜力。
This same technical solution is a foundation of the modern ESBs.
而这些技术解决方案是当代ESB的基础。
Customers implement their own unique ESBs based upon their requirements.
客户根据他们的需求实现其唯一的ESB。
Also on the subject of ease of use I think that open source ESBs score better than many commercial offerings.
同时，在易用性方面，我认为，开源ESB比许多商业产品表现的更好。
In this pattern a broker is employed to mediate between connected ESBs.
在此模式中，使用代理作为连接的ESB之间的中介。
Part 1. Throttling and dispatching with ESBs explains throttling and dispatching, and why they are important for ESBs.
第1部分使用ESB进行节流和分派解释了节流和分派，以及它们对ESB的重要性。
JD: The area where I think the open source ESBs could improve are in the management and in graphical support.
JD：在我看来，开源ESB需要提升的地方在于管理和图形化的支持。
ESBs have a lot of fields of application, including implementing information system-wide Service Oriented Architectures (SOAs).
ESB涉及多个应用领域，包括实现信息系统范畴的面向服务架构（SOA）。
ESBs also offer a better level of insulation than mainframe-centric SOAP stacks.
和以大型机为中心的SOAP堆栈相比，ESB还提供了一个更高层次的抽象层。
These are similar to the directly connected ESBs pattern in that multiple ESBs are connected.
它们类似于由多个ESB连接的直接连接ESB模式。
WS-BPEL has container activities, such as while loops and scopes that ESBs don't support.
WS-BPEL包含容器活动，如ESB不支持的while循环和范围。
This is what the vendors of products for building ESBs are striving to deliver.
这正是构建ESB的产品供应商努力提供的。
Most SOA efforts rely heavily on one or more ESBs as their core software infrastructure.
许多SOA项目在很大程度都依赖于将一个或多个ESB作为其核心的软件基础设施。
made harder by the lack on any industry standard benchmark for ESBs (let alone a standard definition of an ESB)
在没有任何ESB基准测试的工业标准的情况下非常困难（更不用说目前对ESB还没有一个标准的定义）
Message brokerage and the ability to bridge important transaction networks to SOAs and ESBs
消息代理以及将重要事务网络连接到SOA和ESB的能力
