How Your Router Helped Save the Internet

Every device connected to the internet needs an address. That address is called an IP address.

The older internet runs primarily on IPv4, a 32-bit addressing system, which provides roughly 4.3 billion possible addresses.

When the internet was young, that number sounded massive. Today? It’s nowhere near enough.

We now have billions of smartphones, laptops, smart TVs, security cameras, IoT sensors, cars, cloud instances, and industrial devices, all needing to connect. The demand has far outstripped supply.

So how has the internet not already collapsed?

The answer is hiding in your living room.

Your home router is one of the unsung heroes of the modern internet.

Here’s what actually happens:

Your internet provider assigns your home one single public IPv4 address.
Your router then assigns each of your devices (phone, laptop, TV, etc.) a private internal IP address.
When traffic comes in, the router uses NAT (Network Address Translation) to intelligently route the right data to the right device.

Result? 20 devices at home = 20 private IPs + just 1 public IP

To the outside world, your entire household looks like a single address. This simple but brilliant technique allowed us to stretch IPv4 addresses much further than anyone expected.

NAT bought us decades of time.

But NAT was never a permanent fix.

That’s exactly why IPv6 exists.

IPv6 uses a 128-bit addressing system and gives us approximately:

340,282,366,920,938,463,463,374,607,431,768,211,456 addresses

That’s 340 undecillion, enough addresses to give every device on Earth multiple IPs and still have plenty left over.

Where are we in 2026?

IPv6 adoption continues to grow steadily (especially in mobile networks and cloud providers), but IPv4 + NAT is still the dominant reality for most enterprises and homes. The transition is happening, just more gradually than many predicted.

The lesson? Technology often survives through clever engineering workarounds (like NAT) while the long-term solution (IPv6) matures.

Visit https://zinzu.io to learn about what we're building and message me if you'd like to be part of our journey or use our service. We're in the process of porting zinzu to Snowflake.

#Networking #IPv6 #IPv4 #InternetInfrastructure #Tech

Stop Treating Apache Iceberg Like an RDBMS

DATA ENGINEERING & ARCHITECTURE Why applying relational database update patterns to cloud lakehouses causes write amplification, high compute costs, and degraded query performance. Apache Iceberg is getting a lot of attention—and for good reason. It brings capabilities such as ACID transactions, snapshot isolation, schema evolution, time travel, and support

Columnar Storage and Collection Columns: Where Your Arrays and Maps Really Live

Columnar storage formats like Parquet and ORC, and columnar execution engines such as BigQuery, are widely used in analytics systems because they store data column by column on disk instead of row by row. When a query reads only the columns it needs, only those columns are read from disk,

How Block-Based File Formats Enable Parallel Processing

Conversations about data formats often focus on Parquet versus Avro, or columnar versus row-oriented storage. What is discussed less often is the block-based structure that actually enables files to be split and processed in parallel across distributed systems. This article explains that underlying mechanism. A block (e.g.

Own the fire: If you want to be a strong engineer and a real problem solver

Own the fire. * When things break, step forward. * Ownership under pressure is what separates engineers from passengers. * Roll up the sleeves * A fix without understanding is just moving the problem somewhere else. Don’t act blindly on someone else’s suggestion. * If it fails, you own the failure. * If it