Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Feb 21, 2013 12:26 PM by ghostme
Feb 21, 2013 07:02 AM|LINK
Currently we are designing an enterprise web application (internet facing) using the layered acrhiectured approach splitting the components into specific areas of concerns.
In terms of security, we are putting the webserver and application servers in a DMZ(protected by a firewall from the users request). The databases then seats in the internal network(there is a also a firewall between the DMZ and database servers). Also,
the users request are transmitted via https(SSL). Are there any other things with regards security that could be added to make the design more secure.
In terms of scalability and performance, the hardware availability currently supports just one server each for the Application/Web front end servers. However, I know with an enterprise web application it is necessary to have a web farm that takes advantage
of NLB(software or hardware) to manage user requests and ensure high availability.
However, when implementing high availability on an asp.net application what are gotchas that we should look for? and can we also Load balanced the application servers(Which host mainly the webservices to make database calls to the Line of business application).
Finally, what are the guidance or methodical approach in measuring performance with regards CPU load, IIS application pool performance and page load time.
Thank you very much
Feb 21, 2013 10:20 AM|LINK
Some of the things you must take care are following :
Feb 21, 2013 12:26 PM|LINK
Thank you for the reply, with regards security is there any need to make room or implement Transparent Data encryption or Cell level encryption in sql server?
Also, with regards to SQL server caching, is there a need to create a plan of clearing the Cache over a number of period of days/weeks/month.