.Net Remoting or Web Service?

Question

0.00/5 (No votes)

See more:

Hi,

There is a web application (built on three tier architecture) is hosted in a web server which is in DMZ (Demilitarized zone) network and it is trying to access the Database server which is in secure network (Corporate Network). Due to the security concern (the database credentials configured in the config file and the web server is facing the public network [internet]) we considered to move the (DAL) data access layer (BL as well - not sure at this moment) of the web application to the secure network (a different physical server [app server] in corporate network). If we separate the (BL and DAL) from UI then the interaction between BL/DAL and UI has to be done through some logic. Here i see 2 options. One is through web service and other one is through .Net remoting. I don't have any idea about .Net remoting.
(FYI, Application built on .Net 2.0 framework. It is a complex application).

Can you please suggest me which one should i prefer (web service or .Net remoting)?
Do i have to re-architecture the entire application?
Is there any possible way to separate the BL/DAL from UI with minimal impact?

Please provide your valuable information.

With Regards,
Anand

Posted 13-Jun-11 2:15am

anandhakrishnabca

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

#realJSOP · Answer 1 · 2011-06-13T02:21:00

.Net Remoting is deprecated. Use a WCF service. It allows the use of the most appropriate protocol for your situation, and it's easy to implement.

Unfortunately, anything you chose (.Net Remoting, Web Service, WCF service) is probably going to require a moderate/significant re-design of the interface between the buisness layer and the DAL, and of course, the severity is going to be determined completely on the current non-service implementation.

gino_montano · Answer 2 · 2012-06-23T07:39:00

Estimado,
Lamento el tiempo que paso para responderte a tu pregunta.
En primer lugar, lo recomendable no es utilizar lo ultimo (vs 2010) por lo menos hasta el 2013 (3 años despues que este revisado y probado), pues he visto un proyecto que utilizo WCF y el rendimiento de la aplicación fue desaprobado.
Yo trabajo con Visual Studio 2005 (c#) y utilice "genuine channels for .net remoting", y el redimiento era muy bueno. La arquitectura que se uso, tenia todos los niveles de seguridad (Banco Internacional del Peru) y las capas logicas estaban separadas en tres servidores (Web, Componentes y Base de datos).
Te lo recomiendo!.

Saludos,
Gino Montaño Avalos
gino.montano@gmail.com

.Net Remoting or Web Service?

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0