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 course looks at strategies and techniques to incrementally architect your way out of a legacy mess, and to set up new applications for success.
What you will learn
- The joys of a strong domain model, and how to evolve one.
- How to use an anti-corruption layer as a border guard.
- How to get over your dependence on dependency injection frameworks.
- That you can incrementally replace legacy apps more often than you realise.
- The value of getting into production early.
- Not to fear integrating with third party libraries.
- Why “transfer object” is an oxymoron, and how to do remoting properly.
- The big picture: value, risk and the role of an architect.
- Designing for simplicity and clarity.
- Systems integration: remoting, scaling and integrating with third parties.
- Taming legacy systems: strategies for transition and integration.
- Operations: monitoring and performance tuning.
- Human factors: techniques for communication, feedback and successful change.