From d346ec4f9706a854d7c4f9f7eca0e695cadcd5a1 Mon Sep 17 00:00:00 2001 From: Lars Simon Winzer Date: Mon, 9 Mar 2026 18:30:08 +0100 Subject: [PATCH] Add: Blog to cover networking in its entirety --- documents/docs/blog/09-03-26_Network.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 documents/docs/blog/09-03-26_Network.md diff --git a/documents/docs/blog/09-03-26_Network.md b/documents/docs/blog/09-03-26_Network.md new file mode 100644 index 0000000..c83c7a1 --- /dev/null +++ b/documents/docs/blog/09-03-26_Network.md @@ -0,0 +1,21 @@ +# Table of Contents + + +# Basics +## Formal concepts of networking +Whenever you want to access the same data on different devices without carrying it (the data) from device to device, with, let’s say, a thumb drive, you have multiple options for achieving this. + +![Peer To Peer Versus Client-Server Architecture](/documents/images/docs/blog/09-03-26_Network/shared_ressouce_possible_approaches.svg) + + + +**Peer to Peer** enables users to share content (files, messages, ...). +While it does not rely on a central server, it comes with the big trade-of that the device storing the data you want to access has to be reachable and online. +Today Peer to Peer is still widely used with VoIP and decentralized networks for censorship-resistant transactions formaly known as the blockchain. + +The **Client-Server** model evolved into the sophisticated "web-services" we know and use daily. +One central powerful computer (the server) stores data and allows external devices (clients) to access it. + +For our course "Programmierprojekt" we are required to use the Client-Server model.