tag:blogger.com,1999:blog-34524994.post98321239357875219..comments2023-10-21T06:07:22.066-07:00Comments on Azure Thoughts, EAI Challenges: Microsoft ESB GuidanceSteef-Jan Wiggershttp://www.blogger.com/profile/03378054798030259210noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-34524994.post-20843860261078990402009-11-26T17:51:55.485-08:002009-11-26T17:51:55.485-08:00you may want to look at vtd-xml, the latest and mo...you may want to look at vtd-xml, the latest and most advanced xml processing api that is a must have for high perfomrance ESB<br /><br /><a href="http://vtd-xml.sf.net" rel="nofollow">vtd-xml</a>Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-34524994.post-59946488880007398542008-06-09T04:02:00.000-07:002008-06-09T04:02:00.000-07:00Recently I come across Microsoft ESB Guidance (on ...Recently I come across Microsoft ESB Guidance (on codeplex) and in my recent company people have implemented ESB, I don't find any issues with Performance. But yes it is constricting developer or designer in many ways with flexibility compare to only BizTalk solution and with ESB - BizTalk solution. Microsoft ESB Guidance implementation don't allow you to administrate your messages inside Nilay Parikhhttps://www.blogger.com/profile/14862922668894024176noreply@blogger.com