Some books are about architecture and the role of the software architect. Large shelves are dedicated to agile literature. Few books merge the two subSome books are about architecture and the role of the software architect. Large shelves are dedicated to agile literature. Few books merge the two subjects. This is one of them. By design this merge is stretched between 2 not so compatible position. To address it, the author split the architect's missions in 4: - understand : how to gather information from stakeholders - explore : build solutions from needs expressed - make : build models, plans or prototypes - evaluate : check how the realization fits the reality The major drawback of this text is the level of abstraction, with few or no concrete examples. Therefore it miss the dynamism needed to make the reading enjoyable. ...more
I don't know if it makes sense, but the book is somehow messy. The very high level thougths as they are exposed may give something to think about, butI don't know if it makes sense, but the book is somehow messy. The very high level thougths as they are exposed may give something to think about, but miss the practical dimension. Probably this very short text doesn't address the beginner, therefore I had hard time to appreciate it.
Sometimes, I get very bad books. It is one of them. The microservices are a hot subject and looking around to understand the point of view of excellenSometimes, I get very bad books. It is one of them. The microservices are a hot subject and looking around to understand the point of view of excellent authors seems to me the best thing to do. Few are excellent, and build-up a convergent view of the subject, many are acceptable, mainly redondant with the first ones. And few (including this one) are bad, throwing a radically different picture and pretending they are right and everybody else is stupid. Really, the author said the other guys are outdated ! This is not microservices, this is a nanocomponent view. The author is dogmatic about what should be done. His point of view carries a lot of problem, including architectural complexity at the system level, lack of strength and safety between component and mainteance nightmare. The author ignore all these issues by stating that's a problem of incompetence and all we need is a really strong architect (like him). The author is not ignorant, it's pretty obvious along the reading. But the ideas and the arrogance of the author are hard to swallow.
Christophe
>
Books:
software-architecture
(32)
Loading...
