JavaScript

The Supervisor-Worker pattern delegates computationally intensive or blocking tasks to worker threads, preventing the main thread from freezing and maintaining a responsive user interface. A supervisor manages the workers, distributing tasks and collecting results. This example uses web workers in JavaScript. The …

Read More

The Master-Slave pattern involves one object (the Master) controlling and coordinating the actions of one or more other objects (the Slaves). The Master delegates tasks to the Slaves, and the Slaves provide results back to the Master. This allows for parallel processing or distribution of work. The JavaScript …

Read More

The Publish-Subscribe (Pub/Sub) pattern enables decoupling of message producers (publishers) from message consumers (subscribers). Publishers emit events without knowing who, if anyone, is listening. Subscribers express interest in specific events and receive notifications when those events occur. This promotes loose …

Read More

The Blackboard pattern is a computational problem-solving approach where multiple independent knowledge sources (agents) operate on a shared data structure (the blackboard) to collectively solve a complex problem. Each agent recognizes patterns in the blackboard’s state and contributes relevant information, …

Read More

The Pipes and Filters pattern structures an application as a series of processing elements (filters) connected by channels (pipes) through which data flows. Each filter performs a specific, self-contained transformation on the data. This promotes modularity, reusability, and ease of maintenance as filters can be added, …

Read More

The Cluster-based Architecture pattern divides a larger task into smaller, independent “clusters” of work. Each cluster can be handled by a separate worker or process, improving responsiveness and allowing for parallel execution. This example simulates worker clusters using JavaScript’s worker_threads …

Read More

The Shared-Nothing pattern aims for scalability and concurrency by avoiding shared state between processing units. Each unit operates on its own private data and communicates results through passing messages or using a central aggregator. This eliminates the need for locks or other synchronization mechanisms, reducing …

Read More

The Message Broker pattern decouples application components by enabling them to communicate through intermediary message queues. Components (producers) send messages to the broker without knowing who the consumers are, and consumers subscribe to specific message types to receive relevant updates. This promotes …

Read More

The Space-Based Architecture pattern organizes code into independent “spaces” (often modules or namespaces) that communicate via well-defined interfaces. This promotes modularity, reduces coupling, and allows for easier testing and maintenance. Each space encapsulates specific functionality and data, …

Read More

The Event-Driven Architecture (EDA) decouples software components by allowing them to communicate through events. Components (event producers) emit events without knowing who will handle them, and other components (event consumers) subscribe to events they’re interested in. This promotes scalability and …

Read More