Architectural Patterns

• Pattern-Oriented Software Architecture, Volume 1 by Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, and Michael Stal (POSA 1)
• Pattern-Oriented Software Architecture, Volume 2: Patterns for Concurrent and Networked Objects) by Douglas C. Schmidt, Michael Stal, Hans Rohnert, and Frank Buschmann  (POSA 2)
• Pattern-Oriented Software Architecture, Volume 3: Patterns for Resource Management by Michael Kirchner, and Prashant Jain (POSA 3)
  
• Pattern-Oriented Software Architecture, Volume 4: A Pattern Language for Distributed Programming by Frank Buschmann, Kevlin Henney, and Douglas C. Schmidt (POSA 4)
  
• Pattern-Oriented Software Architecture, Volume 5: Patterns and Pattern Language by Frank Buschmann, Kevlin Henney, and Douglas C. Schmidt (POSA 5)

I will present in my posts seven very often used architectural patterns: Layers, Pipes-and-Filters, Broker, Model-View-Controller (MVC), Reactor, Active Object, and Monitor Object.

POSA 1 provides the first classification:

From Mud to Structure

These patterns provide a controlled decomposition of an overall system task into cooperating subsystems.

• Layers: Split a task into layers. Each layer has a specific responsibility and provides a service to a higher layer.
• Pipes and Filters: Decompose a task that performs complex processing into a series of separate elements that can be reused. This can improve performance, scalability, and reusability by allowing task elements that perform the processing to be deployed and scaled independently. (https://docs.microsoft.com/en-us/azure/architecture/patterns/pipes-and-filters)

Distributed Systems

Build systems whose components are located in different processes or address spaces.

• Broker: Structures distributed software systems that interact with remote service invocations. It is responsible for coordinating the communication, its results, and exceptions.

Interactive Systems

Build a system with human-computer interaction.

• Model-View-Controller (MVC): Divides the program logic of a user interface into the separate components model, view, and controller. The model manages the data and rules of the application. The view represents the data, and the controller interacts with the user.

POSA 2 added further classifications:

Event Demultiplexing and Dispatching

Initiate, receive, demultiplex, and dispatch events in distributed and network systems.

• Reactor: An event-driven application that can accept multiple client requests simultaneously and distribute them to different service providers.

Concurrency Patterns

Addresses concurrency architecture and design issues for components, subsystems, and applications.

• Active Object: Separates the method execution from the method call.
• Monitor Object: Synchronizes access to an object so that only one member function can be executed at any time.

What’s Next?

After this overview of the POSA books and their pattern, I will present the architectural pattern Layers in my next post.

{module title=”Marketing”}