1 reply to this topic

[reachpradeep]

ive heard alot of arguements for and against the use of datasets in a asp.net website but have now got a bit confused on what the best approach is to when developing a standard web app.

do u think it is appropriate to use datsets to replace the traditional business object classes in the web environment?
e.g a Customer class would be replaced by a dataset datatable called Customers.

ive have heard that some developers replicate there whole database structure into one dataset and make there website run off the datasets. so basically have the whole database in memeory.
what are the issues when doing this? first thing the springs to mind is that you would chew up the server memory, but what if there isnt that much data in the db?

you thoughts?

[BlackRabbit]

- About Datasets:

they are too heavy for one-shot process as web pages, business objects are not just for data-handling purposes but for secure data access management, lets not forget we are in a web server accessible from everywhere in the world and we don't want foreigners to easily hack their way in our dbs.

- About in memory databases for web servers/services

Nowadays memory is not such an issue if you own your server, about how to load it properly in server memory you should look to more natural ways as :

- Using memory DB's, available in MySQL and in latest SQL Server version.

- Using memcache technologies on the server

- Doing your own executable who mounts the "Shared memory" mechanisms and handles the concurrency