Database-per-User Architecture With Shared Application Environments: How and Why

T1Covered by 1 source · first reported by Databricks / ClickHouse / DuckDB / Supabase / Neon / PlanetScale at 18 Oct 2024, 15:41 UTC

Neon works best with a project-per-user architecture, but there’s more than one way to design, implement, and manage this. Each of the two main strategies has different advantages and drawbacks. Today, we’re going to talk about the one that most resembles what you might think of...