Loading field map
Software architecture emerged as a distinct subfield in the late 1960s and 1970s, separating high-level design concerns from coding details. The foundational paradigm was Structured Design, which advocated for decomposing systems into hierarchical modules with clear interfaces to manage complexity, emphasizing principles like cohesion and coupling. This era established architecture's core purpose: to reason about system properties through deliberate structural choices.
The 1980s and 1990s saw the rise of the Object-Oriented Architecture paradigm, which shifted the unit of decomposition from functions to objects encapsulating data and behavior. This supported modeling real-world domains and promoted reuse through inheritance and polymorphism. Concurrently, the Component-Based Architecture paradigm gained prominence, focusing on larger-grain, independently deployable units with explicit dependencies and contracts, enabling the assembly of systems from pre-built parts, often within standardized middleware frameworks.
As systems became more distributed and interconnected, architectural thinking turned towards integration and interoperability. The Service-Oriented Architecture (SOA) paradigm, prominent in the 2000s, organized systems as collections of loosely coupled, coarse-grained services communicating via standard protocols, aiming for business agility and reuse across organizational boundaries. This represented a shift towards architecture as an orchestration of networked capabilities.
The 2010s brought a reaction to the complexity and centralization often associated with SOA, leading to the Microservices Architecture paradigm. This approach structures an application as a suite of small, independently deployable services built around business capabilities, with decentralized governance and data management. It is closely allied with Cloud-Native Architecture, a paradigm that fully embraces elastic, scalable, and resilient design patterns intrinsic to dynamic cloud environments, such as containerization and declarative infrastructure.
Throughout this evolution, enduring schools like Event-Driven Architecture and Data-Centric Architecture have persisted, focusing on the flow of events or the central role of data models as the primary organizing principle. The field continues to balance the tension between global conceptual integrity and decentralized autonomy, with current discourse often exploring paradigms for intelligent, adaptive systems and the architectural implications of machine learning components.