May 5. 2008 12:25

Marc,

great A-Z guide on being an architect. Being myself a beginner on an architecture team, and being involved in the task of creating such team, I find that the article provides a good summary on the role of the architect and some architecture principles.

Only one comment / sugestion: to include something about the dilema of centralized / distributed systems. Perhaps as part of the "B" letter for Balance.

Being the forest of application silos (at the UI, logic and data levels) often one of the reasons for the need to create an architecture team, the level of centralization / distribution easily becomes part of the architecture strategy.

Having given it some thought, I would summarize it to "Centralization around best-of-breed applications for each vertical business domain, and around a middle tier of business services common to most business domains.". Very summarized obviously.

Looking forward to hear your thoughts!

Regards,
Pedro Bravo

Pedro Bravo