开源项目中企业服务总线 (ESB) 的推荐框架
Java Enterprise Service Bus 的框架非常丰富（OpenESB、ServiceMix、Apache Synapse 等），新项目应该选择哪一个？ 每一种的优点和缺点是什么？ 他们为你工作得怎么样？
With an abundance of frameworks for Java Enterprise Service Bus(OpenESB, ServiceMix, Apache Synapse, ...), which one should be selected for new projects? What are the pros and cons for each one? How well have they worked for you?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
就我个人而言，我不喜欢 ESB。 您的第一步应该是拥有一个可用的服务组合，以解决您要解决的业务问题。 如果您已经很好地划分了问题，我敢打赌 ESB 没有帮助。
它们往往会成为单点故障，迫使人们在服务之外了解太多关于服务内部运作的知识（例如，管理事务的补偿操作）。
“架构师”往往喜欢它们，因为他们认为可以用工具解决问题。
不要最终创建一个令人震惊的意大利面条盒
但如果你必须这样做，我建议< a href="http://www.theserverside.com/news/thread.tss?thread_id=47868" rel="nofollow noreferrer">Spring 与 Mule。
Personally, I'm not a fan of ESB. Your first step should be to have a portfolio of services available that tile the space of the business problem you're trying to solve. If you've partitioned the problem well, I'd bet that an ESB isn't helpful.
They tend to become a single point of failure that forces too much knowledge about the inner workings of the services (e.g., compensating operations to manage transactions) outside the services.
"Architects" tend to love them because they think they can solve problems with tools.
Don't end up creating an Egregious Spaghetti Box
But if you must, I'd recommend Spring for its integration with Mule.