Sites were awash with Dublin news today. But what is it really?
To understand Dublin you can start with Steve Martin’s post announcing the new technology, which will be (of course) covered in detail at PDC later this month. Steve’s team heads up the WCF and WF parts of the .NET Framework so he’s in a good position to explain the new Dublin codename.
In a nutshell: Dublin is about letting the next versions of WCF and WF based apps scale better whilst providing easier deployment and management functionality.
How exactly this is enabled is difficult to get a grip on from Steve, which is why we need to head over to the new Dublin site on Microsoft. Here we learn that Dublin is a server (or as Mary-Jo writes, a new distributed application server).
Actually, it’s not exactly a server, rather a ‘set of enhanced Windows Server capabilities.’ that ‘.extend Internet Information Server (IIS) to provide a standard host for applications that use workflow or communications’ (from the Microsoft Dublin site). Stephen Forte probably has the good summary we came across.
It’s getting a little clearer now, but we’re still a little unsure. Thankfully a nice little table in this Dublin Overview document provides a nice little table:
|Windows Communication Foundation 4.0
||Windows Workflow Foundation 4.0
||Windows Server "Dublin" technologies
- 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
- 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
Dublin will be packaged up and made available as a download for Windows Server customers, and of course included in future Windows Server releases.
The keen eyed amongst you will notice that Oslo rears its head (see Tuesday’s post for details on that front) and if you read through the doc you’ll learn that Dublin will be the first server product ot deliver support for Oslo.
But there’s others of course – further in the doc it notes that they’ll be directly supporting BizTalk and Dublin working nicely together.
Other items: Dublin will be backwards compatible and support existing .NET 3.5 WCF and WF applications.
Microsoft are touting Dynamics AX and CRM as the first products slated to support Dublin.