The first blog post of a series series dedicated to building and scaling multi-tenant, database-per-user apps in Postgres via Neon.

Neon

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.

Multi-tenancy and Database-per-User Design in Postgres

How to store other people’s data in Postgres: the three multi tenant architectures