Don't you think that centralising the responsibility of the architecture design is an antipattern?
For what I saw normally architects can't keep up with all modern techs and if they do, it still takes the ownership of the solution from each domain (FE, BE, DevOps etc).
Wouldn't it be better to have tech leads design the architecture/solution together?
This looks like someone’s sophomore college assignment. There is almost no practical advice here except defining buzzwords at a high level. Most critically the section on microservices contains only the most basic information and shows no real world experience.
„all you to know“ is very ambitious and misguiding phrase for such a shallow presentation. It’s not even close, without ubiquitous language, SOLID, different programming paradigms etc. Distinction between software, solution and enterprise architects is questionable: there are other definitions of those roles.
I've worked for Fortune 50 sized companies, as Chief Architect, and I've worked for some amazing software engineering companies in a similar capacity.<p>Doing software architecture for the business side of the house, traditional IT, at any company is next to impossible. We are at the mercy of the business and the business doesn't care about standards, efficiencies. or anything, except making the quarterly estimates. The business is very supportive of all efforts right up until they decide that it might impact quarterly estimates, and then everything is out the window. When operating in such an environment there is no way software architecture, or security and compliance has a possibility of success.<p>On the Engineering or product side of the house especially for software product companies, software architecture is easy, and welcomed.<p>It all comes down to who you work for and what you are doing.
It is a pity that so much effort has been put on writing/designing this booklet. Software Architecture is very hard to 'compress' into a booklet this size. And the concepts explained seem all mixed up. Also, I never understood the difference between Software Architect and Solution Architect, I think they are just marketing tags to specify a bit more what you can do as an architect (install/customize a turn-key solution, networking architecture, software development guidance from scratch, etc).<p>There is so much noise in the space of Software Architecture. And I think is something natural: building software is <i>not</i> architecture, <i>nor</i> engineering, <i>nor</i> mathematics... still it is all that at the same time. It also has strong social, linguistic and design components. Maybe it is just too new a discipline to define it clearly.<p>Personally I find these resources more convincing than the booklet or the references mentioned inside it:<p>For the technical/organizational (Dev teams) part<p>Architecture without Architects: <a href="https://www.youtube.com/watch?v=qVyt3qQ_7TA" rel="nofollow">https://www.youtube.com/watch?v=qVyt3qQ_7TA</a><p>Clean Architecture: <a href="https://www.youtube.com/watch?v=Nsjsiz2A9mg" rel="nofollow">https://www.youtube.com/watch?v=Nsjsiz2A9mg</a><p><a href="https://www.amazon.com/Things-Architect-Knows-About-Transformation/dp/1537082981/ref=sr_1_1?s=books&ie=UTF8&qid=1545832595&sr=1-1&keywords=37+things+architect+knows" rel="nofollow">https://www.amazon.com/Things-Architect-Knows-About-Transfor...</a><p><a href="https://www.enterpriseintegrationpatterns.com" rel="nofollow">https://www.enterpriseintegrationpatterns.com</a><p>For the Enterprise Architect part:<p><a href="https://www.amazon.com/Organizational-Culture-Leadership-Edgar-Schein-dp-0470190604/dp/0470190604/ref=mt_paperback?_encoding=UTF8&me=&qid=" rel="nofollow">https://www.amazon.com/Organizational-Culture-Leadership-Edg...</a><p><a href="https://www.amazon.com/Chess-Enterprise-Architecture-Gerben-Wierda/dp/9081984055/ref=sr_1_1?s=books&ie=UTF8&qid=1545832621&sr=1-1&keywords=chess+architecture" rel="nofollow">https://www.amazon.com/Chess-Enterprise-Architecture-Gerben-...</a><p><a href="https://www.youtube.com/watch?v=ScHG63YmJ2k" rel="nofollow">https://www.youtube.com/watch?v=ScHG63YmJ2k</a>