From 137501a3815f968a4a77dbffdd6f59f509fcdaf7 Mon Sep 17 00:00:00 2001 From: John Carvalho <18273620+BitcoinErrorLog@users.noreply.github.com> Date: Wed, 9 Oct 2024 09:45:24 +0100 Subject: [PATCH] Delete App Architectures/3. Global Aggregators.md --- App Architectures/3. Global Aggregators.md | 10 ---------- 1 file changed, 10 deletions(-) delete mode 100644 App Architectures/3. Global Aggregators.md diff --git a/App Architectures/3. Global Aggregators.md b/App Architectures/3. Global Aggregators.md deleted file mode 100644 index cfe61e8..0000000 --- a/App Architectures/3. Global Aggregators.md +++ /dev/null @@ -1,10 +0,0 @@ -![[global_aggregator.png]] - -This architectural pattern implements a distributed system model centered around a global aggregation layer, eliminating the need to fetch data from a multitude (maybe thousands!) of homesevers by the client. The core component of this design is a centralized global aggregator that interfaces with multiple home servers, consuming events from each in a unified manner. - -Key features of this architecture include: - -1. **Centralized Event Processing:** The global aggregator serves as a single point of convergence for event streams originating from disparate home servers across the network. -2. **Policy-Driven Filtering:** The aggregators can optionally implement a configurable set of policies and filtering rules, allowing for dynamic event processing based on predefined criteria. -3. **Client Flexibility and Aggregator Choice:** Clients consume data from the global aggregator stream. However, if a client finds the enforced rules of one aggregator unsuitable, it retains the flexibility to switch to an alternative global aggregator that better aligns with its requirements or selectively look for the homeservers itself. -4. **Scalable Event Distribution:** By centralizing the aggregation process, this architecture facilitates efficient event distribution to multiple clients, potentially reducing redundant processing and network overhead. \ No newline at end of file