From 511ed6bae1da0d794d01c500f1cb34c23be6cd45 Mon Sep 17 00:00:00 2001
From: mjkwiatkowski <mati.rewa@gmail.com>
Date: Sat, 4 Jul 2026 14:29:09 +0200
Subject: feat: finished section 4.2

---
 content/implementation.tex | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

(limited to 'content/implementation.tex')

diff --git a/content/implementation.tex b/content/implementation.tex
index 15a450e..ae100bd 100644
--- a/content/implementation.tex
+++ b/content/implementation.tex
@@ -94,9 +94,18 @@ Should anything unusual occur, the \code{Monitoring Service} notifies the \code{
 Then, the \code{Analytics Engine}, ingests the data from the \code{Redis} stream (\myCircled{5}) and analyzes it for further insights.
 All insights generated in this way, are sent to the \code{HTTP Server} (\myCircled{4}) to communicate to the system knobs within the datacenter and to the datacenter operators (\grayCircled{1}).
 
+
 \begin{figure}[t]
 	\input{sources/listing_schema.tex}
 \end{figure}
 
-\input{sources/listing_sinks.tex}
+Of significant importance are data flows (\myCircled{2}) and (\myCircled{3}).
+Due to the massive volume of data incoming from the physical datacenter, the \code{Redis} sink (\myCircled{2}) has been configured to filter out relevant packets.
+\code{Kafka} comes with excellent capability to efficiently compare data packets against a condition and filter our packets that are of no use to the \code{Analytics Engine} (see \Cref{lst:redis-sink}).
+On the contrary, the \code{PostgreSQL} sink (\myCircled{3}) contains all metrics collected by the datacenter sensors (see \Cref{lst:postgresql-sink}).
+This setup achieves excellent abstraction level, because only the most important metrics are forwarded to the \code{Analytics Engine}, with the majority of packets being filtered out.
+
+\begin{figure}[t]
+	\input{sources/listing_sinks.tex}
+\end{figure}
 \section{Programming Effort}\label{ss:programming}
-- 
cgit v1.2.3

