Ask HN: Has anybody shipped a web app at scale with 1 DB per account?
If an &quot;account&quot; is an &quot;enterprise&quot; customer (SMB or large, anything with multiple user accounts in it), then yes, I know at least a few successful companies, and I would argue in a lot of scenarios, it&#x27;s actually advantageous over conventional multitenancy.<p>The biggest advantage is flexibility to handle customers requirements (e.g. change management might have restrictions on versioning updates) and reduced impact of any failures during upgrade processes. It&#x27;s easier to roll out upgrades progressively with proven conventional tools (git branches instead of shoddy feature flags). Increased isolation is also great from a security standpoint - you&#x27;re not a where clause away from leaking customer data to other customers.<p>I would go as far as saying this should be the default architecture for enterprise applications. Cloud infrastructure has eliminated most of the advantages of conventional multitenancy.<p>If an account is a single user then no.<p>PS: I have a quite a lot of experience with this so if you would like more details just ask.