Original Summary

I'm working on the infrastructure for a multi-tenant SaaS and I'm curious how other developers are approaching database isolation. There seem to be three common approaches: One database + shared tables One database + separate schemas Separate database per customer Each seems to have different trade-offs around: - isolation - migrations - backups - connection limits - infrastructure cost - monitoring - scaling We're currently experimenting with a hybrid approach where smaller projects can share infrastructure while larger projects can be allocated to dedicated PostgreSQL databases. The part I'm struggling with is the provisioning/allocator layer. For example: New project ↓ Check available capacity ↓ Choose PostgreSQL node ↓ Provision database/schema ↓ Configure access ↓ Start monitoring usage For anyone running a multi-tenant SaaS: How did you decide between shared schemas and separate databases? And at what point did you decide it was worth building an automated database allocator? Interested in hearing how people are handling this in production.   submitted by   /u/ZENDBX [link]   [comments]

  • 情报分类：服务器与云资源
  • 分类依据：内容涉及服务器、云资源或网络线路
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/9/19 14:56:05