<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on LeanerCloud</title><link>https://leanercloud.com/tags/networking.html</link><description>Recent content in Networking on LeanerCloud</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 20 Aug 2026 02:08:40 +0200</lastBuildDate><atom:link href="https://leanercloud.com/tags/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>The cross-AZ data transfer costs hiding in your database traffic</title><link>https://leanercloud.com/blog/2024-09-20-cross-az-data-transfer-costs.html</link><pubDate>Fri, 20 Sep 2024 22:24:02 +0000</pubDate><guid>https://leanercloud.com/blog/2024-09-20-cross-az-data-transfer-costs.html</guid><description>&lt;h2 id="the-line-item-nobody-can-explain"&gt;The line item nobody can explain&lt;/h2&gt;
&lt;p&gt;Cross-AZ data transfer is one of the least understood costs on an AWS bill. It does not map to a resource you can point at, it just shows up as data transfer charges, and it grows silently as traffic increases. A common source is an application instance talking to its database across an Availability Zone boundary, paying per gigabyte in both directions for traffic that could have been free.&lt;/p&gt;</description></item></channel></rss>