Top 10 Software Architecture Patterns Explained with Pros & Cons

What Is an Architecture Pattern?

According to Wikipedia, an architecture pattern is a reusable solution to a frequently occurring problem within a given context in software architecture, similar to design patterns but with a broader scope.

The article briefly explains ten common architecture patterns, their usage scenarios, and their pros and cons.

Layered Pattern

Also known as multi‑layer architecture, it structures programs into hierarchical layers where each layer offers services to the one above. Typical four layers in information systems:

Presentation (UI) layer

Application (service) layer

Business logic (domain) layer

Data access (persistence) layer

Use cases: desktop applications, e‑commerce web applications.

Client‑Server Pattern

Consists of a server providing services to multiple clients, with the server continuously listening for requests. Use case: online applications such as email, file sharing, banking.

Master‑Slave Pattern

Involves a master component distributing work to slave components and aggregating their results. Use cases: database replication (master DB as authoritative source) and peripheral devices connected via a bus.

Pipe‑Filter Pattern

Builds systems that generate and process data streams, where each processing step is encapsulated in a filter and data flows through pipes. Use cases: compilers (lexical analysis, parsing, semantic analysis, code generation) and bioinformatics workflows.

Proxy Pattern

Used to construct distributed systems with decoupled components that communicate via remote service calls; a proxy coordinates communication. Use case: message broker software such as Apache ActiveMQ, Apache Kafka, RabbitMQ, JBoss Messaging.

Peer‑to‑Peer Pattern

Each component (peer) can act as both client and server, dynamically changing roles. Use cases: file‑sharing networks like Gnutella, multimedia protocols (P2PTV, PDTP), proprietary media apps like Spotify.

Event‑Bus Pattern

Handles events via four main components: event source, listener, channel, and event bus. Sources publish messages to channels; listeners subscribe to channels. Use cases: Android development, notification services.

Model‑View‑Controller (MVC) Pattern

Divides an interactive application into Model (core data and logic), View (user interface), and Controller (handles user input). Purpose: separate internal representation from presentation, enabling code reuse. Use cases: web application architectures in major programming languages, frameworks like Django and Rails.

Blackboard Pattern

Useful for problems without a predetermined solution strategy; consists of a global blackboard (shared memory), knowledge sources (modules), and a control component (selects and executes modules). Use cases: speech recognition, vehicle identification/tracking, protein structure recognition, sonar signal interpretation.

Interpreter Pattern

Designs components that interpret programs written in a specialized language, defining how to evaluate statements or expressions. Use cases: database query languages like SQL, communication protocol description languages.

Comparison of Architecture Patterns

The following summarizes the advantages and disadvantages of each pattern:

Layered: Pros – lower layers reusable, easier standardization, changes confined to a layer. Cons – not universally applicable; some layers may be skipped.

Client‑Server: Pros – clear service provision to users. Cons – each request handled in a separate server thread; inter‑process communication adds overhead.

Master‑Slave: Pros – accuracy by delegating tasks to diverse slaves. Cons – slaves isolated, latency in master‑slave communication, limited to decomposable problems.

Pipe‑Filter: Pros – enables concurrent processing, easy addition and reuse of filters, flexible pipeline composition. Cons – overall speed limited by the slowest filter; data conversion overhead between filters.

Proxy: Pros – dynamic addition, removal, relocation of objects; transparent deployment. Cons – requires standardized service descriptions.

Peer‑to‑Peer: Pros – supports distributed computing, robust fault handling, high scalability. Cons – no QoS guarantees, security challenges, performance depends on node count.

Event‑Bus: Pros – easy addition of publishers, subscribers, and connectors; effective for highly distributed apps. Cons – scalability may suffer as all messages share a single bus.

MVC: Pros – multiple views can share the same model, views can be attached/detached at runtime. Cons – adds complexity; may cause unnecessary UI updates.

Blackboard: Pros – simple addition of new applications; easy to extend data space structure. Cons – modifying data space structure is difficult and impacts all applications; may need synchronization and access control.

Interpreter: Pros – highly dynamic behavior, benefits end‑user programmability, easy to replace interpreter. Cons – interpreted languages are generally slower than compiled ones, affecting performance.

Source: https://www.cnblogs.com/IcanFixIt/p/7518146.html