I want to convert an existing app to a multi tenancy architecture and will be using Postgres schemas for this. One account
will be a tenant = one Postgres schema.
So far I’ve had a single accounts
table which held all accounts and their information:
public (schema)
└── accounts
├── contacts
├── orders
├── settings
└── users
Now the account information should be stored somewhere within the schema boundaries, but having just one account
table to store one single entry feels weird. It would look like this:
tenant_1 (schema)
├── account
├── contacts
├── orders
├── settings
└── users
tenant_2 (schema)
...
I cannot think of a good alternative and couldn’t find any examples online, not even for Rails or Laravel. Is this the way to go or am I missing something?