We architects love a good framework. We like our abstractions, we like to design "enterprise" solutions, we like to mandate complex algorithms, or better yet to prescribe toolkits to enable other teams to implement complex algorithms under our expert guidance. If it looks like a good idea we slap the label "pattern" on it and tell everyone to do it.

Ok, maybe that isn't you. But it's likely you work in an organisation where the other guys do. So what can you do about it? Is this the only way to do architecture?

This tutorial looks at strategies and techniques to incrementally architect your way out of a legacy mess, and to set up new applications for success.

During this one day tutorial you will learn, among other things:

• the joys of a strong domain model, and how to evolve one.
• how to use an anti-corruption layer as a border guard.
• to get over your dependence on dependency injection frameworks.
• not to have interfaces for everything.
• that you can incrementally replace legacy apps more often than you realise.
• how to successfully decouple subsystems.
• the value of getting into production early.
• not to fear integrating with third party libraries.
• the courage to automate the things you should, the serenity to accept the things you can't and the wisdom to know the difference.
• why "transfer object" is an oxymoron, and how to do remoting properly.