resources or database?

I have an ecommerce project to develop with perhaps 3000 products. Being fairly new to MODx I’m wondering if it’s best to store and access product info directly from a mysql database, or to use a MODx resource page with TVs for each product.

Using resources:

• One concern is loading time for the resource tree frame in the manager - if each product requires say 100 bytes to display the resource name etc then 100 x 3000 resources is 300Kb. Thats acceptable I feel as it only needs to load once per session being that Evo uses frames.
• Another concern is being able to manage that many resources in the resource tree. There is a search function which would be helpful, and the products would be in catagories and subcatagories which would also be helpful. But still....

Using mysql directly:

• I’m comfortable doing this as I’ve done loads of database work in mysql and php before. However, it seems to me that a major reason for using a CMF is to bypass the need to do this type of thing.
• I do like the idea of using resources as it also means clients can access the products via the site manager - using mysql directly would mean creating another client login and creating CRUD forms to allow product editing etc, which is all already handled by the manager if resources were used. This is a major pro for using resources.... Or is there a method of incorporating resources/TVs and the direct mysql access method?

Anyone been here before? Can you offer any other pros/cons for each storage/access method?

With a carefully thought-out structure, I think using resources would be your best bet. Especially with the new QuickManager, where the tree doesn’t come into play at all.

The QuickManager menu can be customized very easily, and I’m working with one very bright guy who has a "tools" section in the tree for management tasks, with a main "management" page that is linked to in the QM menu.

All the PubKitBlog and other front-end management applications are linked to from that page.

Very nice, no need for the end-user to go to the Manager at all; his login home page is set to be that "management" menu page.