The post examines the multi-tenancy strategies in Postgres, emphasizing the database-per-user architecture. It discusses the evolution of multi-tenant architectures, highlights the benefits and challenges of the database-per-user strategy, and contrasts it with schema-per-user and shared schema approaches. The post also introduces the concept of control planes for managing and scaling multiple databases effectively, especially with Neon’s cloud-native capabilities.

8m read timeFrom neon.tech
Post cover image
Table of contents
How to store other people’s data in Postgres: the three multi tenant architecturesWhy go database-per-user?Database-per-user system designControl planesWrap-up

Sort: