Repos-que-me-gustan/devops-exercises
1
0
Fork 0
Code Pull Requests Activity

Add answer to Spine & Leaf network question (#410)

Browse Source
This commit is contained in:
sreguzzoni 2024-02-02 14:23:35 +01:00 committed by GitHub
parent 135000b5a9
commit c746d0f46d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -622,6 +622,14 @@ Throughput. To have good throughput, the upload stream should be routed to an un
<details>
<summary>Explain Spine & Leaf</summary><br><b>
"Spine & Leaf" is a networking topology commonly used in data center environments to connect multiple switches and manage network traffic efficiently. It is also known as "spine-leaf" architecture or "leaf-spine" topology. This design provides high bandwidth, low latency, and scalability, making it ideal for modern data centers handling large volumes of data and traffic.
Within a Spine & Leaf network there are two main tipology of switches:
* Spine Switches: Spine switches are high-performance switches arranged in a spine layer. These switches act as the core of the network and are typically interconnected with each leaf switch. Each spine switch is connected to all the leaf switches in the data center.
* Leaf Switches: Leaf switches are connected to end devices like servers, storage arrays, and other networking equipment. Each leaf switch is connected to every spine switch in the data center. This creates a non-blocking, full-mesh connectivity between leaf and spine switches, ensuring any leaf switch can communicate with any other leaf switch with maximum throughput.
The Spine & Leaf architecture has become increasingly popular in data centers due to its ability to handle the demands of modern cloud computing, virtualization, and big data applications, providing a scalable, high-performance, and reliable network infrastructure
</b></details>
<details>