ASP.NET Web Application Architecture Design Council

Question

previously my ASP.NET web application connected directly to the database using ADO.NET. Now I want to change it to 3 layers, ASP.NET level, middle level of web service and database level. I think there is an advantage in that I could abstract the data source on the front layer of ASP.NET, loosely coupled and reduce potential security risks, to allow an ASP.Net external open web application to access the database directly, etc. d.

Compared with 2-tier architecture with three-layer architecture, I met with two main problems.

• An extra layer of average web service will have more traffic, for example. ASP.NET does not negotiate directly with the database, but negotiations with the web service and maintaining the web service with the database will increase traffic. Will this be a bottleneck? Any general recommendations to solve this problem if this is a bottleneck?

• Because ASP.NET cannot connect to the database but connect to the web service, it cannot easily get the DataSet / DataTable. It is hard to imagine tabular form data for data-bound controls. Any ideas for creating a presentation layer in ASP.NET simplified coding?

Regards,
George

Answer 1

, , . , , , , ... ? , ?

:

• , - (, " , ", , , , ASP.NET)

• , - (, ) , , , - ?

- . , .

Answer 2

№2 - , , DataSet -. http://tinyurl.com/ah58xc

, , , . , " " , ASP.NET. , , , .

, , , , "-" - . , , , "" . , , , , , , 3 (back-end, proxy layer ).

Answer 3

: - ? , , , .

, - , - . - :

{internet} → | DMZ | → - → | LAN | → →

, , DMZ. - , - , , IP- DMZ, , .

If you intend to use WCF for communication between servers, I would suggest using something like binary serialization over TCP, not SOAP. This should work better (feel free to set up a quick test). I have not tried it myself, but WCF could serialize a dataset or table by wire. See here .