Topic: A Question for God = David Hansson = 37signals Database?
I wish to develop and market web based applications that have distinct data for each user that operates upon them.
My intensions are nowhere near the application realm of www.37signals.com and I hope my question doesn't reveal any trade secrets.
I expect there are two ways to handle this?
1. Develop a structure so that each customer has a separate database that holds tables with identical names. There login would determine the connection to THEIR database.
2. One LARGE database's main record would be a USERRECORD and all subsequent parent -> child -> grandchild records cascade from this. I expect to CHEAT each record would hold the USERRECORD KEY?
Which method do you use at www.37signals.com?
Along similar lines, I want to create a website that is virtually identical but appears to be many distinct domains. For example I would have 12 domains that are the names of the month (Jan, Feb, Mar. etc) and the only thing different is the database they access. In this way I'd hope to maintain one source deck and be able to manage all 12 sites with reasonable effort. Not only would the database hold the chats, activities, user info, blogs, voting for each distinct site, but also TEMPLATE words such as the <h1>January</h1> . This question follows similar lines in that should I use strategy 1 or 2?
I am taking the Pragmatic Studios class in Dallas on April 18 - 20th and I'm hoping to have my projects moving in your recommended direction before I get there.
dak AT itracker DOT com