Topic: Early Design Issue: keeping data separated or making multiple apps?
my situation is similar to dylanfm's as posted here:
A noob's desire to get it "right" the first timebut my question is about a different part of the site design.
We are just getting started with a new Rails app and we want to map it out in pretty good detail before we get going.
Our site is basically a online exam application where we will have 'semester's' and each semester will have its own set of questions, users, answers, etc.
There will be very little carry over between semesters, except the questions will be copied over.
The question I have is what would be the 'rails way' to divide these semesters up?
At first I was thinking of using a simple table/object for semester where each semester would have_many questions, users, answers ...
But because each semester is essentially its own entity, it seems like a bad idea to keep all the data from every semester in one big database.
Rather, it makes more sense to me currently to have each 'semester' basically be their own rails app, with their own database - keeping everything separated in that way.
Is this a good idea?
The admins of the site would have to be easily able to create a new semester, and if it was done as new rails applications, that would mean my over-all app would have to be able to generate new apps easily... which I haven't been able to glean much info of how that would be done.
So what is a better way to do this?
In my mind, the situation seems similar to how shopify.com operates: a user can go on and create their own 'site'. Each site has all the set-up to add/manage products, collections, etc, but the data between sites is never shared.
Would this be done by making the whole site a plugin?
i'm missing something important here
Thanks very much for any help
Last edited by vlandham (2007-02-16 14:22:05)