module data design across modules #4233
Unanswered
minorityuk
asked this question in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
HI
I am working on a SAAS product and I am quite tempted to use Oqtane as the basic nav, user management and multitenant is what I want and saves me coding it.
The concept in a really simple description is I want to create on the master/admin a module called SurveyManager which will allow us to build survey with question and follow up question based on answer they give to a question. the admin module will create the surveys and store them in the master tenant.
I will then have another module for surveyCustomer for example and this will contain all the tenant logic for viewing the survey answering the survey etc.
I am thinking of keeping the master db as the true source of survey and question and simply storing the answers in the tenant database but I am concerned when I try to show a page of the answer and question since they stored separate it cause latency especially if I need to show many answer groups....what do you think.
My last question or suggestion I am looking for is if I do copy the question down to the tenants and then have extra table for storing the answer can i share my DAL entities between the two modules either creating a class they inherit from or something. Or should I keep them truely seperate as the master never have any answers.
Beta Was this translation helpful? Give feedback.
All reactions