senior-architect

To design scalable software architecture, use structured decision frameworks to evaluate modularity, map dependencies, and generate architecture diagrams that define integration patterns across frontend, backend, and data layers.

Analyzing technology trade-offs involves applying system design decision frameworks to evaluate maintainability and scalability, documenting integration points and dependency mapping across the proposed tech stack.

Generating architecture diagrams requires mapping multi-service integration points and performing dependency analysis to visualize system design patterns across frontend, backend, and data layers.

Yes, system design patterns apply to both frontend and backend integration decisions, providing structured guidance for defining integration points, mapping dependencies, and documenting trade-offs across the entire tech stack.

Dependency analysis is needed to identify coupling and constraints between services, ensuring that integration patterns satisfy modularity and maintainability requirements while documenting architectural trade-offs.

Structured architecture decision frameworks are unnecessary for simple, single-service applications where manual dependency mapping is trivial and trade-off analysis does not impact multi-layer scalability or modularity.