# WAL + S3: Lakebase storage for the era of agents

DevFeed: [WAL + S3: Lakebase storage for the era of agents](<https://devfeed.tech/articles/wal-s3-lakebase-storage-for-the-era-of-agents-5847.md>)

Original publisher: [Read original article](<https://neon.com/blog/wal-s3-lakebase-storage-for-the-era-of-agents>)

Author: Carlota Soto

Published: 2026-08-24T12:00:00Z

Content type: article

Language: en

Sources: [Blog -- Neon Docs](<https://devfeed.tech/sources/blog-neon-docs.md>)

Topics: [Database](<https://devfeed.tech/topics/database.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [data](<https://devfeed.tech/topics/data.md>), [migration](<https://devfeed.tech/topics/migration.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [migration](<https://devfeed.tech/tags/migration.md>), [product](<https://devfeed.tech/tags/product.md>), [s3](<https://devfeed.tech/tags/s3.md>), [storage](<https://devfeed.tech/tags/storage.md>), [transactions](<https://devfeed.tech/tags/transactions.md>)

## AI overview

The article argues that PostgreSQL workloads associated with agents need storage built around transaction history rather than only the current state. It presents the write-ahead log as an existing timeline of database modifications and examines placing S3 beneath PostgreSQL to support isolated copies, point-in-time restoration, historical queries, and many disposable environments more efficiently.

## Source excerpt

Agents treat code as lightweight: branch it, deploy it, throw it away. The infrastructure under that code should work the same way. Working with an OLTP database is traditionally heavy and full of friction, but very little of that is a Postgres problem.