Till now, we've been creating components that "work", and work quite easily. We haven't taken into account various types of failures. In production, a lot of things can go wrong. With the right(!) combination of stupidity, bad luck, chicken blood and lightning strikes, we can get deadlocked, live locked, our nodes could go down, and the universe might explode. An exhaustive discussion of fault tolerance could span years if not decades, but in this session, we'll look at some things we can do to deal with failures without bringing our applications to their knees (or worse).
This is likely to be a bit more diagrams and discussions, but there's likely to be some coding involved too. Remember your laptops :)
Some basic skeleton code is likely to be sent out before the session. There's only so many times we can start from scratch and having the boilerplate ready should save some time. Watch this space!
Please remember to register on http://skillsmatter.com/event/open-source-dot-net/getting-started-with-fault-tollerance as well. It helps with administration considerably.