Paul Downey covers the risks of premature standardisation, partial implementations and open extensions, cloud computing lock-in, and formal activities vs lightweight open processes like open source.
Rod Johnson talks about Java’s evolution, in particular J2EE, presenting the lessons to be learned from its failures, preparing to avoid such mistakes in the future.
Kevlin Henney does not make recommendations for architecting software but rather brings into discussion 5 considerations useful to be reflected upon: economy, visibility, spacing, symmetry, emergence.
Dan North gives an overview of Domain Driven Design and Behavior Driven Development then ties them together for a powerful mix.
Ian Robinson on issues to be addressed when starting a new SOA project by identifying business capabilities using user stories, describing services and contracts, and setting up teams for delivery.
Johnsson refreshes the listeners’ memory on using value objects showing by example how their good use can revolutionize a program’s architecture, simplifying it, making it more readable and testable.
Dan North discusses an example of rearchitecting an application without rewriting it from scratch, and explains general strategies for a holistic rearchitecture.
This tutorial presents an approach utilizing leading-edge techniques from social complexity science and team dynamics to change the dynamics of a team with the aim of optimizing their work together.
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.