Eric Nelson explains what are ORM, EDM, and ESQL, what is the difference between LINQ to SQL and LINQ to Entities, which one should be used, accompanied by hands on demos showing how to use them.
Eoin Woods explains how Barclays Global Investors (BGI) designed Apex to meet the challenges it faces and the Java technologies which were chosen for an architecture with variations on standard J2EE.
Brian Oliver explains a number of data grid design patters: Command, Functor, Messaging, and Push Replication. He also mentions some traditional patterns used so far and Coherence Incubator.
Stefan Tilkov offers guidelines for the architect looking for a solution to his problem. Should it be a generic or a specific one? He compares several such solutions outlining the pros and cons.
Joe Armstrong on 6 reliability laws, Isolation, Concurrency, Failure Detection, Fault Identification, Live Code Upgrade, Stable Storage, showing how they are respected in Erlang, plus some examples.
Based on real-life cases, Michael Poulin shows how to use 7 service oriented principles to handle service behavior in the execution context and UI changes, and how to prepare for unexpected changes.
Graeme Rocher introduces Groovy and its corresponding web framework, Grails, followed by a code writing demo intended to highlight the advantages of using Grails over Java EE for web applications.
This talk discusses a number of patterns common for setting up Agile Distributed Development and will show the results that can be achieved once you get into a good Fully Distributed Scrum.
Sadek Drobi shows how he applied functional programming principles, like recursion, functions, monads, to a real-life project which needed to meet certain performance requirements.
Michael Foord discusses IronPython, the DLR, static vs. dynamic typing, VS.net integration, Resolver One, embedding IronPython, error handling, dynamic operations, and functions as delegates.
Phillip Ghadir presents an application initially built using SOAP, WSDL, WS-*, and was later migrated to REST, Atom, and AtomPub, explaining the decisions made, the pitfalls and the lessons learned.