/plushcap/analysis/neon/neon-multi-tenancy-and-database-per-user-design-in-postgres

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

What's this blog post about?

This text discusses multi-tenancy architectures in Postgres databases, focusing on the database-per-user design. It highlights three main approaches to handling multiple users' data: shared schema, schema-per-user, and database-per-user. The advantages of a database-per-user strategy are outlined, including improved security, isolation, and control over geographic restrictions. The text also explores the concept of isolated vs. shared application environments and the importance of a control plane for managing multiple databases effectively. It concludes by emphasizing that while both approaches have their merits, the choice ultimately depends on specific business requirements and customer preferences.

Company
Neon

Date published
Aug. 29, 2024

Author(s)
Dian M Fay

Word count
1450

Hacker News points
None found.

Language
English


By Matt Makai. 2021-2024.