<Disclaimer>This is personal notes of what I retained during the session. This can be incomplete, partially right or wrong. It is just  part of the notes I took and what retained my attention. Nothing prevents the user to get more information on their favorite web site.</Disclaimer>
Basically, Dublin is an extension to IIS/WAS to monitor and manage workflows and WCF services on top of the .NET framework. It will be available in the next version of Windows Server as a new role.
It implies the hosting, the persistence, the monitoring and the messaging around those services. For example, on the hosting side, a timer and a discovery service will be available. The management will be available through an API accessible, for example, with PowerShell.
It will be possible, using a “Persist” activity, to support service outage, meaning that the “Persist” activity will be responsible of the persistence of the workflow while the target service is down. The workflow will continue when that service will be back online.
Some demo about Routing (versioning), reliability and monitoring were shown during this session.
This session was just an overview of “Dublin”, but, in my opinion is, now, how to make the decision between pure WF implementation, Dublin and BizTalk to implement a sequence of activities…Couple of other sessions are scheduled during this week, so I hope to have an answer in one of them.