Software Architecture Is Overrated: Practical Design Practices from Large‑Scale Tech Companies

Software architecture best practices, enterprise architecture patterns, and formal system description methods are useful tools, but designers should start simple and avoid unnecessary complexity.

The author, who has designed large systems at Uber and Skype, describes how massive projects involving hundreds of engineers are built without standard architecture tools such as UML, 4+1, ADR, or C4, relying instead on simple boxes and arrows.

These teams also lack dedicated architects; senior engineers write code and drive design, with all members contributing ideas and challenging decisions.

Common architecture patterns and terminology (micro‑services, serverless, event‑driven, etc.) are rarely referenced in design documents, even if discussed during brainstorming.

Across many tech companies, the design process follows six steps: start from the business problem, brainstorm solutions, explain the approach on a whiteboard, document the design with clear, jargon‑free language, discuss trade‑offs, and distribute the document for feedback.

The author notes that while the principles align with traditional architecture guides, the execution is far simpler, using tools like Google Docs or Office365 rather than formal modeling languages.

Engineering culture—high autonomy and flat hierarchies—allows this lightweight approach, contrasting with more traditional firms where architects enforce strict documentation and processes.

Simple, terminology‑free designs are preferred because they are easier to understand, review, and maintain; architecture patterns should serve as helpful references, not as goals that dictate design.

To improve system design, the author recommends: collaborating on a whiteboard, writing concise design documents, creating alternative solutions for comparison, clearly stating trade‑offs and constraints, and actively reviewing peers' designs.

The ultimate advice is to aim for the simplest design that anyone can grasp, rather than chasing complex patterns or formal methods.