This article presents 50 concise statements that cover core software architecture concepts, including fundamentals, types, views, design principles, practical practices, distributed architecture basics, and the mindset needed for architects, providing a quick reference for beginners.
The article explains business architecture as a simplified enterprise blueprint, defines business and its components, outlines core elements such as value streams, capabilities, processes, objects, and organizational structure, and provides diagram examples to help readers apply these concepts in projects.
The article explores the broad, evolving nature of software architecture, emphasizing the need for contextual thinking, continuous learning, and understanding of architecture styles, characteristics, decisions, and design principles, illustrated with diagrams and key laws that guide architects in balancing trade‑offs and focusing on why over how.
This article explains the fundamental concepts of software architecture, distinguishes between systems, subsystems, modules, components, frameworks and architectures, outlines the evolution from monolithic to distributed and micro‑service designs, presents fifteen universal design principles, and highlights typical mistakes architects should avoid.
This article explains the concept of enterprise architecture by likening an organization to a massive software system, discusses its importance in digital transformation, outlines its meta‑model and view layers, and highlights why a structured architectural approach is essential for modern enterprises.
This article explains ArchiMate's basic views—including composition, support, collaboration, and implementation perspectives—by describing each viewpoint's purpose, focus, and example tables for composition, support, collaboration, and implementation views, as well as physical and layered views.
This article explains ArchiMate's basic views and the four categories of viewpoints—Composition, Support, Collaboration, and Implementation—detailing their focus areas, examples, and the specific technical and technology‑usage perspectives for enterprise architecture modeling.
This guide introduces ArchiMate views, explains their role in modeling enterprise architecture, outlines the 23 official example viewpoints grouped into basic, motivation, strategy, and implementation & migration categories, and provides detailed descriptions of basic viewpoints such as composition, support, collaboration, and implementation.
This article provides a detailed introduction to software architecture, covering its definition, essential concepts such as systems, subsystems, modules, components, and frameworks, various architectural layers and classifications, evolution from monolithic to micro‑service designs, common pitfalls, evaluation criteria, and recommended learning resources.
This article explains the fundamental concepts of software architecture, distinguishing it from frameworks, defining system, subsystem, module, and component, outlining the four core aspects of architecture, and detailing the various layers such as business, application, data, code, technical, and deployment architectures.
The article explains the concept of technical architecture, defines enterprise technology architecture (ETA) as reusable standards and guidelines, describes how to initiate ETA development, and outlines key organizational concepts such as technical domains, patterns, and services, emphasizing the need for an end‑to‑end view.
The article explains enterprise business architecture (EBA) as a bridge between business models and strategy, outlines what EBA is not, describes its four dimensions—people, finance, process, and organization—lists key influencing factors, and shows how EBA integrates with the broader enterprise context and business architecture.
This article explains the fundamental concepts of software architecture—including systems, subsystems, modules, components, frameworks, and architecture itself—by defining each term, illustrating their relationships with real‑world examples, and clarifying common misconceptions for technical professionals.
This article shares a comprehensive PPT from the 2018 Domain-Driven Design China Summit, offering valuable insights and practical guidance for mastering DDD, a pivotal approach to software architecture and domain modeling in modern development.
This article explores the evolution of software development—from machine language and assembly to high‑level languages—examines the two software crises that spurred structured and object‑oriented programming, and explains how software architecture emerged to manage system scale, coupling, and complexity.
This article explains the evolution of software development from machine code to high‑level languages, describes the two software crises that led to structured programming and OOP, and defines software architecture as the top‑level structure that manages system complexity through clear components, modules, and rules.
This article demystifies software architecture by defining systems, subsystems, modules, components, and frameworks, illustrating their relationships with real‑world examples and diagrams, and proposing a concise definition of architecture as the top‑level structure of a software system.
This article breaks down the concept of system architecture, derives a concise formula—elements plus connections plus solving specific problems—and explores its classifications, characteristics, and practical implications for designing coherent, goal‑oriented software systems.
Software architecture defines the overall structure and components of a system, guiding design decisions, balancing performance, scalability, and maintainability, while fostering team alignment through clear standards and abstractions, and the article outlines its purpose, best practices, evaluation criteria, and a path to becoming an architect.
This article explores the role of software architects, outlining their responsibilities, essential qualities, differences between internet and traditional enterprises, team dynamics, common optimization practices, and practical advice on growing into an architect and advancing your career.
The author reflects on his journey from developer to software architect, arguing that architecture must be accessible to programmers, integrated with agile practices, and guided by lightweight, incremental methods that balance theoretical rigor with practical, real‑world solutions.
The article explains software architecture as a top‑down, macro view of systems—covering business decomposition, domain modeling, technical and system design, deployment considerations, and the skills architects need to create scalable, maintainable solutions.
This article outlines a comprehensive series that guides developers and aspiring architects through the fundamentals, career path, modeling techniques, design patterns, deployment strategies, and real‑world case studies of software architecture, offering a step‑by‑step roadmap for growth.
Software architecture is described as a set of critical decisions about system organization, including the selection of components, their interfaces, and collaborative behavior, and as a compositional style that progressively assembles these elements into larger subsystems, a definition comprehensively presented by Booch, Rumbaugh, and Jacobson in the UML User Guide.
