Dublin + .NET Framework 4.0 = "BizTalk/SOA Express Framework" ! (part 4)
Finally I have a name for what I was talking about – DUBLIN !
With the announcement of Riding the Next Platform Wave: .NET Framework 4.0 and Windows Server "Dublin", and the attached overview of WCF 4.0, WF 4.0, and Windows Server "Dublin" specifications we understand that the unification of “Dublin” and the version of Biztalk that would come after BizTalk 2009 is unavoidable !
Microsoft has laid the foundation ( now we see the true meaning ) of this in the Version 3.0 of the .NET Framework.
Just look at this section from the specification
Q: What Application Server technologies are coming in Windows Server?
Windows Communication Foundation 4.0
Declarative Workflow Services
Significant improvements in performance and scalability
New workflow flow-control models and pre-built activities
Enhancements in workflow modeling
Updated visual designer
Provide standard host for WF and WCF applications
Pre-built developer services
Greater scalability and easier manageability
Supports “Oslo” modeling platform
So what do we expect to be the difference ?
- let’s start with the word light weight or cheap ( or “Express” )
- Did some one said LOB / B2B ? in Dublin , officially Microsoft won’t promise this Functionality , why ? The word “Adapters” comes to mind as the first connotation word. But considering the fact that this would give a great Integration solution with current status of richness in .NET Web Service ( ASP.NET & WCF ) based applications that your company might have – then the missing “Adapters” won’t matter to you really
- So you want a more “Visual” comparison ? Do you know the Difference between WSS 3.0 and Moss2007 Enterprise ? BDC ( Business Data Catalog ) , Forms Server and Excel Services are just but a few added values to the amount of available scalability that comes already with the Moss2007 Standard.
- On the other hand ! to be a “real” “Dublin” programmer it would be best if you’d be also a BizTalk programmer – why ? because of this section:
The integration server and application server workloads are distinct but complementary; customers want to be able to deploy them separately as needed to support their distinct requirements. For example, customers that don’t need the rich LOB or B2B connectivity provided by an integration server, will deploy the Windows Server application server to host and manage middle-tier applications. Likewise, customers that need to connect heterogeneous systems across an enterprise, but don’t need to develop and run of custom application logic, will deploy BizTalk Server. When customers need both capabilities, “Dublin” and BizTalk Server will work together nicely.
which shows to us that in the end this would help Microsoft in the integration of BizTalk into companies that still don’t work with BizTalk , but use .NET as their development platform. OR companies that required an elevated ( Server ) capability of their business logic which was wrote in .NET 3.x WF/WCF
The King ( BizTalk ) is not dead , he just would marry the princess of the neighboring country 😉 , just like MFC Still lives among us , it’s just “Managed” now 😀