Dart

The Master-Slave pattern (also known as Leader-Follower) involves one object (the Master) holding the primary data and control, while other objects (the Slaves) synchronize their state with the Master. Changes are made to the Master, and these changes are then propagated to the Slaves. This ensures data consistency …

Read More

The Publish-Subscribe (Pub/Sub) pattern decouples message senders (publishers) from message receivers (subscribers). Publishers don’t know who their subscribers are, and subscribers only know of the publishers, not how to directly interact with them. 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 shared data structure, the “blackboard,” holds the problem state. Knowledge sources (independent modules) observe the blackboard and, when their conditions are met, execute to …

Read More

The Pipes and Filters pattern breaks down a complex processing task into a series of independent, reusable processing steps (filters) connected by channels (pipes). Each filter takes data, transforms it, and passes the result to the next filter. This promotes modularity, maintainability, and testability.

This Dart …

Read More

The Cluster-based Architecture pattern distributes workload across a group of identical worker nodes (clusters) to improve performance, scalability, and fault tolerance. Each cluster performs the same tasks independently, allowing for parallel processing. A central dispatcher (or load balancer) routes requests to …

Read More

The Shared-Nothing pattern emphasizes independent processes that don’t share any global state. Each process has its own dedicated resources – memory, disk – and communicates exclusively through message passing. This avoids contention and simplifies concurrency.

This Dart example models a simple distributed counter …

Read More

The Message Broker pattern decouples application components by enabling them to communicate through intermediary message channels (brokers). Components, termed publishers and subscribers, don’t need to know about each other directly. Publishers send messages to the broker, and subscribers receive messages they’ve …

Read More

The Space-Based Architecture pattern decouples an application into independent, self-contained “spaces” that communicate via messages. Each space manages its own state and logic, reducing global state and improving modularity. This implementation uses Dart’s StreamController to create these spaces and message passing. …

Read More

The Event-Driven Architecture (EDA) decouples components by having them communicate through events. Components (event producers) emit events when something significant happens, and other components (event consumers) react to those events without needing direct knowledge of the producers. This promotes flexibility and …

Read More

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

Read More