Ideally you would design your architecture with the realization that every architecture will become inadequate over time. So basically, design things so you can rip out various parts of it when the time comes.
I'll probably get a copy, just because I might learn something interesting.
In the end, the point isn't to learn software architecture, it's to learn the thought process behind software architecture.
Thanks for your input - the evolution of the architecture is the apple of my eye. The demo part of the book comes from the evolutionary architecture step, which is described on around 100 pages.
I'll probably get a copy, just because I might learn something interesting.
In the end, the point isn't to learn software architecture, it's to learn the thought process behind software architecture.