# Internet Architecture Published articles for Internet Architecture. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## What N, N+1, 2N, and 2(N+1) Mean in a Data Center DevFeed: [What N, N+1, 2N, and 2(N+1) Mean in a Data Center]() Original publisher: [Read original article]() Author: j2sw Published: 2026-08-27T13:59:08Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [datacenter](), [data]() Tags: [2n-redundancy](), [capacity](), [colocation](), [components](), [cooling](), [data-center](), [data-center-power](), [equipment](), [internet-architecture](), [maintenance](), [n-plus-1-redundancy](), [network-operations](), [power-distribution](), [system](), [ups]() ### AI overview This article explains what data center redundancy ratings N, N+1, N+2, 2N, and 2(N+1) indicate about component capacity, failures, maintenance, cooling, and alternate paths. ### Source excerpt Have you ever looked at a data center marketing slick and wondered what N, N+1, 2N, and 2(N+1) actually mean? The main thing they tell you is how many components can fail before the system drops below the capacity needed to support the load. When I evaluate a data center, I want to know what ... Read more The post What N, N+1, 2N, and 2(N+1) Mean in a Data Center appeared first on Justin Wilson (j2sw). ## Multi-Core Fiber: Several Optical Cores Inside One Strand DevFeed: [Multi-Core Fiber: Several Optical Cores Inside One Strand]() Original publisher: [Read original article]() Author: j2sw Published: 2026-08-18T13:39:00Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [Hardware](), [Networks](), [interface]() Tags: [400g](), [cabling](), [channel](), [connectors](), [data-center](), [fiber](), [fiber-optics](), [internet-architecture](), [multi-core-fiber](), [network-engineering-resources](), [networks](), [optical-networking](), [optics](), [space-division-multiplexing](), [transmission]() ### AI overview This article explains how multi-core fiber places several optical cores inside one standard 125-micron cladding. It distinguishes MCF from high-fiber-count cable, describes aggregate capacity using separate channels and space-division multiplexing, and explains the need for specialized optical interfaces, connectors, splicing, and testing. ### Source excerpt Multi-core fiber places several independent optical cores inside one standard 125-micron cladding. It increases channel density, but it also requires different connectors, splicing methods, and testing procedures. The post Multi-Core Fiber: Several Optical Cores Inside One Strand appeared first on Justin Wilson (j2sw). ## Using Cisco Prefix Lists Inside Route Maps for BGP Filtering DevFeed: [Using Cisco Prefix Lists Inside Route Maps for BGP Filtering]() Original publisher: [Read original article]() Author: j2sw Published: 2026-08-11T14:48:44Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [BGP](), [Cisco](), [Network]() Tags: [bgp](), [bgp-filtering](), [cisco](), [internet-architecture](), [network-engineering](), [network-engineering-resources](), [prefix-lists](), [route-maps](), [routing-policy]() ### AI overview This tutorial explains how Cisco prefix lists and route maps work together for BGP filtering. Prefix lists define which routes match, while route maps apply actions such as permitting, denying, or modifying route attributes. It also describes route-map sequence order and implicit deny behavior. ### Source excerpt Prefix lists define which BGP routes match a policy. Route maps use those matches to permit routes, deny them, or change attributes such as local preference. The post Using Cisco Prefix Lists Inside Route Maps for BGP Filtering appeared first on Justin Wilson (j2sw). ## Understanding BGP Route Types: Full Routes vs Partial vs Default vs Customer Routes DevFeed: [Understanding BGP Route Types: Full Routes vs Partial vs Default vs Customer Routes]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-24T16:28:00Z Content type: article Language: en Sources: [Justin Wilson (j2sw)]() Topics: [BGP](), [networking](), [Routing (disambiguation)](), [Internet](), [gateway](), [Networks]() Tags: [bgp](), [cpu](), [flexibility](), [internet-architecture](), [isp](), [memory](), [network-engineering](), [network-operations](), [route](), [router](), [routing](), [routing-policy](), [routing-table](), [traffic-engineering](), [visibility]() ### AI overview This article explains BGP route choices, comparing default routes, full routes, partial routes, and customer routes. It describes the tradeoffs between small routing tables, Internet visibility, traffic engineering control, and router resource requirements. ### Source excerpt 5 minute read time.Justin Wilson j2sw.com When you configure a BGP session, one of the first questions is what routes you actually want to receive. If you have ever filled out a questionnaire with Hurricane Electric or another transit provider, they ask you what "kind" of routes you want. In this article, I plan to ... Read more The post Understanding BGP Route Types: Full Routes vs Partial vs Default vs Customer Routes appeared first on Justin Wilson (j2sw). ## How Passive Optical Networks (PON) Work DevFeed: [How Passive Optical Networks (PON) Work]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-22T12:35:00Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [Networks](), [gpon](), [Internet](), [Ethernet](), [gateway](), [Security](), [Deployment]() Tags: [ethernet](), [fiber](), [ftth](), [gateway](), [gpon](), [internet](), [internet-architecture](), [isp](), [networks](), [passive-optical-network](), [pon](), [providers](), [provisioning](), [router](), [security](), [xgs-pon]() ### AI overview This tutorial explains how Passive Optical Networks (PON) deliver residential fiber Internet. It describes the roles of the OLT, passive optical splitters, ONTs, and the customer router or gateway, including how providers share feeder fiber among subscribers and provision authorized ONTs. ### Source excerpt If you've spent any time looking into fiber Internet, you've probably run across terms like GPON, XGS-PON, OLT, and ONT. These are all parts of what's called a Passive Optical Network, or PON. Most residential fiber providers use PON because it lets them connect alot of homes without having to pull a separate fiber from ... Read more The post How Passive Optical Networks (PON) Work appeared first on Justin Wilson (j2sw). ## Fat Rail vs Thin Rail in AI compute clusters DevFeed: [Fat Rail vs Thin Rail in AI compute clusters]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-01T07:30:18Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [Artificial Intelligence](), [Job](), [datasets]() Tags: [400g](), [ai](), [cluster](), [clusters](), [compute](), [data](), [fabric](), [fat-rail](), [internet-architecture](), [switching](), [thin-rail]() ### AI overview The article explains "fat" and "thin" rails in AI compute clusters. The terms describe whether a node's connection to the fabric provides sufficient bandwidth for the workload, with the practical distinction determined by node-to-node traffic rather than cable count alone. ### Source excerpt We are starting to hear about "Thin" and "Fat" rails in AI fabrics. These are just another way to say a connection from compute into the Fabric. The link either has sufficient capacity (Fat) or insufficient capacity (Thin). A thin rail provides the node with a single path into the fabric. That may be one ... Read more The post Fat Rail vs Thin Rail in AI compute clusters appeared first on Justin Wilson (j2sw). ## George Washington, the Delaware, and Direct Routes DevFeed: [George Washington, the Delaware, and Direct Routes]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-30T16:15:53Z Content type: opinion Language: en Sources: [Justin Wilson (j2sw)]() Topics: [Network design](), [Networks](), [BGP](), [Network]() Tags: [bgp](), [blog](), [fd-ix](), [internet-architecture](), [ixp](), [network-design](), [network-peering](), [networks](), [peering](), [route](), [routers](), [routing](), [traffic](), [transit]() ### AI overview This commentary compares George Washington's direct route across the Delaware with network peering. It argues that direct connections between networks can reduce transit dependencies, router hops, and latency compared with longer BGP-selected transit paths. ### Source excerpt I originally posted this over on the FD-IX Bloghttps://blog.fd-ix.com/george-washington-the-delaware-and-direct-routes/ When George Washington crossed the Delaware River on Christmas night in 1776, the goal was simple. Reach the objective by the most effective path while avoiding unnecessary delays and giving the opposing force as little warning as possible. The crossing was risky, but it created a ... Read more The post George Washington, the Delaware, and Direct Routes appeared first on Justin Wilson (j2sw). ## HTTP 206 Partial Content Explained DevFeed: [HTTP 206 Partial Content Explained]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-26T11:37:15Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [HTTP](), [client](), [browser](), [file](), [servers](), [Cache]() Tags: [browser](), [cache](), [cdn](), [client](), [file](), [http](), [http-206](), [http-codes](), [internet-architecture](), [large-files](), [range](), [request](), [server](), [video](), [web-servers](), [web-troubleshooting]() ### AI overview This tutorial explains HTTP 206 Partial Content, a successful response used when a client requests only part of a file or other resource. It describes byte-range requests, the Range and Content-Range headers, and uses such as video playback, resumable downloads, and cache or CDN handling. ### Source excerpt A browser does not always need the whole file at once. Sometimes it only needs a slice of the file. That slice might be the next part of a video or a chunk of a large object sitting behind a CDN. When that happens, the client can request a byte range instead of requesting the ... Read more The post HTTP 206 Partial Content Explained appeared first on Justin Wilson (j2sw). ## Sam's First Visit to An Internet Exchange DevFeed: [Sam's First Visit to An Internet Exchange]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-25T03:54:15Z Content type: release Language: en Sources: [Justin Wilson (j2sw)]() Topics: [networking](), [Networks](), [Internet Traffic](), [BGP]() Tags: [bgp](), [book](), [books](), [children](), [explainer](), [fiber](), [internet](), [internet-architecture](), [internet-exchange](), [internet-traffic](), [ix](), [ixp](), [j2-updates](), [j2sw](), [justin-wilson](), [network-engineering-resources](), [networking](), [networks](), [peering](), [router](), [sam](), [stem-book](), [traffic]() ### AI overview Justin Wilson announces A Kid's First Visit to An Internet Exchange, a children's picture book in which Sam learns how networks connect, peer, and move Internet traffic. The book is available in Kindle and paperback editions. ### Source excerpt Justin Wilson announces his second children's networking book, A Kid's First Visit to an Internet Exchange. Follow Sam as he learns how networks meet, peer, and move Internet traffic. The post Sam's First Visit to An Internet Exchange appeared first on Justin Wilson (j2sw). ## Data Center Fabrics High Level Overview DevFeed: [Data Center Fabrics High Level Overview]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-17T12:30:00Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [data centers](), [Network architectures](), [networking](), [Latency]() Tags: [architecture](), [data-center](), [ecmp](), [internet-architecture](), [latency](), [leaf-switch](), [network](), [servers](), [spine-switch](), [storage](), [vxlan]() ### AI overview This article explains data center fabrics as networks that connect servers, storage systems, and other network devices. It describes the common leaf-and-spine architecture, the roles of leaf and spine switches, packet movement, and how multiple paths provide bandwidth and predictable latency. ### Source excerpt A data center fabric connects servers, storage, and network devices using a leaf-spine architecture designed for high bandwidth and predictable latency. Learn how packets move through a fabric, why ECMP matters, and how modern data centers support virtualization, cloud, and AI workloads. The post Data Center Fabrics High Level Overview appeared first on Justin Wilson (j2sw).