Multiple websites/databases with a shared database [modified]
-
Hi, I have 2 websites. I want users to be able to register once, and then be able to login into any one of the websites and have their user details displayed. The 2 websites are different in nature. The reason for doing it this way is because I don't want users to register twice, once for each site. I am asking for your advice on how to implement something like this because I have never done it this way. I was thinking of having a separate database for my membership stuff. But if I have my membership stuff in a separate database as to the website database, won't this reduce speed because it is working with 2 databases?? Let me explain my scenario. Lets say I have an ecommerce application. One website that resides in South Africa, and the other website is in Australia. They are similar in nature, but each has their own database, and the "shared" membership database. Now this raises the next question, what should I all place in the shared database? Products? Product reviews? Country? etc etc etc.. Some where along the line I will need to make a relationship to link 2 tables in separate databases, like customer and product review. This is the type of questions that I have because I don't know how to implement this. It's like Amazon.com and Amazon.co.uk. I am sure of it they have their own separate database for each website, but a shared database for memberships? I hope I can make sense, can you please help me think through this scenario? What would I have to Google on something like this? Thanks
modified on Thursday, June 18, 2009 4:16 AM
-
Hi, I have 2 websites. I want users to be able to register once, and then be able to login into any one of the websites and have their user details displayed. The 2 websites are different in nature. The reason for doing it this way is because I don't want users to register twice, once for each site. I am asking for your advice on how to implement something like this because I have never done it this way. I was thinking of having a separate database for my membership stuff. But if I have my membership stuff in a separate database as to the website database, won't this reduce speed because it is working with 2 databases?? Let me explain my scenario. Lets say I have an ecommerce application. One website that resides in South Africa, and the other website is in Australia. They are similar in nature, but each has their own database, and the "shared" membership database. Now this raises the next question, what should I all place in the shared database? Products? Product reviews? Country? etc etc etc.. Some where along the line I will need to make a relationship to link 2 tables in separate databases, like customer and product review. This is the type of questions that I have because I don't know how to implement this. It's like Amazon.com and Amazon.co.uk. I am sure of it they have their own separate database for each website, but a shared database for memberships? I hope I can make sense, can you please help me think through this scenario? What would I have to Google on something like this? Thanks
modified on Thursday, June 18, 2009 4:16 AM
.NET Enthusiast wrote:
I want users to be able to register once, and then be able to login into any one of the websites and have their user details displayed.
try Single Sign On(SSO)
himanshu
-
Hi, I have 2 websites. I want users to be able to register once, and then be able to login into any one of the websites and have their user details displayed. The 2 websites are different in nature. The reason for doing it this way is because I don't want users to register twice, once for each site. I am asking for your advice on how to implement something like this because I have never done it this way. I was thinking of having a separate database for my membership stuff. But if I have my membership stuff in a separate database as to the website database, won't this reduce speed because it is working with 2 databases?? Let me explain my scenario. Lets say I have an ecommerce application. One website that resides in South Africa, and the other website is in Australia. They are similar in nature, but each has their own database, and the "shared" membership database. Now this raises the next question, what should I all place in the shared database? Products? Product reviews? Country? etc etc etc.. Some where along the line I will need to make a relationship to link 2 tables in separate databases, like customer and product review. This is the type of questions that I have because I don't know how to implement this. It's like Amazon.com and Amazon.co.uk. I am sure of it they have their own separate database for each website, but a shared database for memberships? I hope I can make sense, can you please help me think through this scenario? What would I have to Google on something like this? Thanks
modified on Thursday, June 18, 2009 4:16 AM
if you are using mysql you just need to grant access to the ip of each website. if they're both on one server you don't even need to do that.
-
Hi, I have 2 websites. I want users to be able to register once, and then be able to login into any one of the websites and have their user details displayed. The 2 websites are different in nature. The reason for doing it this way is because I don't want users to register twice, once for each site. I am asking for your advice on how to implement something like this because I have never done it this way. I was thinking of having a separate database for my membership stuff. But if I have my membership stuff in a separate database as to the website database, won't this reduce speed because it is working with 2 databases?? Let me explain my scenario. Lets say I have an ecommerce application. One website that resides in South Africa, and the other website is in Australia. They are similar in nature, but each has their own database, and the "shared" membership database. Now this raises the next question, what should I all place in the shared database? Products? Product reviews? Country? etc etc etc.. Some where along the line I will need to make a relationship to link 2 tables in separate databases, like customer and product review. This is the type of questions that I have because I don't know how to implement this. It's like Amazon.com and Amazon.co.uk. I am sure of it they have their own separate database for each website, but a shared database for memberships? I hope I can make sense, can you please help me think through this scenario? What would I have to Google on something like this? Thanks
modified on Thursday, June 18, 2009 4:16 AM
I wouldn't worry too much about connecting to two databases, as long as you're pooling your connections it shouldn't cause much of (if any at all) a performance issue. If you really don't want to do it, you can use cross database joins (in SQL Server) or cross schema joins (in Oracle) as long as your two databases are on the same server. If they're on different servers you can use linked servers with SQL server but I wouldn't recommend it.
-
Hi, I have 2 websites. I want users to be able to register once, and then be able to login into any one of the websites and have their user details displayed. The 2 websites are different in nature. The reason for doing it this way is because I don't want users to register twice, once for each site. I am asking for your advice on how to implement something like this because I have never done it this way. I was thinking of having a separate database for my membership stuff. But if I have my membership stuff in a separate database as to the website database, won't this reduce speed because it is working with 2 databases?? Let me explain my scenario. Lets say I have an ecommerce application. One website that resides in South Africa, and the other website is in Australia. They are similar in nature, but each has their own database, and the "shared" membership database. Now this raises the next question, what should I all place in the shared database? Products? Product reviews? Country? etc etc etc.. Some where along the line I will need to make a relationship to link 2 tables in separate databases, like customer and product review. This is the type of questions that I have because I don't know how to implement this. It's like Amazon.com and Amazon.co.uk. I am sure of it they have their own separate database for each website, but a shared database for memberships? I hope I can make sense, can you please help me think through this scenario? What would I have to Google on something like this? Thanks
modified on Thursday, June 18, 2009 4:16 AM
Based on this information,
.NET Enthusiast wrote:
One website that resides in South Africa, and the other website is in Australia.
.NET Enthusiast wrote:
The 2 websites are different in nature.
.NET Enthusiast wrote:
what should I all place in the shared database?
I would replicate the registered user information to achieve your requirment of
.NET Enthusiast wrote:
I want users to be able to register once, and then be able to login into any one of the websites and have their user details displayed.
I can't imagine that you would be having thousands of new members signing up at each website, so I would build a webservice that would allow Website A to create a registered user in Website B and vice versa. This would allow your websites to operate independently yet provide the registered user easy access to both websites. My 2 cents. :cool: