Appears on
Articles4
Multi-tenancy and Database-per-User Design in Postgres
Many Neon users aren’t just storing their own information, but host data on behalf of many clients or customers, commonly called tenants. Over the decades, approaches to these multi-tenant data architectures have evolved in three main directions: shared schema, schema-per-user, a...
Control Planes for Database-Per-User in Neon
Due to its serverless architecture, Neon is a great option for building multi-tenant, database-per-user applications in Postgres. In a previous post, we explored the various approaches to multi-tenancy in Postgres, with a particular focus on the database-per-user architecture and...
Database-per-User Architecture With Shared Application Environments: How and Why
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...
Database-per-User Architecture With Isolated Application Environments
Previously in this series, we discussed implementing database-per-user architecture in Neon with a shared application environment communicating with individual user databases. That approach keeps operational complexity contained by minimizing the number of software systems deploy...