Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- en:modul:m321_aws:topics:01 [2025/08/13 16:59] – angelegt dgaravaldi
+++ en:modul:m321_aws:topics:01 [2025/08/13 17:35] (aktuell) – dgaravaldi
@@ Zeile 1: / Zeile 1: @@
 ===== Centralized vs Distributed System Architecture  =====
+\\
+{{:en:modul:m321_aws:topics:cs_vs_ds.png?600|Fig-01: Centralized vs Distributed System Architecture}}
+\\
 \\
 ==== Centralized System Architecture  ====
 A centralized system architecture refers to a computing architecture where all or most of the processing, data storage, and management are performed by a single central server or a mainframe. This central entity is responsible for handling all requests and serving all client devices connected to it. Here are the main characteristics and components of a centralized system architecture:
+\\
 === Characteristics ===
-- **Single Point of Control**: All processing, data storage, and management are handled by a central server or mainframe.
+  * **Single Point of Control**: All processing, data storage, and management are handled by a central server or mainframe.
-- **Tight Integration**: Components are closely integrated, typically within a single physical location.
+  * **Tight Integration**: Components are closely integrated, typically within a single physical location.
-- **Simplified Management**: Easier to administer, update, maintain, and back up since all resources are centralized.
+  * **Simplified Management**: Easier to administer, update, maintain, and back up since all resources are centralized.
-- **Scalability Constraints**: Limited by the capacity of the central server; scaling often requires upgrading the central server's hardware.
+  * **Scalability Constraints**: Limited by the capacity of the central server; scaling often requires upgrading the central server's hardware.
-- **Reliability Issues**: System depends heavily on the central server; a failure in the central server can make the entire system unavailable.
+  * **Reliability Issues**: System depends heavily on the central server; a failure in the central server can make the entire system unavailable.
-- **Performance**: Can be fast for small-scale operations due to reduced network latency and overhead within the local environment.
+  * **Performance**: Can be fast for small-scale operations due to reduced network latency and overhead within the local environment.
 === Components ===
@@ Zeile 19: / Zeile 22: @@
 === Examples ===
-- Mainframe systems
+  * Mainframe systems
-- Client-server architecture
+  * Client-server architecture
-- Single data center cloud computing
+  * Single data center cloud computing
+\\
-<a id=distributed-system-architecture></a>
+\\
 ==== Distributed System Architecture ====
 A distributed system architecture refers to multiple independent components (or nodes) work together to appear as a single coherent system to the end-users. These components are spread across different physical or virtual machines.
@@ Zeile 29: / Zeile 32: @@
 === Characteristics ===
-- **Multiple Points of Control**: Processing and data storage are spread across multiple independent nodes or servers.
+  * **Multiple Points of Control**: Processing and data storage are spread across multiple independent nodes or servers.
-- **Loose Integration**: Components are often geographically dispersed and communicate over a network.
+  * **Loose Integration**: Components are often geographically dispersed and communicate over a network.
-- **Complex Management**: Requires more sophisticated coordination, synchronization, and administration.
+  * **Complex Management**: Requires more sophisticated coordination, synchronization, and administration.
-- **Scalability**: Can scale horizontally by adding more nodes to the system, making it suitable for large-scale operations.
+  * **Scalability**: Can scale horizontally by adding more nodes to the system, making it suitable for large-scale operations.
-- **Reliability**: More fault-tolerant; failure of one node does not necessarily bring down the entire system.
+  * **Reliability**: More fault-tolerant; failure of one node does not necessarily bring down the entire system.
-- **Performance**: Can handle large-scale operations more effectively by distributing the load; network latency and communication overhead can be a challenge.
+  * **Performance**: Can handle large-scale operations more effectively by distributing the load; network latency and communication overhead can be a challenge.
 === Components ===
@@ Zeile 44: / Zeile 47: @@
 === Examples ===
-- Internet services (e.g., Google, Facebook)
+  * Internet services (e.g., Google, Facebook)
-- Peer-to-peer networks
+  * Peer-to-peer networks
-- Distributed databases (e.g., Apache Cassandra, Amazon DynamoDB)
+  * Distributed databases (e.g., Apache Cassandra, Amazon DynamoDB)
-- Cloud computing (multi-data center)
+  * Cloud computing (multi-data center)
+\\
+\\
 ==== Comparison ====
+| Feature                | Centralized System                      | Distributed System                       |
-| Feature          | Centralized System                      | Distributed System                       |
+|------------------------|-----------------------------------------|------------------------------------------|
-|------------------|-----------------------------------------|------------------------------------------|
+| **Control**            | Single central server                   | Multiple independent nodes               |
-| **Control**      | Single central server                   | Multiple independent nodes               |
+| **Integration**        | Tight integration, often local          | Loose integration, often geographically dispersed |
-| **Integration**  | Tight integration, often local          | Loose integration, often geographically dispersed |
+| **Management**         | Simplified management                   | Complex management                       |
-| **Management**   | Simplified management                   | Complex management                       |
+| **Scalability**        | Vertical scaling (hardware upgrades)    | Horizontal scaling (adding nodes)        |
-| **Scalability**  | Vertical scaling (hardware upgrades)    | Horizontal scaling (adding nodes)        |
+| **Reliability**        | Single point of failure                 | Fault-tolerant, no single point of failure|
-| **Reliability**  | Single point of failure                 | Fault-tolerant, no single point of failure|
+| **Performance**        | Low latency in small-scale operations   | High performance for large-scale operations; may face network latency |
-| **Performance**  | Low latency in small-scale operations   | High performance for large-scale operations; may face network latency |
+| **Examples**           | Mainframes, client-server systems       | Internet services, peer-to-peer networks, cloud computing |
-| **Examples**     | Mainframes, client-server systems       | Internet services, peer-to-peer networks, cloud computing |
-{{:en:modul:m321_aws:learningunits:lu02:cs_vs_ds.png?600|Fig-01: Centralized vs Distributed System Architecture}}
-{{:en:modul:m321_aws:lu02:cs_vs_ds.png?600|Fig-01: Centralized vs Distributed System Architecture}}
 In summary, centralized systems are simpler to manage and more straightforward in design but face challenges in scalability and reliability. Distributed systems offer better scalability and fault tolerance but are more complex to design, implement, and manage.