Skip to content

Solution architecture

Solution architecture sits between enterprise architecture and day-to-day engineering. A solution architect takes a specific business problem, works out the requirements that really matter, and designs a system that meets them within the organization’s standards, budget and timeline.

What should we build to solve this problem, and how do we know the design is good enough?

No pages in this category yet. The first ones are on the way.

  • Gathering requirements and quality attributes (non-functional requirements)
  • Architecture decision records (ADRs)
  • Trade-off analysis
  • Documenting architecture with the C4 model
  • Communicating designs to stakeholders
  • Build vs buy decisions

Written and edited by Abhinav Taduka, enterprise software architect.