97 articles on networking — what drives the cost, how it is priced, and where the savings actually are.
Every Service of type LoadBalancer provisions a real cloud load balancer with its own hourly fee. Teams that expose each microservice this way pay hundreds per month for routing that one ingress controller would handle. Here is the math and the fix.
Training pulls terabytes from object storage, distributed jobs push gradients across zones, and inference ships embeddings between services. At $0.01 to $0.09 per GB, AI data movement turns into a five-figure line quickly.
Moving data between a lake, a warehouse, a stream, and a BI tool crosses availability zones, regions, and account boundaries. Each crossing has a price, and at analytics volumes they add up fast.
Not all outbound traffic is billable. Every major cloud has a list of destinations where egress is free, and routing through them is one of the cheapest optimizations available. Here is the list and how to use it.
An API response is billed by the byte once it leaves the cloud. Multiply a few hundred wasted bytes by a billion calls and the padding becomes a real line item. Here is how to price a payload.
Splitting a monolith turns function calls into network calls. Those calls are metered, and a fan-out pattern across availability zones can quietly add thousands per month. Here is the arithmetic.
Spreading pods across availability zones buys resilience and costs bandwidth. Kubernetes load balances without regard to zone by default, so most of your service traffic is billed. Here is how to fix it.
A read replica in another zone or region is not just a second instance bill. Every write is shipped over a metered network, and for write-heavy systems the transfer can rival the compute. Here is the breakdown.
Backup storage is cheap and well understood. Backup movement is neither. Cross-region copies, restores, and third-party backup targets all cross metered networks. Here is what each one costs.
Video is the heaviest thing most companies put on a network. One hour of 1080p delivered to one viewer moves several gigabytes, and the per-GB meter does the rest. Here is the cost per viewer, worked out.
DNS is priced per million queries, which feels free until you count how many queries a busy system actually makes. TTLs, health checks, and service discovery all move the number. Here is the math.
Transfer Acceleration routes S3 traffic over the CloudFront edge network for a per-GB premium on top of normal transfer. Sometimes it is worth several times its price, and sometimes it does nothing at all.
Origin shield adds a second caching layer between edge locations and your origin. It costs per request and saves origin load, but it only pays for itself under particular traffic shapes. Here is when.
Active-active across two regions is not twice the cost of one. Duplicated compute, duplicated storage, and constant bidirectional replication traffic push the multiple closer to 2.3 or 2.5. Here is the breakdown.
A bandwidth bill is meaningless as an absolute number. Divided by active users it becomes a metric you can trend, forecast, and compare against revenue per user. Here is how to build it.
The more data you accumulate in one place, the more it costs to move elsewhere, and the more services cluster around it. Egress pricing is what turns that pull into a financial constraint.
Every pod start pulls an image. Multiply a 1.2 GB image by a few thousand pulls a day and registry traffic becomes a real line item, especially when the registry sits in another region or another cloud.
Observability data leaves your cloud on its way to a vendor, and it leaves continuously. At typical volumes the egress alone can rival a mid-size database bill, before the vendor charges anything.
Moving tens or hundreds of terabytes into or out of a cloud has three viable paths with very different economics. The right one depends on volume, deadline, and available bandwidth. Here is the comparison.
Private Service Connect gives you a private IP inside your VPC for a Google or third-party service. It charges per endpoint hour and per gigabyte, and it usually beats routing the same traffic through Cloud NAT.
Putting a function in a VPC is free in itself. What it pulls in is not: a NAT gateway for outbound access, data processing charges, and the choice between endpoints and gateways. Here is the bill.
Data transfer is billed per GB with no resource to point at, which is why it is the hardest line to attribute and the easiest to ignore. Here is how to find the flows, rank them, and cut them, with the per GB rates that matter.
A load balancer with no targets and a public IP with no association each cost a few dollars to tens of dollars a month. Individually trivial, collectively thousands. Here is how to find them, verify they are dead, and remove them safely.
A NAT Gateway costs about $0.045 per hour plus $0.045 per GB processed, while a NAT instance is just an EC2 box with no per-GB processing fee. For low traffic the instance can be far cheaper, but it trades money for operational risk. Here is the math.