Website design help
-
I trying to find the best way to structure the company website. They want the website to now be off site in a hosted location, BUT the database that it uses are to stay here in the office as it is integrated into the back office systems. The site currently has a public area and 2 sub sites (these talk to the database regularly) that are membership based and also has web services that are used by external parties. My thoughts are to host the all of the above in the hosted location and have it talk to the database in our office through a web service but I am not sure that this is the best approach.
Lobster Thermidor aux crevettes with a Mornay sauce, served in a Provençale manner with shallots and aubergines, garnished with truffle pate, brandy and a fried egg on top and Spam - Monty Python Spam Sketch
-
I trying to find the best way to structure the company website. They want the website to now be off site in a hosted location, BUT the database that it uses are to stay here in the office as it is integrated into the back office systems. The site currently has a public area and 2 sub sites (these talk to the database regularly) that are membership based and also has web services that are used by external parties. My thoughts are to host the all of the above in the hosted location and have it talk to the database in our office through a web service but I am not sure that this is the best approach.
Lobster Thermidor aux crevettes with a Mornay sauce, served in a Provençale manner with shallots and aubergines, garnished with truffle pate, brandy and a fried egg on top and Spam - Monty Python Spam Sketch
-
Then our claims handlers and brokers can't retrieve specific information from our back office database.
Lobster Thermidor aux crevettes with a Mornay sauce, served in a Provençale manner with shallots and aubergines, garnished with truffle pate, brandy and a fried egg on top and Spam - Monty Python Spam Sketch
-
Then our claims handlers and brokers can't retrieve specific information from our back office database.
Lobster Thermidor aux crevettes with a Mornay sauce, served in a Provençale manner with shallots and aubergines, garnished with truffle pate, brandy and a fried egg on top and Spam - Monty Python Spam Sketch
The point however is that you need a business decision about how that impacts the business functionality of the site. That in turn impacts the implementation. Some possible implementations. 1. The site is unusable, and tells the user that. 2. Some specific parts are unusable and tells the user that. 3. Data from the office is cached, with perhaps appropriate expiration times (which again might require some user error if.) 4. Any down time at all is unacceptable thus a replication scheme is needed. Not to mention of course that you want some way to be notified if the web site can't see the database.
-
I trying to find the best way to structure the company website. They want the website to now be off site in a hosted location, BUT the database that it uses are to stay here in the office as it is integrated into the back office systems. The site currently has a public area and 2 sub sites (these talk to the database regularly) that are membership based and also has web services that are used by external parties. My thoughts are to host the all of the above in the hosted location and have it talk to the database in our office through a web service but I am not sure that this is the best approach.
Lobster Thermidor aux crevettes with a Mornay sauce, served in a Provençale manner with shallots and aubergines, garnished with truffle pate, brandy and a fried egg on top and Spam - Monty Python Spam Sketch
If the web application must use the database in your office, then go for a web service (a WCF service in case of a .NET solution) in between your web site and the database, otherwise you may want to have a separate database for your web site. I find it easy to have separate databases for each app and make them share data as needed instead of one big "do-it-all" database that is hard to maintain.
-
If the web application must use the database in your office, then go for a web service (a WCF service in case of a .NET solution) in between your web site and the database, otherwise you may want to have a separate database for your web site. I find it easy to have separate databases for each app and make them share data as needed instead of one big "do-it-all" database that is hard to maintain.