About hosting architecture for a travel agency - How to decide? [on hold]
We're changing the hosting for our web sites. Do you know where can I get
advice on the best architecture that we can have?
Currently we've only one server which holds all the domains and all the
databases. The domains are from a Travel Agency, and this is an IIS server
with SQL Server, and the number of visits is around 500,000 per month.
I was thinking in having two database servers, one that manages all the
database content for promotions, tours information, etc, and other
database server that holds the customers information (the information from
the people buying things on the web sites).
What do you think?
No comments:
Post a Comment