The first goal of software architecture is to be able to identify all the interacting components of a system, including individual parts that may work independently, but contribute to the system as a whole.
As an example, a typical system will have some form of front-end channel/component (web portal or mobile app), a backend (handling all the heavy lifting) and a database (for long-term, durable data storage).
If you take this one step deeper, backend usually contains a number of components (API, processing service, notifications service etc.). Being able to describe and refer to each individual component makes it much easier to explain and communicate the software design and bridge the communications gap between technical (development teams) and functional (founder and customer) perspectives.
For more useful tips, check out our podcast ‘From The Factory Floor’ or subscribe to our weekly blog!
Alternatively, feel free to email me at
Merry Christmas and Happy New Year!
