distributed App, best design (SPEED)

hello,

i am designing a multi tier distributed app in .NET .
DataAccess.dll containing load , insert , update ,.... methods.
DataItem.dll containing classes having the list of the concerning
properties (CPerson : FirstName , LastName ,...) these classes
are filled by the presentation tier and passed as parameters
to be inserted Ex: daPerson.Load (objPerson). stored procedures
are used to access the DB.

The speed is an important concern !!!.

what is the best design if :
-- the database is put in a server (over internet).
-- i want to build a windows app.
-- i can put all dlls in the client side.

thanks in advance.

Well, the design definately depends on how the application is supposed to function.

If the distributed application has a client side and a server side which is all local to the end user's LAN, then you can see how putting as much as possible on the LAN's server machine would be beneficial.

If the app is going to be run over the internet/WAN then the design will be a bit different.

Without having a lot of detail in how this is supposed to work, I can suggest that you make a list of what function need to happen, if you will be connecting to an outside / remote data server, etc.

If you are connecting remotely to access data, you may want to think about designing a datacache system to store data that doesn't change frequently on the client machine.

If you want more speed, design a separate app to run in separate memory to do the data pulls, and store that data in a cache or queue, then have the client poll for that data right after a flag has been set saying that the data is ready for retrieval.

hello,

you are right , some details are missing !.

The app is going to be run over the internet/WAN . The DataBase
should reside in a remote server and accessed from a windows
application .

The DataItem.dll that contains classes representing the state
of each object , should be put in the client side.

well , an example for the dataaccess classes is "daPerson.vb"
this class should have a list of methods and functions
a Load function to retreive a list of objects to be bound to a
DataRepeater ,
a Load function to retreive a single object for the editing,
and Insert , Update and Delete functions.
All DataAccess classes should have mainly the same functionality.

The question is where do i have to put the DataAccess classes?

and which technology do i have to use?
Web service ? .NET remoting? all together?

another question ! what do you mean by :::
"""a separate app to run in separate memory to do the
data pulls, and store that data in a cache or queue"""

thanks a lot,

>"""a separate app to run in separate memory to do the
>data pulls, and store that data in a cache or queue"""

There are lots of ways to do this, however, the easiest way to describe what I mean is to write your application first with everything in one place, then start to dissect the parts that need to be distributed.

It is nice to have code wizards because the alpha development is virtually done for you. Now you can focus on making it work in a distributed fashion.