I Just returned from TechEd 2012 and one of my favorite sessions was ‘Application Integration Futures – The Road Map and What’s Next in Windows Azure‘. It was refreshing to see the first slide’s title “Key takeaways: we are innovating in BizTalk”.
Here is the abbreviated message from the slide deck:
Continued investment in BizTalk – take your investment forward
BizTalk Server: releasing 6 months after Windows 8
Enabling new Azure based BizTalk scenarios in IaaS & PaaS
Bringing together BizTalk on-premises and Azure
Bet on BizTalk and continue to buy
BizTalk on IaaS coming soon – reduce hardware procurement lead time; reduce time & cost setup and configuration (expect “base BizTalk images”; move apps to Azure and back easily
BizTalk on PaaS – we are already seeing EAI & EDI on Service Bus using Bridges, Transforms, and trading partner management
Here is the timeline (taken from the presentation slide deck)
A challenge we have at Tallan is keeping our training up-to-date with the latest and greatest of technologies. We are constantly re-evaluating our lessons to keep up with ever changing technologies. In recent months, we have seen a shift in our client work from using traditional ASP.NET to using ASP.NET MVC 2. This has challenged our .NET developers to learn and create MVC best practices and ensure high quality deliverables. As you may know, MVC to a .NET developer can take time to understand and learn.
As an organization, we approach training from a mentor/mentee concept. This allows our trainees to have a dedicated training partner to guide him/her through the module and it allows for the mentor to learn communication and management skills. We have begun reviewing our training process, in particular our .Net training modules. With this in mind…
Recently, a company in the process of implementing BT 2006 within their enterprise asked me for a recommendation regarding best practices for a pre-existing usage scenario they were seeking to accommodate using BizTalk. This company receives, on a reoccurring basis, a variety of disparate inbound flat file business documents which, at present, are processed into their suite of business applications using SQL Server DTS. While the interchange with this company in question has CERTAINLY inspired folks at BlogBizTalk and Tallan to start developing a whitepaper comparing and defining best-practice usage and design considerations for implementing SSIS (or equivalent ETL tool) and BizTalk both in scenarios of consonance or autonomy, a few much more immediate considerations arose for my address.
One such very much more low level consideration was that for the handling of the disparity of received file formats. My understanding…