DataBase vs Cache

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

vze1r2ht@verizon.net - 30 Jun 2006 17:28 GMT

I have a UserCollection that contains User objects that map to a User
table.

There could be potentially, 50-100K users in the table.

Should I load all the users into a Cache and just read/write from
there? (Everytime a write is made, it also writes to the DB). If I do
so, will it be memory efficient?

Also for filtering a collection, is there a way to have multiple
filters like DataTable.Select can?
Like very complex ones like (AND ID = 1 OR ID = 2) AND Admin = True etc.

Reply to this Message

Marina Levit [MVP] - 30 Jun 2006 17:32 GMT

That is a lot of data to store in the cache. And I'm not sure it is worth
it - it shouldn't be a lot of work to go to the user's table when you are
logging in a user or what not. And keeping the cache in sync with the
database would be a pain.

If you have multiple web servers at some point, now you have the problem of
keeping the other web server in sync.

And yes, you can use AND and OR in the DataTable.Select.

>I have a UserCollection that contains User objects that map to a User
> table.
[quoted text clipped - 8 lines]
> filters like DataTable.Select can?
> Like very complex ones like (AND ID = 1 OR ID = 2) AND Admin = True etc.

Reply to this Message

DataBase vs Cache

Free Magazines