TypeScript

The Supervisor-Worker pattern delegates complex or potentially blocking tasks to worker threads, preventing the main thread from freezing and maintaining responsiveness. A supervisor thread manages the workers, distributing work and collecting results. This is particularly useful in TypeScript/JavaScript environments …

Read More

The Master-Slave pattern distributes work to multiple worker nodes (slaves) from a central coordinator (master). The master manages the tasks and distributes them, while the slaves execute the tasks and return results. This example uses TypeScript’s asynchronous programming features (Promises and async/await) to …

Read More

The Publish-Subscribe (PubSub) pattern decouples message publishers from message subscribers. Publishers (or topics) don’t know who their subscribers are, and subscribers only know about topics they’re interested in, not who is publishing. This allows for loose coupling and scalability.

The code implements …

Read More

The Blackboard pattern is a computational architecture where multiple independent knowledge sources (agents) collaborate to solve a complex problem. A central data structure, the “blackboard,” holds the problem state, and agents react to changes on the blackboard, modifying it to move closer to a solution. …

Read More

The Pipes and Filters pattern structures a program as a sequence of processing stages (filters), each performing a distinct operation on the input data. Data flows through this “pipeline,” with each filter receiving input from the previous one and passing its output to the next. This promotes modularity, …

Read More

The Cluster-based Architecture pattern distributes processing across multiple worker processes (clusters) to improve performance and reliability, particularly in single-threaded environments like Node.js/TypeScript. It leverages multi-core processors. This example uses Node’s cluster module to create a simple HTTP …

Read More

The Shared-Nothing pattern promotes scalability and resilience by avoiding shared state between components. Each component has its own private data and communicates with others via explicit message passing (typically function calls with data transfer). This eliminates contention points like locks, often found in …

Read More

The Message Broker pattern decouples application components by enabling them to communicate via messages. Components don’t need to know about each other directly; they interact through a central message broker. This promotes scalability, flexibility, and resilience.

This TypeScript implementation uses a simple …

Read More

The Space-Based Architecture pattern organizes code into independent, self-contained “spaces” that communicate via well-defined interfaces (often events or messages). This promotes loose coupling, making the system more modular, testable, and easier to evolve. Each space encapsulates specific functionality …

Read More

The Event-Driven Architecture (EDA) decouples 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 flexibility.

This …

Read More