Here we are in the home stretch of the conference and the gems keep on popping up.
A replacement for the SQL Adapter?
I asked my annual question about whether they will be re-writing the SQL adapter and the short anser is "no" but... a surprise during the adapter presentation was the revelation that there will be a new Oracle adapter in R2. It turns out that the new Oracle adapter is a complete rewrite based on ADO.NET. Furthermore, it was suggested that since it's based on ADO.NET that it could also include support for SQL Server. It may be the case that we see a new 'database' adapter that supports Oracle and SQL server. Let's keep our fingers crossed!
Large Messages
A common challenge with BizTalk solutions is handling large messages. A large message is defined as anything over 1-2 megabytes. A persuasive demo showed us how dramatic the performance hit can be if you do not handle large messages carefully. The general approach is to avoid pumping huge messages into the message box. Instead, store the large part of the message in a file or database and then tag the message with a reference to the storage location. This would happen in the incoming pipeline. When messages leave BizTalk an outgoing pipeline reconstructs the message by retrieving the large bit and joining back to the message.
A very impressive solution was demonstrated that actually examined the incoming message for large elements, pulled them out (and replaced them with a reference id), stored them in the database, and then reconstructed the message on the way out. The performance improvement of this approach was huge. Something like a 60% improvement.
The presenter has a blog that's a good place to seek out more information on large message handling. It can be found here: http://blogs.digineer.com/blogs/tabraham/default.aspx
No comments:
Post a Comment