# 7.2 The Infinite Archive In a traditional warehouse, the [[Postgres/Chapter 5 - The Hunger of Resources#The Lesson of the Desk|Filing Cabinet]] is a physical object bolted to the floor. If the warehouse burns down, the cabinet is gone. Modern "Cloud-Native" Postgres solutions (like **Amazon Aurora**, **Google AlloyDB**, and **Neon**) do something radical: they **divorce the elephant from the cabinet**. ![The Cloud WAL](assets/arch_cloud_wal.png) ## The Magic Cloud (Distributed Storage) Instead of a metal cabinet in the basement, these systems use an **Infinite Archive** in the sky. When the elephant makes a change, he still scribbles in his Pocket Diary (WAL). But instead of eventually walking to the basement to update a cabinet, he simply **tosses the diary pages into a glowing cloud**. The cloud is magic. It is spread across a hundred different buildings. It never loses a page. It is always awake. ## Why This Changes Everything By moving the storage to the cloud and only shipping the WAL: 1. **Instant Recovery**: If the elephant falls asleep (crashes), a new elephant can wake up, reach into the cloud, grab the latest diary pages, and be ready to work in seconds. He doesn't need to rebuild the whole warehouse; the data is already there. 2. **Infinite Scaling**: You can have a hundred elephants all reading from the same magic cloud. They don't need their own copies of the filing cabinet; they just look at the cloud's current state. 3. **Low Latency Replication**: Because the storage _is_ the record, there is no delay in "shipping" the data. Everyone sees the cloud update at the same time. By mastering the **[[Architecture/WAL|WAL]]**, the lazy elephant has finally achieved his ultimate goal: a world where he doesn't even need to own a filing cabinet. He just thinks, scribbles, and the cloud remembers. --- [[Chapter 7/7.1 - Read Replicas|← 7.1 - Read Replicas]] | [[Chapter 7/7.0 - The Cloud Scales|↑ 7.0 - The Cloud Scales]] | [[Chapter 7/7.3 - Partitioning|7.3 - Partitioning →]]