|
|
Posted by AlterEgo on 01/26/07 00:17
Mikee,
I would put all users in the same database. Less maintenance, less problems.
You can always scale up or out if the site is successful. With multiple
databases, the more successful the site, the more maintenance and headaches
you'll have.
BTW, don't store the photos in the database, store them in the file system.
Use a hive folder structure based upon parts of the file name.
A
--AA
--AB
----ABA
----ABB
----ABC
Also, make sure you have a good backup and recovery plan for the DB and file
system as well.
-- Bill
"Mikee Freedom" <mikeefreedom@gmail.com> wrote in message
news:1169763927.138077.147690@m58g2000cwm.googlegroups.com...
> Good Morning all,
>
> New member to the list, hoping you might be able to give me some much
> needed advice.
>
> Basically, I have a client who would like to offer the ability for his
> users to have their own independent website at his domain. It is not as
> clear cut as that but as a generic description it will do.
>
> I know such services exist and I'm by no means emulating there's in any
> way. the specific purpose of the individual user sites is fairly
> specific, hence why he needs to get us to create it for him.
>
> In a nutshell, people will be able to sign up, make some configuration
> decisions, add some content, and have a website of their own that they
> will be able to upload photo's to. Lot's of photo's.
>
> The decision I was looking at making, was whether or not to create
> individual databases for each of the new users. If this was going to be
> a good idea or bad, or if it was dependent a little on further factors.
>
> I've only begun to plan the site but this idea popped in to my head and
> I was hoping someone could either say - "you ass, what are you
> thinking?"; or indicate it may be beneficial.
>
> My alternate option is to relate all content, photo's, albums, etc to
> individual users. This is cool I guess, but liked the idea of complete
> seperation.
>
> One specific question I had was, if I needed to search for a particular
> value in multiple databases is this going to be a pain in the ass, a
> terrible load on the server... or anything else that I may be
> overlooking.
>
> Conclusion :
>
> I like the idea of it, is it a good one?
> Are there considerations?
>
> Thanks everyone,
> Mikee
>
> p.s. if any of what I've written doesn't make sense please feel free to
> berate or ask for further explanation :)
>
Navigation:
[Reply to this message]
|