J
Jacob
I am designing a system which will have a C# backend and an ASP.NET frontend.
My question is about how I would best design the application. The first way
that I am considering doing it is writing a data access layer as part of the
App_Code directory inside the webapp which would just compile and run with
the app. The second option would be to create a server process that
interfaces with the database and then have the web frontend communicate with
the server process by an IPC method (most likely WCF).
It is likely that this application will have to support a large number of
concurrent users if that has an effect on the method selected. Any input
would be appreciated, a pros/cons list would be great if somebody has that
much time. Thanks in advance!
My question is about how I would best design the application. The first way
that I am considering doing it is writing a data access layer as part of the
App_Code directory inside the webapp which would just compile and run with
the app. The second option would be to create a server process that
interfaces with the database and then have the web frontend communicate with
the server process by an IPC method (most likely WCF).
It is likely that this application will have to support a large number of
concurrent users if that has an effect on the method selected. Any input
would be appreciated, a pros/cons list would be great if somebody has that
much time. Thanks in advance!