<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Topology on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/topology/</link><description>Recent content in Topology on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Wed, 06 Nov 2024 00:00:00 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/topology/atom.xml" rel="self" type="application/rss+xml"/><item><title>Several Common Network Topology Structures</title><link>https://www.chenshaowen.com/en/blog/common-network-topology.html</link><pubDate>Wed, 06 Nov 2024 00:00:00 +0000</pubDate><atom:modified>Wed, 06 Nov 2024 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/common-network-topology.html</guid><description>1. Fat-Tree In 1985, Charles E. Leiserson of MIT invented the Fat-Tree network. As shown in the figure below, a fat-tree network is a binary tree in which bandwidth gradually increases from the root nodes down to the leaf nodes.
In August 2008, a group of computer scientists at UC San Diego published a scalable network architecture design that adopted a topology inspired by the fat-tree topology, achieving better scalability than previous hierarchical networks.</description><dc:creator>WeChat Official Account</dc:creator><category>AI</category><category>Network</category><category>Topology</category><category>Operations</category><category>Learning</category><category>Data Center</category><category>Fat-Tree</category></item><item><title>Evolution of Kubernetes Under Multiple Locations</title><link>https://www.chenshaowen.com/en/blog/evolution-of-kubernetes-under-multipl-location.html</link><pubDate>Sat, 18 Jun 2022 12:09:53 +0000</pubDate><atom:modified>Sat, 18 Jun 2022 12:09:53 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/evolution-of-kubernetes-under-multipl-location.html</guid><description>1. Application Architecture Matches Business Growth and Operations Capability At industry conferences, in documents and blogs, we constantly see all kinds of excellent solutions — but if you copy them straight into your own business, you keep hitting walls. Because these technical solutions were incubated in specific business scenarios; different business forms, different business scales, and different stages of business development all affect how technology lands.</description><dc:creator>WeChat Official Account</dc:creator><category>Multi-Location</category><category>Kubernetes</category><category>Architecture</category><category>Topology</category><category>Operations</category></item></channel></rss>