Skip to content

Add large databases use case page - #5549

Open
carlotas19 wants to merge 9 commits into
mainfrom
content/large-databases-use-case
Open

Add large databases use case page#5549
carlotas19 wants to merge 9 commits into
mainfrom
content/large-databases-use-case

Conversation

@carlotas19

@carlotas19 carlotas19 commented Aug 15, 2026

Copy link
Copy Markdown
Collaborator

Part of a broader Solutions tab update

Argues that conventional Postgres becomes operationally heavy at multi-TB
scale, then shows how Lakebase architecture keeps restore, branching, and
replicas independent of size. Sources recovery stats from the restores
survey and cost framing from the traconiq migration.
@vercel

vercel Bot commented Aug 15, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
neon-next Ready Ready Preview Aug 17, 2026 6:56pm

Request Review

carlotas19 and others added 2 commits August 16, 2026 10:06
Frames Lakebase as the reason restore, environments, replicas, and API
ops get simpler, then hands off to each practical section in turn.
Replaces the two stats that the figures now carry, and credits the
restores survey as the source below them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants