Swift

The Master-Slave pattern (also known as Leader-Follower) involves one object (the Master) holding the primary data and logic, while other objects (the Slaves) maintain copies of that data and react to changes propagated from the Master. This ensures consistency across multiple views or components. Here, the Master …

Read More

The Publish-Subscribe (Pub/Sub) pattern decouples message senders (publishers) and message receivers (subscribers). Publishers don’t know who their subscribers are, and subscribers only know of the publishers, not how to access their data directly. A central message broker (often called a topic or event bus) …

Read More

The Blackboard pattern is a computational architecture for solving problems that involve multiple, independent knowledge sources. A central “blackboard” data structure holds the problem state, and “knowledge sources” observe the blackboard, triggering actions when their conditions are met. This …

Read More

The Pipes and Filters pattern breaks down a complex task into a series of independent, self-contained processing steps (filters) connected by channels (pipes) through which data flows. Each filter performs a specific transformation on the input data and passes the result to the next filter. This promotes modularity, …

Read More

The Cluster-based Architecture pattern organizes components into independent, interchangeable “clusters” each managing a specific aspect of the application. This promotes modularity, scalability, and easier maintenance. A central coordinator or manager (often a facade) interacts with these clusters, shielding the core …

Read More

The Shared-Nothing pattern aims for scalability and fault tolerance by distributing data and computation across multiple independent nodes, each with its own dedicated resources (CPU, memory, disk). There is no shared memory or storage between these nodes. Communication happens via message passing. This example …

Read More

The Message Broker pattern decouples application components by allowing them to communicate through intermediary message channels. Components don’t need to know about each other directly; they simply publish messages to the broker, and other components subscribe to the messages they’re interested in. This …

Read More

The Space-Based Architecture pattern decouples components of an application by using a central “space” (often a dictionary or similar data structure) to store and retrieve data. Components communicate by publishing and subscribing to changes within this space. This avoids direct dependencies and promotes …

Read More

The Event-Driven Architecture (EDA) decouples software components by allowing them to communicate through events. Components (event producers) emit events when something significant happens, and other components (event consumers) react to those events without needing to know who produced them. This promotes flexibility …

Read More

The Service-Oriented Architecture (SOA) pattern structures an application as a collection of loosely coupled, reusable services. Each service encapsulates a specific business function and communicates with others through well-defined interfaces (often network calls). This promotes modularity, maintainability, and …

Read More