Designing software architecture for change
Requirements will change. Good architecture makes those changes ordinary rather than painful.
This is a placeholder article. It will be replaced with final, reviewed content.
The only certainty in a software project is that the requirements will change. Architecture is how we prepare for that.
Separate what changes often
Business rules, integrations and interfaces change at different speeds. Keeping them apart limits the ripple effect of each change.
Prefer boring foundations
Well-understood, stable foundations leave more energy for the parts of the system that are genuinely new.