Add Mutli-Tenant Feature

[BjornTheProgrammer]

Thank you for your amazing framework, It is incredibly useful!

I would like to instantiate multiple Medusa stores for separate tenants, this way I would not need to use multiple different databases for each tenant's store alongside different instances of MedusaJS. It would be much harder to maintain such a setup without Medusa handling it natively, additionally, it would consume much more compute resources.

To do so, we would only really need a store_id or tenant_id on every table. I have a client that would be interested in maintaining this feature in the future as well, otherwise, they will likely maintain a fork of Medusa.

Please let me know if you would be interested in such a feature set, and the requirements that you might have for such a feature!

[sumitbhanushali]

you can have multiple databases in one database server by mapping site name to database name. This way no unnecessary schema level changes need to be done and data will also be protected which can otherwise be exposed by some wrong query or missed permissions

[BjornTheProgrammer]

Thank you for your input @sumitbhanushali! We've already considered this as a solution, but it falls short in a few respects. 1) It still requires separate MedusaJS instances, 2) It requires additional overhead for each database and additional connection logic (even if it is on a single server), and 3) It would still require migrations to occur on every single database.

As for the security concerns, this can be mitigated very well by postgresql's row-level security feature.

Making a high-availability read, and write single db is also much easier than a lot of other methods, for example, shopify was able to do so until 2014. And using that method, if you want to shard data in the future, it can be even more complex.

This is why it would be very beneficial for there to be a scheme change to support multiple tenants.