Part 1. Throttling and dispatching with esbs.
第1部分使用ESB进行节流和分派。
This same technical solution is a foundation of the modern ESBs.
而这些技术解决方案是当代esb的基础。
So let's look back at the defining principles of ESBs listed earlier.
那么让我们回头来看看前面列出的esb定义原则。
ESBs offer integration facilities by providing integration components.
ESB通过供应集成组件提供了集成设施。
In this pattern a broker is employed to mediate between connected ESBs.
在此模式中，使用代理作为连接的esb之间的中介。
Customers implement their own unique ESBs based upon their requirements.
客户根据他们的需求实现其唯一的ESB。
This is what the vendors of products for building ESBs are striving to deliver.
这正是构建esb的产品供应商努力提供的。
Infoq: One of the selling points of ESBs is transparent implementation of security.
InfoQ：ESB的一个卖点是安全的透明实现。
Additional standards are needed for asynchronous ESBs to reach their full potential.
异步esb还需要其他标准，以便充分发挥他们的潜力。
WS-BPEL has container activities, such as while loops and scopes that ESBs don't support.
WS - BPEL包含容器活动，如esb不支持的while循环和范围。
ESBs don't need any of those annoying business requirements, only technology requirements.
ESB并不需要任何这样的业务需求，仅仅需要技术需求。
There are several things that are common to most ESBs. Some of the most important ones are.
大多数esb产品都有一些共性。
The concepts, architecture, and code explained in this article can be reused for other ESBs.
本文提供的概念、架构和代码可以在其他ESB中重用。
Message brokerage and the ability to bridge important transaction networks to SOAs and esbs.
消息代理以及将重要事务网络连接到soa和esb的能力。
These are similar to the directly connected ESBs pattern in that multiple ESBs are connected.
它们类似于由多个ESB连接的直接连接esb模式。
However, the ESB integration patterns and concepts apply to ESBs implemented with any product.
然而，这些ESB集成模式和概念也适用于使用任何产品实现的ESB。
Service consumers and providers access services throughout the network through one of these ESBs.
整个网络的服务使用者和提供者通过其中的一个esb来访问服务。
So in short, you really should consider open source ESBs when selecting an ESB for your organization.
所以，简而言之，为你的组织选择esb时，你真的应该考虑开源esb。
Business processes and transactions spanning multiple ESBs require aggregation of infrastructure services.
跨多个ESB的业务流程和事务需要聚合基础设施服务。
JD: the area where I think the open source ESBs could improve are in the management and in graphical support.
JD：在我看来，开源esb需要提升的地方在于管理和图形化的支持。
Also on the subject of ease of use I think that open source ESBs score better than many commercial offerings.
同时，在易用性方面，我认为，开源esb比许多商业产品表现的更好。
Regardless of the number of ESBs in the topology, each interaction involves two ESBs that are directly linked.
不管拓扑中esb的数目有多少，每次交互都涉及两个直接连接的ESB。
The following table compares some of the common use cases, suited to ESBs and the alternate, JEE-ish solution.
下表比较了适合于ESB、可使用JEE作为替代解决方案的常见用例。
Service interactions between ESBs are facilitated through a common broker that implements the bridge services.
ESB间的服务交互通过实现桥接服务的公共代理进行。
BPM and BPEL, which remain challenges for mainframe-centric integration solutions, are widely available on ESBs.
BPM和BPEL已经广泛运用于esb，但以大型机为中心的集成解决方案却面临着很多挑战。
Currently, although it's improving, the integration between BPM engines, rules engines and the ESBs isn't perfect.
当前，尽管有所提升，但是BPM引擎，规则引擎和esb之间的集成还不是很完美。
In the open source world, Enterprise Service Buses (ESBs), have emerged as the best infrastructure to support SOA.
在开源社区中，企业服务总线(esb)已成为SOA的最佳基础设施。
InfoQ: What are the painpoints of the current state of ESBs that motivated the need for looking for a replacement?
InfoQ：为什么要寻求替代方案，当前ESB的哪些痛点刺激了这一需求的产生？
Part 1. Throttling and dispatching with ESBs explains throttling and dispatching, and why they are important for ESBs.
第1部分使用ESB进行节流和分派解释了节流和分派，以及它们对esb的重要性。
InfoQ: Given the current state of open source ESBs, would you consider them to be on par with commercial alternatives?
InfoQ：鉴于开源esb目前的状态，您认为能够把它们看作是商业产品相当的替代品么？
应用推荐