Software Architecture
It means taking a stand.
It’s easy to think of architecture as a series of choices: which database, which operating system, which programming language, which framework. All of those decisions should flow naturally from having a clear idea of what you’re building and why.
What are you going to hang your hat on? Responsiveness? Reliability? Durability? Throughput?
A good system will try to accomplish all of the above and more, but it had better know what it’s trying to be the best at. Once you’re clear on what you’re trying to accomplish, your decisions are justifiable and their success measurable.
