请 Talend Open Studio ESB 用户反馈（相对于 jbossesb/mule/servicemix）
我正在快速回顾 ESB，到目前为止，我对 Talend ESB 感到惊讶和印象深刻。我真的很期待 Mule（最受认可的开源 ESB 之一）成为事实。
在我仅进行学术和基本测试审查后做出承诺之前，是否有任何对 Talend 有更多实践经验的人（最好是在使用另一个开源 ESB 之后）提供任何优点/缺点？
给我留下深刻印象的地方是： *EAI，准备进行集成的组件/传输的数量。我发现其他一些 ESB 更多地遵循“您可以通过使用 Camel 或其他库来获取该功能”，但没有提供设置这些“外部可用”功能的简单集成/指导。
*作为单点服务总线的安全性。看来 Talend 为管理所有公开的 SOA 服务的安全性提供了良好的支持。我没有机会在实际环境中充分尝试它（再次，请有更多经验的人！），但 ESB 为您提供完整（在运行时可管理）安全控制的想法很有吸引力。
*非常好的契约优先 IDE 支持创建服务然后由 ESB 使用。再次，请诚实的反馈。
*我对部署方面有点担心，听起来您需要运行多个服务器/服务，并且 ESB 解决方案的“部署”（带有存储库内容...？）可能会导致多点部署。另外，当转移服务位置（开发/测试/生产）时，我的快速回顾中并不太清楚（特别是与其他 ESB 解决方案相比……如果它们都稍微复杂一点，那也没关系）。
*诸如契约优先 Web 服务之类的用例，可以聚合/组合/重新映射来自多个其他 Web 服务（可能是二进制 java rmi 或 ejbremote）的信息来填充响应。
*用例例如监视 ftp 服务器的文件丢失、拾取文件、解析 xml/csv/edi 文件格式以馈送到另一个服务（不一定是繁重的批处理）
*用例例如监视 RSS 源以获取包含以下内容的新条目XML/CSV/EDI 文件链接、下载（新）文件、处理/提供给其他服务。
*CIFS/Windows 共享我没有研究过，但我也会从监控文件位置/拾取这里询问。
问题：具有 Talend ESB 经验的人，请对上述陈述提供有关现实世界准确性和/或问题的评论，也许还有一些更多现实世界的反馈。正如我上面提到的，从表面上看，我实际上对 Talend Open Studio 中的内容感到震惊，它作为开源免费提供，但无需许可即可在商业环境中使用，说实话，在使用 JbossESB 和 Mule 时，我对 JbossESB 和 Mule 有点失望在 Talend ESB 旁边。
感谢您的任何反馈！
I'm doing a quick review of ESB's and so far I've been surprised and impressed with the Talend ESB. I was really expecting Mule, one of the more well recognized open source esb, to be the defacto.
Before I commit after only an academic and basic testing review, does anyone that has much more hands-on experience with Talend (preferably after using another open source ESB) provide any pros/cons?
The areas that impressed me were:
*EAI, the number of components/transports ready-to-go for integration. I found some of the other ESB's followed more of a 'you can get that feature by using Camel or another library', but didn't provide easy integration/guidance in setting up those 'externally available' features.
*Security as a single-point service bus. It appears Talend offers good support for managing security of all your exposed SOA services. I didn't quite get a chance to fully try it in a hands-on environment (again, someone with more experience please!), but the idea that the ESB gave you full (manageable-during-runtime) security control was appealing.
*Pretty good contract-first IDE support for creating the Service then used by the ESB. Again, honest feedback please.
*I am a little worried on the deployment front, it kind of sounds like you need multiple servers/services running, and that 'deployment' of an ESB solution (with the repository stuff...?) may cause multi-point deployment. Also, when shifting service locations (Dev/test/production) it wasn't quite as clear in my quick review (particularly as compared to other ESB solutions...if they are all slightly complicated, that's fine).
*Usecases such as contract-first webservice, that may aggregate/combine/remap information from multiple other webservices (maybe binary java rmi, or ejbremote) to fill-in the response.
*Usecases such as monitoring ftp server for file drops, picking up the file, parsing the xml/csv/edi file format to be fed into another service (not necessarily heavy batch processing)
*Usecases such as monitoring RSS feed for new entries that contain XML/CSV/EDI file links, downloading (new) files, processing/feeding to another service.
*CIFS/windows share I didn't look into, but I'll ask here as well from a monitoring file location/pickup.
Question: Someone with Talend ESB experience, please provide comments to the above statements as to real-world accuracy and/or gotchas, and maybe some more real-world feedback. Like I mentioned above, on the surface I was actually blown away by what was in the Talend Open Studio offered for free as open source but usable in a commercial environment without licensing, and to be honest was a little disappointed with JbossESB and Mule when put beside Talend ESB.
thanks for any feedback!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
Talend ESB 提供了一个带有许多组件的漂亮、点击式的 IDE。然而当它
遇到定制要求时，解决方案可能会变得尴尬，有时
不可行的。一些 ESB 组件还不够成熟，它发生在我们的
项目中，Talend 可以动态装备这个和那个。
当您是软件开发人员时，我建议您手工制作。与阿帕奇骆驼一起
与 Apache Karaf 结合，您可以获得 100% 的控制权。顺便说一下这些框架
都在 Talend 的保护下。了解 Talend 所需的学习曲线
并不比学习这些提到的框架小。
干杯
希尔德
Talend ESB provides a nice clicky dicky IDE with many components. However when it
comes to a customized requirement the solution may become awkward and sometimes
infeasible. Some ESB components are not mature enough and it happend in our
project that Talend equips this and that on the fly.
When your are software developers I recommend make it by hand. With Apache Camel in
combination with Apache Karaf you gain 100% control. By the way these frameworks
are under the hood of Talend. The learning curve you need to understand Talend
is not that smaller than learning these mentioned frameworks.
Cheers
Hilde
我无法回答 Talend，但确实对 Mule 有相当深入的实践经验。您能否就您对 Mule 感到失望的地方提供更多反馈？您提到的这些领域都被 Mule ESB 社区的用户充分认可为优势。您应该查看最新的 Mule Studio 版本，因为它创建了与 Open Studio 一样强大的开发环境以及 MuleForge 上各种（60 多个）现成的连接器。
但是，从许可角度来看，MuleESB 是在 CPALv1.0 下分发的，这与 Talend 的 Apache v2.0 不同。
I can't answer for Talend but do have pretty in depth hands on experience with Mule. Can you provide more feedback on what you were disappointed with Mule? The areas you mentioned are all pretty well recognized by users in the Mule ESB community as strengths. You should check out the latest Mule Studio release as it creates a development environment as robust as Open Studio as well as the variety (60+) of ready to go connectors on MuleForge.
However, from a licensing perspective beware that MuleESB is distributed under CPALv1.0, unlike Talend's Apache v2.0.
最近推出了 Mule 3.0，Mule IDE 和 Talend IDE 的功能非常强大且具有可比性。
Jboss ESB 和 ServiceMix 仍然需要大量手动配置。
尽管我不认为自己是 Talend 专家，但由于我已经完成了审查，并且没有其他人以 Talend 经验回答过该问题，因此我将按照“Talend ESB 足够了，但现在 Mule ESB 也足够了”中的回答结束问题。
Recently with Mule 3.0, the Mule IDE and the Talend IDE are very capable and comparable.
The Jboss ESB and ServiceMix are still very hand-configuration heavy.
Although I do not consider myself a Talend expert, since I have finished my review and no others have answered the question with Talend experience, I am closing the question as answered in that 'Talend ESB is sufficient, but now so is Mule ESB'.