So as the blog has died a little off (I am sorry for that) I still want to share more with you as we go forward, I’ve moved from consultancy, to MVP for Integration, to Microsoft as Technical sales and I’m currently working as a Program Manager for BizTalk in Microsoft Corp, my passion for BizTalk is still there but I feel the purpose of this blog is to help you as a BizTalk operator to make it easier.
For those following me for a while, know that I took my family of 6 and relocated to Seattle, Redmond to work for Microsoft to help deliver advanced integration capabilities. The PM team isn’t big but what we deliver is awesome. Although the release is not on my back the team behind this release has really pulled it of, and I am very proud.
Today I’m happy to announce the RTM (Released to manufacturing) of BizTalk Server 2016. You will soon be able to play around with it but it will take some more time until the last pieces of the puzzle is completed.
We’ve done massive changes to the UI and the dev UI. Minor issues that has been there since 2006 has be resolved. We have also done upgrades to align with standards (like SHA2 support, updated SWIFT, the HIS 2016 is also RTM). We will continue our investments in the product going forward.
If you want to read some more resources I’d suggest you to take a look at the following links
The release we have been waiting for is finnaly starting to turn into a full product. Although a lot of the features we’re waiting for as of know the new release brings out a full set of new features. Just the fact that you know can export multiple messages in one bunch, and import bindings without tracking turned on (global setting).
We all know that the focus at Microsoft is Mobility first and cloud first at the moment. AS some of you have found out I’m no longer in the MVP program since I joined Microsoft January 1st.
We all know that debatching should be done in the receive pipeline, I’ve yet to see any really good scenarios where you shouldn’t, but I know there is some (debatching in the orchestration can give you a huge performance loss in BizTalk).
So I guess most of you are aware that benchmarking of the environment and your applications are critical for your environment, when it comes to tuning and to see how well your applications are performing, we often end up with requirements like “We need to transfer 100 messages a minute” we all go “okay” but how good is it in the end, and where is the biggest bottleneck?
So, how often do you benchmark. We got the BizTalk Benchmark Wizard to indicate how your environment is doing. So I decided to go above and beyond and make something for you guys. But I want your input. What is the biggest struggles you have when it comes to benchmarking, and maybe I’ll implement them into the tool.