Dublin + .NET Framework 4.0 = "BizTalk/SOA Express Framework" ! (part 4)

12 באוקטובר 2008

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

Windows Workflow
Foundation 4.0

Windows Server
"Dublin" technologies

RESTful enhancements

  • Simplifying the building of REST Singleton & Collection Services, ATOM Feed and Publishing Protocol Services, and HTTP Plain XML Services using WCF
  • WCF REST Starter Kit to be released on Codeplex to get early feedback

Messaging enhancements

  • Transports – UDP, MQ, Local in-process
  • Protocols – SOAP over UDP, WS-Discovery, WS-BusinessActivity, WS-I BP 1.2
  • Duplex durable messaging

Correlation enhancements

  • Content and context driven, One-way support

Declarative Workflow Services

  • Seamless integration between WF and WCF and unified XAML model
  • Build entire application in XAML, from presentation to data to services to workflow

Significant improvements in performance and scalability

  • Ten-fold improvement in performance

New workflow flow-control models and pre-built activities

  • Flowcharts, rules
  • Expanded built-in activities – PowerShell, database, messaging, etc.

Enhancements in workflow modeling

  • Persistence control, transaction flow, compensation support, data binding and scoping
  • Rules composable and seamlessly integrated with workflow engine

Updated visual designer

  • Easier to use by end-users
  • Easier to rehost by ISVs
  • Ability to debug XAML

Provide standard host for WF and WCF applications

Pre-built developer services

  • Message-based correlation
  • Message forwarding service
  • Content-based message routing
  • Compensation service for long-running transactions

Greater scalability and easier manageability

  • Enable scale-out of stateful workflow applications
  • Persisting and rehydrating state for high scalability
  • Enhanced management and monitoring functions
  • Tracking store for workflow events

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 😀

.NET Framework 4.0 = "BizTalk/SOA Express Framework" ? PART3
.NET Framework 4.0 = "BizTalk/SOA Express Framework" ? PART2
.NET Framework 4.0 = "BizTalk/SOA Express Framework" ?

הוסף תגובה
facebook linkedin twitter email

כתיבת תגובה

האימייל לא יוצג באתר. שדות החובה מסומנים *

4 תגובות

  1. Eran Kampf13 באוקטובר 2008 ב 18:36

    Actually Biztalk (V6) was orgiginally part of the Oslo roadmap and was supposed to be redesigned to work with workflows and messaging tools from Oslo (finally, WF workflows that scale at enterprise level?)

    However, Microsoft pushed that plan and changed the roadmap so that Biztalk V6 is not part of Oslo which means it will continue to support BizTalk Server's separate messaging and Orchestration components, alongside the corresponding .NET Framework technologies that are part of Oslo.

    While having BizTalk as Oslo's orchestration engine, like you suggest in your post, made perfect sense., sadly its not part of the V6 \ V7 roadmaps of the product published by MSFT 🙁

    The probable reason for this change in roadmap is that moving to use Oslo would have been difficult for customers and partners with solutions on the current version of BizTalk Server. Furthermore, Microsoft itself would have faced a major project re-creating BizTalk Server's messaging adapters, EDI, RFID, and other components to work with Oslo tools.

    Makes you wonder though, what kind of orchestration engine will drive Oslo's applications…

  2. Eran Kampf13 באוקטובר 2008 ב 18:45

    BizTalk Roadmap page:

    (Check the part about Oslo at the bottom)

  3. Ben2 בפברואר 2009 ב 12:07

    Biztalk is a big $$ solution , not just the product but the whole team that runs it . I think this is the reason it was not integrated by Oslo