轮毂，辐条和ESB之间的区别 [英] Difference between Hub, Spoke and ESB

问题描述

我知道已经孤单对这个问题问得很好，但它并没有真正回答我要找的。

I know theres already a good question on this, but it doesn't really answer what I'm looking for.

据我了解：

1.both用作应用程序之间的中央联络点结果
2.both可以使用的服务/应用程序之间的路由/调解/改造等。

1.both are used as a central focal point between applications
2.both can use routing/mediation/transformation etc. between services/apps

但唯一不同的我真的可以看到的是，中心辐射通常有许多不同的格式进入轮毂（SOAP / REST / XML / JSON ...），而ESB通常具有标准格式（通常只是SOAP）。

But the only difference i can really see is that hub and spoke typically have many different formats entering the hub(SOAP/REST/XML/JSON...) while ESB typically has a standard format(Usually just SOAP.)

我还留着读取枢纽和辐条引入单一故障点相比，ESB。所以是物理部署在这里的区别？当一个集线器有每一个可能的端点，作为ESB具有端点部署在多个集线器？因此，一个ESB只是多个集线器（为更好的话想）？

Also I keep reading that hub and spoke introduces a single point of failure compared to an ESB. So is the physical deployment the difference here? Where a hub has every possible endpoint and as ESB has endpoints deployed across multiple hubs? So an ESB is just multiple hubs(for want of better words)?

谁能帮助清除此为我？

推荐答案

有没有确切的答案在这里，因为你可以说说ESB作为一个具体的设计模式，或有关软件集成工具和SOA演进的话语。

There is no exact answer here, since you can talk about ESB as a specific design pattern, or as the discourse about the evolution of software integration tools and SOA.

ESB作为一种设计模式意味着你使用的是公交车，在这里客户可以很容易地插入和退出管理不同的服务之间的通信。这通常是通过迫使他们使用标准的数据格式和协议完成的，而具有中心和分支您可以使用自定义连接器和数据转换为每个客户端。这限制了你可能有运行多个集成问题的数量，但你可能仍然有一个单一的故障点ESB。

ESB as a design pattern means that you manage communication between different services using a bus where clients can easily plug in and out. This is usually done by forcing them to use standard data formats and protocols, whereas with Hub and Spoke you might use custom connectors and data transformations for each client. This limits the number of problems you may have with running multiple integrations, but you may still have a single point of failure in ESB.

ESB作为一个话语（或营销术语）是一个比较复杂的问题，人们争论什么是真正的ESB。有人说，你需要有一个模块化架构，您可以选择您部署的组件，也需要能够在不同的机器组件分发到允许扩展和容错能力。在极端情况下的定义，你需要甚至部署数据变压器分布式服务。

ESB as a discourse (or marketing term) is a more complex issue, where people argue over what is "True ESB". Some people say you need to have a modular architecture where you can select which components you deploy, or you need to be able to distribute the components across different machines to allow scaling and fault tolerance. In the extreme definition you would need to deploy even your data transformers as distributed services.

这篇关于轮毂，辐条和ESB之间的区别的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！