I think of software architecture more about the boundaries within a system, objects, modules, services, etc. their responsibilities and interactions. Code orga

I think of software architecture more about the boundaries within a system, objects, modules, services, etc. their responsibilities and interactions. Code organization is related but depends on the language/framework if that matters. If you are using an object-oriented language then reading up on Design Patterns will be helpful, the most common in web application development is MVC. To dive into why MVC is important you have to realize that, back in the day, single file Perl scripts (or PHP, Python, etc.) that did everything (get parameters, execute DB code, output HTML, etc.) were the norm. A lot of what is good software design/architecture comes from the history of bad design/architecture. Separation of concerns is a solid concept within applications and for integrating applications. Be wary of digging into what BigTech companies do - they have really large/complex systems that most of us won't ever scale up to. These may be solutions to problems you'll never have and could cause more complexities than you need.