I have 3 database-driven dynamic web sites. 1 is already built. 2 others are still in testing. 1 is a consumer sweepstakes site. The other 2 sites are B2B and ecommerce-related.
My question is is having ONE database behind all these sites (i.e. having a global member username/password/email/address) system better thanhaving one database behind each site. I noticed both Yahoo and Lycos are
using the one database approach but not sure if this is the best way to go for me.
I would like to know if having ONE database is indeed the best way or would it cause too much trouble for what it's worth. I.E. A user that registered for the sweepstakes site wants to use his "throw-away" email but he does not want to use his "throw-away" email address when he is using the ecommerce site.
Thanks!
My question is is having ONE database behind all these sites (i.e. having a global member username/password/email/address) system better thanhaving one database behind each site. I noticed both Yahoo and Lycos are
using the one database approach but not sure if this is the best way to go for me.
I would like to know if having ONE database is indeed the best way or would it cause too much trouble for what it's worth. I.E. A user that registered for the sweepstakes site wants to use his "throw-away" email but he does not want to use his "throw-away" email address when he is using the ecommerce site.
Thanks!