How to build multi-tenancy? #495
-
|
Hey, I was reading about multi-tenancy here Also, I read here in different ways to add multi-tenancy support. I want to go for the "one schema per tenant" solution but using Vendure as my backend. Does anyone have any library in mind similar to django-tenants to add multi-vendor support? Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 20 replies
-
|
Hi there, I skimmed the article you linked but I don't really understand what is meant by "one schema per tenant", but it seems it may be a Postgres-specific solution? Vendure supports several different DBs so I doubt any DB-level solution would work here. By "community projects" it is referring to contributions to the core that enable multi-tenancy features, rather than a plugin you can install. For example: These PRs make it so Orders and Customers are assigned to specific channels. So as of now the following entities are "channel-aware":
A Channel in this case can be used to represent a tenant (vendor). So currently it may be possible to have a multi-tenant solution, but I'm pretty sure you'll find some rough edges and cases where things may break down or not be as expected. Alternative solutionIf you are aiming to build a Shopify-like platform where a merchant can create an account and then get a new e-commerce store created for him or her, then there is another approach you may want to consider. You can do it at the operations level by creating infrastructure that will create a new Vendure instance for each tenant. In this way each instance is truly isolated. Pros:
Cons:
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the quick reply! Yeah, I was planning to build a Shopify like platform and found the isolated approach to be infra heavy. I think I'll go with the channels method for now and will make some PRs if I solve any issues! |
Beta Was this translation helpful? Give feedback.
-
|
I am also using Vendure as multi-tenant marketplace: https://github.com/martijnvdbrug/shops/tree/master/vendure |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for sharing @martijnvdbrug! Having a look right away. |
Beta Was this translation helpful? Give feedback.
-
What would be the work required to support this built-in? Listing some tasks would make it easier for potential contributors to tackle some of them. |
Beta Was this translation helpful? Give feedback.
-
|
@michaelbromley
To implement this I'm thinking of creating a new channel every time a new user comes in and creates a new channel page. I hope this approach would be fine? |
Beta Was this translation helpful? Give feedback.
-
|
Hi,
Next.js is a good choice - many people are already using it with Vendure. The Next.js Commerce project still seems a bit immature to recommend - it is still tightly coupled to BigCommerce for example.
I don't quite understand the need for this part. Why can you not have a single page that is used by all stores, where the data is dynamically populated from the API? A new physical file for each store seems highly unusual.
The Admin API has the assignProductsToChannel mutation which you can use to assign a product to the channel of a particular merchant. Each Channel has a The other parts sound fine. I'll be interested to see the finished product! |
Beta Was this translation helpful? Give feedback.
-
Yeah, I found it tough to set up too. Any other Nextjs based framework or storefront that you would recommend? Starting from scratch would be a lot of work otherwise. I was thinking of using react-storefront. Going by their documentation, I only need to write a connector to integrate Vendure.
So I want the creators of the stores to easily share the link of their store. Their customers can open the store link with any browser and place their orders. If the link is the same, how would we figure out which store to display to the customer? Some examples of products following the same page method
Got it, the channels feature is actually pretty cool.
Absolutely! Will be sharing the product and my experience in the Thanks a ton for your help. |
Beta Was this translation helpful? Give feedback.
-
|
Hey How do you suggest I store the tenant's login data? As the login would be through an OTP every time, I won't be storing any password. However, there will be a channel token associated with every token. So I was thinking of keeping the login data directly in my Postgres and store the channel token along with the phone number in each row. I anyhow would be coding the logic of OTP login on my own, so I guess I don't need vendure to login/register the tenant? (Apart from changing/creating the channel) Would appreciate any input. |
Beta Was this translation helpful? Give feedback.
-
|
Hi! It's hard for me to advise in detail without fully understanding the way your auth should work, but in general you should be aiming to work within the pattern described here: https://www.vendure.io/docs/developer-guide/authentication/ You could, for example, store the phone # as the |
Beta Was this translation helpful? Give feedback.
-
|
Ohh, missed your reply somehow! Thanks for sharing this, will have a look and revert. |
Beta Was this translation helpful? Give feedback.
-
|
Good Morning Michael I was trying to figure out the right way to use a channel with Nextjs Dyanmic routing. I want to achieve the following with graphql, nextjs and urql SSR
SSR is setup by following the guide https://formidable.com/open-source/urql/docs/advanced/server-side-rendering/#nextjs / pages/index.js
import React from 'react';
import Head from 'next/head';
import { withUrqlClient } from 'next-urql';
const Index = () => {
const [result] = useQuery({
query: '{ test }',
});
// ...
};
// was wondering if I could add the store-name to the url below
export default withUrqlClient((_ssrExchange, ctx) => ({
// ...add your Client options here
url: 'http://localhost:3000/graphql',
}))(Index);I asked this question in the Urql, their solution works but they also suggested to use a better method to do the same So now i'm thinking to use the channel token as a query parameter, but I cant figure out where exactly shall the query parameter go? The options in any of the queries does not seem to have a channel token parameter. |
Beta Was this translation helpful? Give feedback.
-
|
Amazing, thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Hey @michaelbromley, peeps at urql helped me out to set the token header Now for the Dashboard, I'm using client side rendering and am currently trying to implement the following flow
I'm confused about the third part, could you let me know how did you do the same in the Admin UI and Apollo? I'll figure out to convert the Apollo logic to Urql, they're pretty similar. |
Beta Was this translation helpful? Give feedback.
-
|
I did some research and I guess I should use cookies to do the above? |
Beta Was this translation helpful? Give feedback.
-
|
Cookies are very simple because the browser handles it all for you. Bearer tokens are useful when you e.g. need to support mobile apps or other non-browser clients. So yeah, use cookies if you only need to support the browser. |
Beta Was this translation helpful? Give feedback.
-
|
Got it. Thanks Michael and Merry Christmas 🎄 |
Beta Was this translation helpful? Give feedback.
-
|
Hello ; |
Beta Was this translation helpful? Give feedback.
Hi there,
I skimmed the article you linked but I don't really understand what is meant by "one schema per tenant", but it seems it may be a Postgres-specific solution? Vendure supports several different DBs so I doubt any DB-level solution would work here.
By "community projects" it is referring to contributions to the core that enable multi-tenancy features, rather than a plugin you can install. For example:
These PRs make it so Orders and Customers are assigned to specific channels. So as of now the following entities are "channel-aware":
A Channel in this case c…