如何处理所有这些中间件？
我的组织最近一直在思考我们是否应该将不同的中间件产品/概念合并到我们的应用程序中的问题。我们正在研究的产品包括 Pegasystems、Oracle BPM / BPEL、BizTalk、Fair Isaac Blaze 等。
但我很难掌握这一切。在我继续评估这些不同产品的有用性（积极或消极）之前，我试图了解这个领域的所有不同概念。我对 BPM、ESB、SOA、CEP、WF、BRE、ERP 等字母汤感到不知所措。有些产品似乎涵盖了其中一个或多个方面，其他产品则专注于其中一个方面。这些术语似乎都非常含糊并且相互混淆。
是否有一个很好的资源来处理所有这些不同的中间件概念/模式？一本书？一个网站？有一篇文章总结得很好吗？如果有一个资源可以将各种流行产品映射到它们所解决的模式，那就加分了。
谢谢，
贾斯汀
My organization has recently been wrestling the question of whether we should be incorporating different middleware products / concepts into our applications. Products we are looking at are things like Pegasystems, Oracle BPM / BPEL, BizTalk, Fair Isaac Blaze, etc., etc., etc.
But I'm having a hard time getting a handle on all this. Before I go forward with evaluating the usefulness (positive or negative) of these different products I'm trying to get an understanding of all the different concepts in this space. I'm overwhelmed with an alphabet soup of BPM, ESB, SOA, CEP, WF, BRE, ERP, etc. Some products seem to cover one or more of those aspects, others focus on doing one. The terms all seem very ambiguous and conflated with each other.
Is there a good resource out there to get a handle on all these different middleware concepts / patterns? A book? A website? An article that sums it up well? Bonus points if there is a resource that maps the various popular products into which pattern(s) they address.
Thanks,
~ Justin
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
在过去的 3-4 年里，我一直在写关于您提到的主题的博客 (http://www.UdiDahan.com) 以及编写我自己的轻量级 ESB (http://www.NServiceBus.com) 以及许多年在这个领域工作和咨询。我得出的主要结论是，需要强大的业务分析和与技术无关的架构 - 没有任何工具或技术本身可以防止混乱。
有一本《企业集成模式》一书，它提供了所涉及的技术模式的良好目录，但没有涉及必要的业务分析。我发现价值网络（http://en.wikipedia.org/wiki/Value_network_analysis ）可以用作识别业务边界的良好开端，然后可以将 IT 边界与其对齐，从而带来 SOA 的好处，并且跨这些边界使用 ESB 是合理的。
CEP、WF 和 BRE 应在边界内使用，而不是跨越边界。
ERP 包往往会跨越边界，因此应该零碎地集成到所提到的边界中 - DDD 反腐败层可用于将自定义逻辑与这些应用程序隔离。
希望有帮助。
I've spent the last 3-4 years blogging on the topics you mentioned (http://www.UdiDahan.com) as well as writing my own lightweight ESB (http://www.NServiceBus.com) and many more years working and consulting in this space. The main conclusion that I've come to is that strong business analysis and technologically-agnostic architecture is needed - no tool or technology can prevent a mess by itself.
There is the Enterprise Integration Patterns book which provides a good catalog of the technical patterns involved but doesn't touch on the necessary business analysis. I've found that Value Networks (http://en.wikipedia.org/wiki/Value_network_analysis) can be used as a good start for identifying business boundaries to which IT boundaries can be then aligned, resulting in the benefits of SOA, and the use of an ESB across those boundaries is justified.
CEP, WF, and BRE should be used within a boundary and not across them.
ERP packages tend to cross boundaries and, as such, should be integrated piecemeal into the boundaries mentioned - DDD anti-corruption layers can be used to insulate custom logic from those apps.
Hope that helps.
IBM 和 Oracle 拥有 SOA 认证。由于他们是市场的领导者（Gartner 魔力象限），我会了解他们如何定义 SOA 和 ESB（以及支持 SOA 所需的方法和组件，如治理、注册表等）。它将为您提供您正在寻找的高级概述以及“所有这些中间件”正在尝试解决的用例。
IBM and Oracle have SOA certifications. Since they're the leaders in the marketplace (Gartner Magic Quadrant), I would read about how they define SOA and ESBs (along with methodology and the components needed to support SOA like Governance, Registry, etc etc). It'll give you the high level overview that you're looking for and the use cases "all this middleware" is trying to solve.