Architectural advice needed

Matthew Owens

Hey,

I've been tasked to write a system using wpf & wcf, the system will be nTier with data held centrally in an SQL Server Database. There will be 200+ connected clients, updating the data more or less constantly so its pretty transaction intense. Ideally the data will be accessed through a series of WCF stubs. My question is: what would be the best way to handle the data? Would it be wise to use one static cached dataset which every client accesses through the services, or to proliferate the data to the client and hold it locally in a dataset? Any ideas or suggested articles would be be much appreciated.

Thanks

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Bechir Bejaoui18y ago
In this case you have to adopt multi threaded technique to avoid the server overhead and the concurence between serveral use. In your case Mutex class and Semaphore are the best objects to manage the access to the data. The data it self is not the problem you can use any type of data container.

Other suggestion, I propose that you use only one instance at the server level, I mean don't allow each client to create its server instance, use a singleton object at the server level.

Other sugestion, If you have to create a great number of clients, I propose to create only one then clone the rest and change their properties rather than instnnciate each one it's more performant
Bechir Bejaoui18y ago
In this case you have to adopt multi threaded technique to avoid the server overhead and the concurence between serveral use. In your case Mutex class and Semaphore are the best objects to manage the access to the data. The data it self is not the problem you can use any type of data container.

Other suggestion, I propose that you use only one instance at the server level, I mean don't allow each client to create its server instance, use a singleton object at the server level.

Other sugestion, If you have to create a great number of clients, I propose to create only one then clone the rest and change their properties rather than instnnciate each one it's more performant