[2005] Best practice: MVC and secure connection string(s)?

[brin351]

I second what mendhak said. I'm no .net guru but have worked on corporate sites for some years now and a standard setup is a dedicated server running the site and if needed a seperate db server and possibly mail server.

If the time comes that webfarms or co location are needed your site should be running very efficient scalable code and smoothly move accross multi servers.

I think that's the most important point, how well the site runs. Adding more hardware will not fix resource or bandwidth hungry coding.

[alex_read]

Hi guys

Many, many thanks for the suggestions and opinons, they really help! Brin - I was trying (and hopefully am ) writing scalable code at the moment btw, but thanks also.

The side question I was thinking of, in relation to this question too was whether the way I'd always been taught to write sites - that is just writing front-end and processing sites and COM+ or .Net dlls and hosting them all on the web server, with just a secondary database server was the right way to go about it. Whether to move processing to third and fourth servers or not, and it's been fantastic and fascinating to hear you all code the same way - and just upscale the 2 servers into a base of 2 farms. That's very interesting to know!

Many many thanks for your time and thoughts