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.

[mnstry]

We really need this too! Have you initiated the fork already?

[BjornTheProgrammer]

It's being internally maintained right now. And it is quite specific just to their needs. So I don't think a public fork will be coming in the near future. I'll ask about it to make sure.

[techspawn]

We would be interested in using and maintaining it in case you make it public.

[trevster344]

I tried to do this a short while ago. There doesn't appear to be any way with existing features to accomplish this. My workaround so far has been to implement each of my tenants as a sales channel and apply middleware to restrict / apply sales_channel_id filtering on many features. This has been pretty successful thus far.

[jpxgen]

Hi @trevster344
I am glad to know that you could achieve through a workaround solution.

Can you please help sharing, how you are able to get the product categories and collections specific only to that sales channel? Also, are the orders separated based on that sales channel?

[trevster344]

@jpxgen hey no problem. As far as product collections and categories go, I would create module links between either module and the sales channel module. Then apply a middleware on the respective routes that checks this using the remote query module. Most of the core features in medusajs are implemented in workflows. Many of these workflows have hooks. Use the hooks as a place to create the link records when products or orders are created. Orders are really easy because they already have the sales channel id field for tenancy filtering. Use a middleware on the order routes to force this or check for this.

[saranshisatgit]

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!

You can create a a store and use module link to link it with partner or your desired namespace and keep using that everywhere the same reference! You might need to develop your API route like say partner which can handle all the required isolation. It’s doable not complex but it’s a choice of design !

Store is associated with location and currency which doesn’t need isolation as such , products are connected with channels which are connected with stores and each public key is associated to store which creates the isolation per store level.

[tom-aniol]

Hey @BjornTheProgrammer, hope this helps a bit in topic

We (Rigby) have had many conversations about multi-tenancy and multi-store setups in Medusa and decided to do a deep dive as eBook: Multi-Tenant Architecture in Medusa, covering the different technical approaches and trade-offs.

You can also read a summary on the official Medusa blog: Building a multi-tenant commerce platform with Medusa, written by our CTO.

[BjornTheProgrammer]

Appreciate the write up!

[trevster344b]

@tom-aniol Thank you! I have played a lot with multi tenancy in my apps with medusajs. It's nice to see the different approaches so well documented.