Hacker News new | past | comments | ask | show | jobs | submit login

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).

There is so much noise in the space of Software Architecture. And I think is something natural: building software is not architecture, nor engineering, nor 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.

Personally I find these resources more convincing than the booklet or the references mentioned inside it:

For the technical/organizational (Dev teams) part

Architecture without Architects: https://www.youtube.com/watch?v=qVyt3qQ_7TA

Clean Architecture: https://www.youtube.com/watch?v=Nsjsiz2A9mg



For the Enterprise Architect part:




Solution architecture may incorporate non-software related concepts and processes, thus defining the role of solution architect broader than role of software architect and requiring bigger set of skills (e.g. when some process should be implemented without software via manual labor, you‘ll need certain understanding of human psychology to evaluate its efficiency). As a solution architect you solve a business problem, using software as necessary. As software architect you focus only on those business problems, which require software. That’s the difference, as it should be (but quite often it’s just one or another marketing tag, as you correctly suggest).

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact