.NET Framework 4.0 = "BizTalk/SOA Express Framework" ?
Ok, let me first say that this is MY OWN current mashup !
Well lets look at the current status:
In the year 2005, Microsoft have released the .NET Framework 2.0. In it was the FREE ( as opposed to the "you have to buy" ) products: ASP.NET 2.0 WebParts, ASP.NET 2.0 Memebership provider (a "Forms Authentication component") and SqlServer Express 2005 = what you got is the ability to write you own "SharePoint 2005 Express Edition", great no ?
In the year 2006, Microsoft have released the .NET Frameowrk 3.0. In it was the FREE products: Workflow Foundation, Windows Communication Foundation and CardSpace = What we got is a base for Sequential/State Machine/Data-Driven Workflow [WF] which can communicate, with support in Transactions, with all most any thing [WCF] in a secure way [CardSpace]. Well all of these have created a way to build a "partial SOA platform". Why do I say partial? mainly because SOA is Message based, and some one has to build and process Inbound and Outbound Messages in a fastest and with least code manner, just like what we have in BizTalk – Pipelines , Adapters.
Today, in 2007, we have the new and shiny .NET Framework 3.5, which has just now been released. One of the main architectural aspects that came along with the .NET Framework 3.5 was the LINQ concept. LINQ has become the current buzzword, and for a very good reason, with LINQ we have among other the XLINQ, DLINQ and PLINQ. Using these we would be able to communicate with any Data[DLINQ] / XML[XLINQ] message in a the fastest way [PLINQ]. But as all things, even components have to mature in the industry, and the industry waits for a "SP1" of the product. By the time "SP1", in this case .NET 4.0, would mature, the long waited Entity Framework would be complete, thus completing the circle for creating a Framework which has the ability to go side by side with Microsoft's next SOA platform – BizTalk 2009.
The plans for 2009, the expected release year of .NET Framework 4.0, is still unknown. But, as an example, if we look at the history of VC++ 6.0 , with the release of .NET Framework 1.x, MFC was not thrown away, just future development was put into a halt. The same I expect to be in our case, BizTalk Orchestrations would be able to live side by side with WF Workflows. On the same level Adapters and Pipelines would be able to be replaced with WCF and LINQ components
Just look at the pictures below, and do the math ( each picture has a link )
from the: An XML Guru's Guide to BizTalk, Part 2