Java

The Supervisor-Worker pattern distributes tasks to multiple worker threads managed by a supervisor thread. The supervisor maintains a work queue and assigns tasks to idle workers. This promotes concurrency and responsiveness by preventing the main thread from blocking on long-running operations.

The Java implementation …

Read More

The Master-Slave pattern distributes work to multiple worker nodes (slaves) from a central coordinator (master). The master assigns tasks, and slaves execute them, reporting results back to the master. This improves performance through parallelization. This Java example uses a simple thread-based implementation. The …

Read More

The Publish-Subscribe (Pub/Sub) pattern decouples message senders (publishers) from message receivers (subscribers). Publishers emit messages to a topic without knowing who, if anyone, is listening. Subscribers express interest in specific topics and receive messages published to those topics. This promotes loose …

Read More

The Blackboard pattern is a communication and coordination mechanism for independent knowledge sources (agents) to collaboratively solve a complex problem. A central data structure, the “blackboard,” holds the problem state, and agents react to changes on the board, contributing their expertise. This code …

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) that pass data from one filter to the next. Each filter performs a specific transformation on the data without knowing the source or destination of that …

Read More

The Cluster-based Architecture pattern distributes application logic and data across multiple independent computing nodes (a “cluster”) to improve availability, scalability, and performance. Tasks are divided and potentially replicated within the cluster. This example simulates a simple log processing …

Read More

The Shared-Nothing architecture is a distributed computing paradigm where each node in the system has its own private, dedicated resources – CPU, memory, and storage – and communicates with other nodes solely via explicit communication protocols (like network calls). It avoids shared resources to minimize contention …

Read More

The Message Broker pattern decouples application components by enabling asynchronous communication through a central message store. Components don’t directly interact; instead, they publish messages to the broker, and other components subscribe to receive messages of interest. This promotes scalability, …

Read More

The Space-Based Architecture pattern decouples application logic by using a shared, immutable context (the “space”) to pass data between components. Instead of direct dependencies, components register to receive notifications when data they’re interested in changes within the space. This promotes …

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) listen for these events and react accordingly, without needing direct knowledge of the producers. This …

Read More