The authors of this paper put forth the idea of architectural styles, and trying to define common patterns used for solutions, not problems. They classify mainly the styles used for handling data and communication in architectures, then suggest patterns to follow based on need.
I enjoyed their breakdown and thought it was interesting, but is it enough? The job of the architect is far from over after picking the needed data communication. How execution is structured, style, modularity and many other concerns will still have to be addressed. Should these be categorized too? Does one type of data architecture naturally lead to one type of process for development? This paper is a good start, and opens the door for more research in the field.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment