C++

The Supervisor-Worker pattern distributes tasks among a pool of worker threads managed by a supervisor thread. The supervisor assigns tasks from a queue to available workers, ensuring work is processed concurrently without overwhelming the system. This implementation uses a std::queue for task management and …

Read More

The Master-Slave pattern distributes work to multiple worker threads (slaves) from a central thread (master). The master typically manages a work queue and assigns tasks to available slaves. This improves performance by leveraging multi-core processors. Here, the master thread creates worker threads and pushes tasks …

Read More

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

Read More

The Blackboard pattern is a computational problem-solving technique where multiple independent knowledge sources (KSs) contribute to solving a problem via a shared data structure, the Blackboard. KSs ‘watch’ the Blackboard for changes that match their expertise, and when a match occurs, execute to modify the data …

Read More

The Pipes and Filters pattern is a design pattern where a series of processing units (filters) are connected by channels (pipes). Each filter performs a specific transformation on its input and passes the result to the next filter through a pipe. This promotes modularity, reusability, and simplifies complex processing …

Read More

The Cluster-based Architecture pattern organizes components into independent groups (“clusters”) to manage complexity and facilitate independent development, deployment, and scaling. Each cluster encapsulates related functionality and exposes a well-defined interface to other clusters. This promotes loose …

Read More

The Shared-Nothing architecture is a distributed computing model where each node in the system has its own private memory and storage, and communicates with other nodes via network messages. There is no shared memory or disk. This promotes scalability and fault tolerance as nodes are independent. This example …

Read More

The Message Broker pattern decouples application components by enabling them to communicate through intermediary message queues. Components, or “clients,” don’t directly call each other; instead, they publish messages to topics and subscribe to topics of interest. A central broker manages message …

Read More

The Space-Based Architecture pattern decouples the data structures used by a system from the algorithms that operate on that data. Instead of tightly coupling data and methods within classes (like traditional OOP), it focuses on representing data as a collection of “spaces” – contiguous memory blocks – and …

Read More

The Event-Driven Architecture (EDA) decouples software components by allowing them to communicate through events. Components don’t directly call each other; instead, they publish events, and other components subscribe to those events to react accordingly. This promotes flexibility and scalability.

This C++ …

Read More