Architecture Decisions Regarding Common DB Access, Remoting, and Performance

J

JTS

I need to create three ASP.NET applications - each one will run on a
different production server. Each application does basically the same thing
with respect to data access; the apps differ primarily in presentation and
audience. Each app will need to interact with a SQL Server database that is
running on its own server. All servers will initially be on the same subnet,
however there is no guarantee that they will remain on the same subnet in
the future (the SQL Server may go behind an its own firewall). Just
considering my architecture options...

Is this scenario a no-brainer for separating out the data access logic to
its own assembly? If so, is .NET Remoting the obvious choice for
communication (given the close proximity of the boxes)? What about the
future firewall for the SQL Server - how would that impact the design, and
should I design for that up front? What about performance considerations. Am
I correct in thinking that implementing a Web Service (strictly for data
access services from behind the firewall) in this scenario would only serve
to hurt performance and create bigger headaches for data security on the
wire in (comparison to implementing data services via .NET Remoting)?

Any thoughts on any aspect of these factors is greatly appreciated
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Members online

Forum statistics

Threads
473,744
Messages
2,569,480
Members
44,900
Latest member
Nell636132

Latest Threads

Top