I guess the answer to your question is dependent on the problem(s) you're trying to solve. I've recently finished a project for which I considered using the ESB Toolkit for error handling but eventually decided that the scope of the project wasn't big enough for the extra effort required to setup and learn how to use it!
For me, the most useful "feature" of BizTalk I use is direct-binding in my orchestrations to produce de-coupled orchestrations. But again, thats what I needed for the specific scenario.
BizTalk is a massive product and I would suggest that you use the available functionality only if it solves you problem simply (don't attempt to provide over-engineered solutions!)
By all means investigate all the functionality that interests you; there's a huge store of resource available and lots of helpful individuals here on SO!
发布评论
评论（1）
我想您问题的答案取决于您想要解决的问题。
我最近完成了一个项目，我考虑使用 ESB 工具包进行错误处理，但最终决定该项目的范围不够大，无法承担设置和学习如何使用它所需的额外工作！
对我来说，我使用的 BizTalk 最有用的“功能”是在我的编排中直接绑定以生成解耦的编排。但同样，这就是我针对特定场景所需要的。
BizTalk 是一个庞大的产品，我建议您仅在它能够简单地解决您的问题时才使用可用的功能（不要试图提供过度设计的解决方案！）
无论如何都要调查您感兴趣的所有功能；这里有大量的可用资源和很多乐于助人的人！
我的钱花得很值:)
I guess the answer to your question is dependent on the problem(s) you're trying to solve.
I've recently finished a project for which I considered using the ESB Toolkit for error handling but eventually decided that the scope of the project wasn't big enough for the extra effort required to setup and learn how to use it!
For me, the most useful "feature" of BizTalk I use is direct-binding in my orchestrations to produce de-coupled orchestrations. But again, thats what I needed for the specific scenario.
BizTalk is a massive product and I would suggest that you use the available functionality only if it solves you problem simply (don't attempt to provide over-engineered solutions!)
By all means investigate all the functionality that interests you; there's a huge store of resource available and lots of helpful individuals here on SO!
There's my pennies worth :)